CVE-2026-123549

validatingZero is analyzing and reversing it now.

GHSA-f3q2-cw3w-jw26 ↗EUVD-2026-119434 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
OpenIdentityPlatform OpenAM < 16.1.4
fixed in 16.1.4
ETK-2026-3875Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

OpenAM before 16.1.4 may allow anonymous self-registration requests to set attributes that should be restricted, including group membership. An attacker can use an available legacy self-service REST endpoint or User Self-Service flow to join administrative groups and potentially obtain administrative control.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade OpenAM to version 16.1.4 or later. Until upgraded, disable or restrict anonymous self-registration and the affected self-service interfaces where operationally possible.

fixed in 16.1.4

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 01:37Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-08 01:37Z
    ghsa: trigger signal, started the run
  2. 2026-11-08 01:37Z

this entry in the feed

GET /api/v1/feed/CVE-2026-123549

{
  "etk_id": "ETK-2026-3875",
  "cve_id": "CVE-2026-123549",
  "display_id": "CVE-2026-123549",
  "ghsa_id": "GHSA-f3q2-cw3w-jw26",
  "euvd_id": "EUVD-2026-119434",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Improper attribute authorization in OpenAM self-registration",
  "summary": "OpenAM before 16.1.4 may allow anonymous self-registration requests to set attributes that should be restricted, including group membership. An attacker can use an available legacy self-service REST endpoint or User Self-Service flow to join administrative groups and potentially obtain administrative control.",
  "mitigation": "Upgrade OpenAM to version 16.1.4 or later. Until upgraded, disable or restrict anonymous self-registration and the affected self-service interfaces where operationally possible.",
  "vendor": "OpenIdentityPlatform",
  "product": "OpenAM",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 16.1.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "16.1.4"
      ],
      "package_name": "OpenAM",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-08T01:37:53.496000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T01:37:53.496000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T01:37:53.496000+00:00",
      "url": "https://github.com/advisories/GHSA-f3q2-cw3w-jw26"
    }
  }
}

published 2026-11-08 03:48Z
last change 2026-11-08 04:01Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.