CVE-2026-123549

waiting for further signalsZero needs more public information before it can validate it.

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
4h 46msince last run
23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h33m
0
+4h
+6h
+8h
+10h
+12h

description

OpenAM versions before 16.1.4 do not properly restrict attributes submitted during account self-registration. An unauthenticated attacker may assign privileged group membership and obtain administrative control where self-registration is enabled.

mitigation

Upgrade OpenAM to version 16.1.4 or later. Until the upgrade is complete, disable or restrict anonymous self-registration and the legacy self-service registration endpoint.

fixed in 16.1.4

check
no
exploit
no
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.
contextual
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
23m
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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

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": "published",
  "anchor_state": "anchored",
  "title": "Self-registration authorization bypass in OpenAM",
  "summary": "OpenAM versions before 16.1.4 do not properly restrict attributes submitted during account self-registration. An unauthenticated attacker may assign privileged group membership and obtain administrative control where self-registration is enabled.",
  "mitigation": "Upgrade OpenAM to version 16.1.4 or later. Until the upgrade is complete, disable or restrict anonymous self-registration and the legacy self-service registration endpoint.",
  "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": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.751353383333335,
  "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 08:40Z

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.