CVE-2026-46498: Openam oauth2 OpenAM Arbitrary OAuth Token Minting Vulnerability

HIGH
Advisory Identifier: GHSA-cj8f-2fhf-826r
Share
CWE-639
Published
Advisory Summary

CVE-2026-46498 is a HIGH openam arbitrary oauth token minting vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Openam oauth2 libraries in the Maven ecosystem. The issue involves openam arbitrary oauth token minting via push registration. Remediation is available by upgrading affected packages to version 16.1.1.

CVE-2026-46498 at a Glance

CVE Identifier CVE-2026-46498
GHSA Identifier GHSA-cj8f-2fhf-826r
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Openam oauth2
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-46498

To remediate this vulnerability, upgrade all affected Openam oauth2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.openidentityplatform.openam:openam-oauth2 fixed: 16.1.1 
<dependency>
    <groupId>org.openidentityplatform.openam</groupId>
    <artifactId>openam-oauth2</artifactId>
    <version>16.1.1</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=org.openidentityplatform.openam

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-46498, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.openidentityplatform.openam

Analyze the terminal output to locate any version of Openam oauth2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 16.1.1), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.openidentityplatform.openam command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Openam oauth2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary **Description** An Authorization Bypass Through User-Controlled Key (CWE-639) exists in OpenAM's stateful OAuth2 token-read path. Under certain conditions, this may allow an attacker to forge OAuth2 bearer tokens and OIDC ID tokens with arbitrary subject, client, realm, and scope. This affects OpenAM Community Edition through version 16.0.6. The OAuth2 token-read path reads caller-supplied token identifiers from the shared Core Token Store (CTS) without placing them in an OAuth-only namespace and without binding the row's trusted CTS type to the expected OAuth token family, so any CTS row whose BLOB claims to be an OAuth token is accepted on the read path with no integrity check. ## Impact OpenAM Community Edition deployments through version 16.0.6 with the OAuth2 Provider service enabled in a realm are potentially affected, but the vulnerable read path is only reachable once an attacker can place attacker-controlled JSON into the shared CTS under an identifier they know. For example, an anonymous Push Notification SNS callback handler, reachable by any low-privileged user in a Push Notification-enabled realm after a single legitimate Push registration can trigger the exploit. In any deployment where such a primitive exists, an attacker can forge OAuth2 bearer tokens with attacker-chosen userName, clientID, realm, and scope. The compromise does not by itself create an OpenAM SSO session or grant admin-console access. ## Patch This has been patched in OpenAM Community Edition version 16.1.1. Users are encouraged to update to the latest release.

CVE-2026-46498 Affected Openam oauth2 Versions

1 component(s)
Fixed Versions:
16.1.1
Product / Package Ecosystem Affected Versions Fixed Version
org.openidentityplatform.openam:openam-oauth2
maven/org.openidentityplatform.openam/openam-oauth2
Maven
< 16.1.1
16.1.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-cj8f-2fhf-826r
Openam oauth2 Source Repository REPOSITORY
https://github.com/OpenIdentityPlatform/OpenAM
Openam oauth2 Release RELEASE
https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.1.1

Frequently Asked Questions

What is CVE-2026-46498?
CVE-2026-46498 is a security vulnerability in Openam oauth2 involving OpenAM Arbitrary OAuth Token Minting via Push Registration under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Openam oauth2 versions are affected?
Affected versions include releases prior to 16.1.1 across affected packages: org.openidentityplatform.openam:openam-oauth2.
What version fixes CVE-2026-46498?
Upgrading to 16.1.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openam-oauth2 affected?
Yes, org.openidentityplatform.openam:openam-oauth2 is affected in releases prior to 16.1.1. Upgrade your dependency to 16.1.1 or later.
What CWE is associated with CVE-2026-46498?
CVE-2026-46498 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Maven dependencies for CVE-2026-46498?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.openidentityplatform.openam'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cj8f-2fhf-826r",
  "modified" : "2026-06-25T17:07:58Z",
  "published" : "2026-06-25T17:07:58Z",
  "aliases" : [ "CVE-2026-46498" ],
  "summary" : "OpenAM Arbitrary OAuth Token Minting via Push Registration",
  "details" : "## Summary\n\n**Description**\n\nAn Authorization Bypass Through User-Controlled Key (CWE-639) exists in OpenAM's stateful OAuth2 token-read path. Under certain conditions, this may allow an attacker to forge OAuth2 bearer tokens and OIDC ID tokens with arbitrary subject, client, realm, and scope. This affects OpenAM Community Edition through version 16.0.6.\n\nThe OAuth2 token-read path reads caller-supplied token identifiers from the shared Core Token Store (CTS) without placing them in an OAuth-only namespace and without binding the row's trusted CTS type to the expected OAuth token family, so any CTS row whose BLOB claims to be an OAuth token is accepted on the read path with no integrity check.\n\n## Impact\n\nOpenAM Community Edition deployments through version 16.0.6 with the OAuth2 Provider service enabled in a realm are potentially affected, but the vulnerable read path is only reachable once an attacker can place attacker-controlled JSON into the shared CTS under an identifier they know. For example, an anonymous Push Notification SNS callback handler, reachable by any low-privileged user in a Push Notification-enabled realm after a single legitimate Push registration can trigger the exploit.\n\nIn any deployment where such a primitive exists, an attacker can forge OAuth2 bearer tokens with attacker-chosen userName, clientID, realm, and scope. The compromise does not by itself create an OpenAM SSO session or grant admin-console access.\n\n## Patch\n\nThis has been patched in OpenAM Community Edition version 16.1.1. Users are encouraged to update to the latest release.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.openidentityplatform.openam:openam-oauth2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "16.1.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-cj8f-2fhf-826r"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OpenIdentityPlatform/OpenAM"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.1.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-25T17:07:58Z",
    "nvd_published_at" : null
  }
}