CVE-2026-46498: OpenIdentityPlatform OpenAM OAuth token forgery via Push Registration

CVE-2026-46498 · Severity: high · CVSS 4 · Published 2026-09-15

OpenAM is an open-source access management solution used to secure web applications and services. A security flaw allows an attacker to create fraudulent digital identity tokens (OAuth2 and OIDC) that can impersonate any user or client. This could allow an attacker to gain unauthorized access to protected resources and data by pretending to be a legitimate user.

Technologies: org.openidentityplatform.openam:openam-oauth2 (Maven), Open Identity Platform OpenAM Community Edition. Vendors: Maven, Open Identity Platform.

Quick answers

Is CVE-2026-46498 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46498 being exploited in the wild.
How severe is CVE-2026-46498?
High severity, with a CVSS score of 4, published 15 September 2026.
Which products and versions are affected?
org.openidentityplatform.openam:openam-oauth2 (Maven) < 16.1.1, ECOSYSTEM:introduced=0,fixed=16.1.1; Open Identity Platform OpenAM Community Edition <= 16.0.6.
Is there a fix for CVE-2026-46498?
Yes. org.openidentityplatform.openam:openam-oauth2 (Maven): upgrade to 16.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46498 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-46498?
Check whether you run org.openidentityplatform.openam:openam-oauth2 (Maven) or Open Identity Platform OpenAM Community Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.openidentityplatform.openam:openam-oauth2 (Maven): upgrade to 16.1.1 or later
    # set org.openidentityplatform.openam:openam-oauth2 to 16.1.1 in your pom.xml or build.gradle

Technical details

An Authorization Bypass Through User-Controlled Key (CWE-639) exists in the stateful OAuth2 token-read path of OpenAM. The vulnerability stems from the OAuth2 token-read path reading caller-supplied identifiers from the shared Core Token Store (CTS) without enforcing an OAuth-only namespace or verifying the CTS type against the expected OAuth token family. An attacker who can inject attacker-controlled JSON into the CTS (for example, via a Push Notification SNS callback handler) can forge bearer tokens with arbitrary userName, clientID, realm, and scope. This issue is patched in version 16.1.1.

Affected products

  • OpenIdentityPlatform OpenAM Community Edition <= 16.0.6

Identifiers

  • CVE-2026-46498
  • GHSA-cj8f-2fhf-826r

Timeline

  • 2026-06-25: disclosed
  • 2026-06-25: advisory: GHSA-cj8f-2fhf-826r published
  • 2026-06-25: patched: Version 16.1.1 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.