On this page (7 sections)

A critical flaw tracked as CVE-2026-123549 affects OpenAM, the open source access management and single sign-on platform. According to the GitHub Advisory Database entry, OpenAM before 16.1.4 does not enforce the Valid Creation Attributes list during self-registration. An anonymous attacker can therefore set attributes that should be restricted, including group membership.

If your organization runs OpenAM and exposes any self-registration feature to the internet, treat this as urgent. The advisory says the result can be full administrative control of the OpenAM instance, and an identity provider sits in front of many other systems.

What happened

The advisory was published on November 8, 2026. Its description states that OpenAM fails to apply the Valid Creation Attributes list when a new user registers themselves. That list is meant to restrict which attributes a self-registering user may supply. Without enforcement, a registrant can supply values for attributes they should never control.

The advisory names two paths: the legacy self-service REST endpoint and the User Self-Service flow. Through either, an anonymous attacker can reportedly join administrative groups and gain full administrative control of OpenAM.

Only one independent publisher covers this so far. The NVD record repeats the same description and is not separate confirmation. The advisory also links to a VulnCheck advisory and a project security advisory; check those for fix details, as this article could not rely on their contents.

Why this weakness is dangerous

This is a privilege management problem (CWE-269). Self-registration is meant to create low-privilege accounts. The safeguard is an allow-list of attributes the user may set. When the server ignores that list and trusts whatever the client sends, the user effectively decides their own privileges. Group membership is often what grants administrative rights, so setting it at sign-up turns a public form into an admin creation tool.

The CVSS v4 metrics in the advisory describe network attack vector, low attack complexity, no attack requirements, no privileges required and no user interaction. Impact on the vulnerable system is rated high for confidentiality, integrity and availability. In plain terms: no login is needed, and no one else has to click anything.

CVSS score shown in the GitHub advisory
9.3
OpenAM version named as the boundary in the description
16.1.4

Who is exposed

  • Organizations running OpenAM versions earlier than 16.1.4.
  • Deployments where the legacy self-service REST endpoint or the User Self-Service registration flow is reachable by anonymous users, including from the internet.
  • Environments where administrative access to OpenAM, or membership in certain groups, grants access to other applications through single sign-on.

If self-registration is disabled and unreachable, the attack path described in the advisory should not be available, though the advisory does not state this explicitly. Upgrading is still the proper fix.

How to check your exposure

Start with the version, then look at what is reachable and who is in your privileged groups. The research does not give a version command for OpenAM, so use your normal deployment records or the version shown in your administration console.

  1. Find every OpenAM instance you run, including test and forgotten ones, and record its version.
  2. Check whether User Self-Service registration or the legacy self-service REST endpoint is enabled and reachable from outside your network.
  3. Review the membership of administrative groups and sort the accounts by creation date. Look for accounts you do not recognize, especially recent self-registered ones.
  4. Review web server and OpenAM access logs for registration requests from unfamiliar addresses, and for new accounts created through self-service.

A simple read-only way to look through a reverse proxy or web server access log for registration activity is to search for the word in request paths. Run it on the host that stores the log; adjust the path to your setup. Matches show registration requests you can then compare against known users.

Search an access log for registration requests (read-only; adjust the log path)Shell
grep -i "register" /var/log/nginx/access.log | tail -n 100

What to do now

  1. Upgrade OpenAM to 16.1.4 or later, after confirming the exact fixed release in the project's security advisory.
  2. If you cannot upgrade immediately, disable self-registration and the legacy self-service REST endpoint, or restrict them to trusted networks.
  3. Audit administrative groups and remove any account you cannot account for.
  4. If you find suspicious accounts, assume the instance may be compromised: rotate administrator credentials, secrets and keys that OpenAM manages, and review configuration changes.
  5. Review applications that trust OpenAM for sign-on and check them for unexpected access during the exposure period.
  6. Keep a copy of logs from before and after the change for investigation.
Caution. Upgrading or disabling features on an identity provider can interrupt sign-in for every application that depends on it. Test first, schedule a window, and have a rollback plan and a break-glass administrator account ready.
Tip. If you need to put a control in front of the endpoints while you plan the upgrade, a web application firewall rule or an IP allow-list for registration paths can reduce exposure. See What is a WAF? for what this can and cannot do. It is a stopgap, not a replacement for the update.

Detection and monitoring afterwards

  • Alert on new members added to administrative groups, and on any account created through self-service.
  • Alert on administrative logins from new locations or at unusual times.
  • Watch for configuration changes to realms, authentication chains and trusted applications.
  • Track your internet-facing services so that an exposed login or registration page does not appear unnoticed. Webforta Monitor can watch certificate, DNS and header changes on the hosts that front your identity services, which helps you notice unexpected changes around them.

For wider guidance on spotting compromise, see how to check if a website is hacked and website hacked: what to do.

What is still unknown

The GitHub entry lists affected and patched versions as unknown in its structured fields and marks the advisory as unreviewed. It does not say whether exploitation has been observed, and the research contains no proof-of-concept or incident reports. Vendor release notes should be treated as the authority on exactly which releases contain the fix. This article will need updating if the project publishes more detail.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-123549 - GitHub Advisory Databasegithub.com
  2. CVE-2026-123549: OpenAM before 16.1.4 fails to enforce the Valid Creation Attributes list during self-registration, allowing anonymous attackers to set restricted attributes…nvd.nist.gov ·
  • OpenAM
  • CVE-2026-123549
  • privilege escalation
  • identity management
  • authentication