External risk intelligence

OpenAM Self-Registration Attribute Bypass Privilege Escalation.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-123549

OpenAM is an identity and access management platform frequently deployed as a public-facing identity portal to handle user authentication, self-service registration, and REST API access. Because self-service registration flows are designed to be accessible to external users for account creation, the vulnerable interface is inherently public-facing by design.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in OpenAM's self-registration process allows unauthorized users to gain administrative privileges by manipulating attribute settings. This could lead to a complete compromise of the platform and any sensitive data it manages.

  • Anonymous registration can grant administrator access.
  • Concerns arise from potential unauthorized control.
  • Confirm if OpenAM is deployed and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by accessing either the legacy self-service REST endpoint or the User Self-Service flow. By submitting a crafted registration request, they can bypass restrictions on attribute settings, allowing them to add themselves to administrative groups. This ultimately grants them full administrative control over the OpenAM system.

  • Entry: Publicly accessible self-registration.
  • Trigger: Setting restricted user attributes.
  • Risk: Full administrative control of the system.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, anonymous attackers could exploit a flaw in OpenAM's self-registration process to assign themselves administrative privileges. This could occur when using the legacy self-service REST endpoint or the User Self-Service flow.

  • Administrative group memberships.
  • Anonymous attackers may exploit the self-registration flow.
  • Full administrative control of OpenAM.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in OpenAM, allowing anonymous attackers to gain administrative control by exploiting the self-registration attribute bypass, requires immediate attention from teams responsible for identity and access management. The first practical step is to inventory all OpenAM instances, confirm their exposure to the internet or untrusted networks, and identify the business-critical systems relying on them. This will allow for prioritization and coordinated remediation planning.

  • Identity and Access Management teams own resolution.
  • Verify external access and business criticality.
  • Plan and coordinate remediation with vendor.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is OpenAM?

OpenAM is an identity and access management platform. Organizations use it to centralize how users log in, manage their profiles, and authenticate across different applications. It acts as a gatekeeper for digital identities, often hosting portals that allow users to register for accounts or interact with services through its built-in self-service features and APIs.

What does CVE-2026-123549 mean for my security?

This vulnerability is an Improper Privilege Management issue, categorized as CWE-269. It means the software fails to properly check which profile details a new user is allowed to set during account creation. Because of this flaw, an anonymous person can tell the system they belong to an administrative group, tricking OpenAM into granting them full control over the platform immediately upon registration.

How can an attacker trigger this vulnerability?

An attacker triggers this by using the standard account creation process, specifically through the legacy self-service REST endpoint or the User Self-Service flow. They simply submit a registration request that includes unauthorized attribute data. This bug is not triggered if self-registration features are completely disabled or if the specific, vulnerable service endpoints are not active in your configuration.

Is my OpenAM instance likely at risk?

According to Halo Surface Signal, this software is frequently deployed as a public-facing portal specifically to handle account registration. If your instance is reachable from the internet to allow user sign-ups, it is inherently positioned in a way that makes this vulnerability a significant concern, as anonymous users can reach the necessary registration flows directly.

Do I need to take action to secure my OpenAM deployment?

Yes. First, create an inventory of all your OpenAM instances to identify which ones are currently running. Determine if these systems are accessible from the internet or untrusted networks. Once you have identified your footprint and assessed the business criticality of each instance, prioritize them for updates or temporary service modifications as recommended by the vendor.

References