Home › Vulnerabilities

Open Identity Platform OpenAM Flaw CVE-2026-123549: Update Now

Published November 8, 2026 · Last updated November 8, 2026

CVE Critical Patch

The short version: CVE-2026-123549 is a critical-severity security flaw in Open Identity Platform OpenAM. The National Vulnerability Database (NVD) published it on November 8, 2026, and the score it lists is 9.8 out of 10. When FraudMeNot checked on November 8, 2026, CISA had not added CVE-2026-123549 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-123549

The record was filed by vulncheck.com. In its own words: "OpenAM before 16.1.4 fails to enforce the Valid Creation Attributes list during self-registration, allowing anonymous attackers to set restricted attributes including group membership. Attackers can register through the legacy self-service REST endpoint or User Self-Service flow to join administrative groups and gain full administrative control of OpenAM."

Why OpenAM admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on vulncheck.com rated CVE-2026-123549 9.8 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping OpenAM running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Scores can differ between the vendor and NVD because each judges the worst realistic case differently. For this flaw, the address listed on vulncheck.com gives it 9.3 (Critical, CVSS 4.0).

Affected OpenAM releases

According to the record, these releases are vulnerable:

  • versions before 16.1.4

The type of bug behind CVE-2026-123549

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-269, Improper Privilege Management. MITRE describes this class of bug as follows: "The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor."

Vendor remediation for CVE-2026-123549

The vendor advisory remediation for operators of OpenAM, quoted for this page, is: "Upgrade OpenAM to 16.1.4 or later (OpenIdentityPlatform advisory GHSA-jv8f-m88g-h6mm; versions up to 16.1.3 are affected). Only realms where self-registration is enabled are affected, and self-registration is off by default in both the legacy and current self-service settings. Check User Registration in each realm's User Self-Service service and Self-Registration for Users with the Legacy Self-Service REST Endpoint in the legacy settings; until patched, turn self-registration off where it is not needed. The 9.8 and 9.3 scores come from VulnCheck as CNA, not from NVD or the OpenAM maintainers, and no exploitation has been publicly confirmed. After upgrading, list members of administrative groups in every realm, delete accounts that registered themselves into privileged groups, review recently created agents and groups, and rotate OAuth2 client secrets or federation settings if an unexpected administrator could have changed them."

What to do about it

  • Update now: Upgrade OpenAM to 16.1.4 or later (OpenIdentityPlatform advisory GHSA-jv8f-m88g-h6mm; versions up to 16.1.3 are affected). Only realms where self-registration is enabled are affected, and self-registration is off by default in both the legacy and current self-service settings. Check User Registration in each realm's User Self-Service service and Self-Registration for Users with the Legacy Self-Service REST Endpoint in the legacy settings; until patched, turn self-registration off where it is not needed. The 9.8 and 9.3 scores come from VulnCheck as CNA, not from NVD or the OpenAM maintainers, and no exploitation has been publicly confirmed. After upgrading, list members of administrative groups in every realm, delete accounts that registered themselves into privileged groups, review recently created agents and groups, and rotate OAuth2 client secrets or federation settings if an unexpected administrator could have changed them.
  • Who should act: IT teams, managed service providers, and developers who run or ship OpenAM. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Open Identity Platform (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 8, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-123549. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-123549 record details from CISA and NVD

  • Attack complexity for CVE-2026-123549: low
  • CVE-2026-123549 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-123549: exploitability 3.9, impact 5.9.
  • Who mapped the weakness type: the address listed on vulncheck.com (Primary)
  • References in the NVD record: 2.

Dates to know

  • November 8, 2026: NVD publishes CVE-2026-123549.
  • November 8, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-123549 is not listed.
  • November 8, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.