OpenAM Arbitrary OAuth Token Minting via Push Registration (CVE-2026-46498) | HOL Guard CVE

High severityCVE-2026-46498GHSA-CJ8F-2FHF-826R

OpenAM Arbitrary OAuth Token Minting via Push Registration

Answer in brief

CVE-2026-46498 records a High severity vulnerability in OpenAM Arbitrary OAuth Token Minting via Push Registration. The current sources do not mark it as known exploited. The current feed maps OpenIdentityPlatform/OpenAM (generic), org.openidentityplatform.openam:openam-oauth2 (maven). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 15, 2026Updated Sep 15, 2026Source checked Sep 17, 2026First seen by HOL Jun 25, 2026Material review Sep 15, 2026

Upstream Advisory

Key facts

Risk: High
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps OpenIdentityPlatform/OpenAM (generic), org.openidentityplatform.openam:openam-oauth2 (maven). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
OpenIdentityPlatform/OpenAMgeneric	< 16.1.1	Not reported
org.openidentityplatform.openam:openam-oauth2maven	<16.1.1	16.1.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for OpenIdentityPlatform/OpenAM, org.openidentityplatform.openam:openam-oauth2.
Review the reported fix. Update org.openidentityplatform.openam:openam-oauth2 to 16.1.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jun 25, 2026

Sources and claim methodology

Upstream source description

Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, OAuthTokenStore reads caller-supplied token identifiers from the shared Core Token Store (CTS) without an OAuth-only namespace, and OAuthAdapter accepts a row whose BLOB claims to contain an OAuth token without binding the trusted CTS type or verifying integrity. An attacker who can place controlled JSON in CTS under a known token identifier, such as through Push Registration followed by an anonymous SNS callback in an enabled realm, can mint OAuth bearer tokens and OpenID Connect ID tokens with chosen subject, client, realm, and scope. The flaw does not by itself create an OpenAM SSO session or grant console access. This issue is fixed in version 16.1.1.

Quoted source text, attributed separately from HOL analysis.