# CVE-2026-46498: OpenAM Arbitrary OAuth Token Minting via Push Registration

> Attackers can mint arbitrary OAuth and OIDC tokens by manipulating the token store, bypassing authentication controls in OpenAM.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-cj8f-2fhf-826r, UBUNTU-CVE-2026-46498

## What is CVE-2026-46498?

CVE-2026-46498 is a high-severity authentication bypass vulnerability in OpenIdentityPlatform OpenAM, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-46498?

2 open source packages ship an affected version, including org.openidentityplatform.openam:openam-oauth2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.openidentityplatform.openam:openam-oauth2` | Maven | All versions | 16.1.1 |
| `org.openidentityplatform.openam:openam-oauth2` | Maven | All versions | 16.1.1 |

## How do I fix CVE-2026-46498?

Upgrade org.openidentityplatform.openam:openam-oauth2 to 16.1.1 or later.

## Is CVE-2026-46498 being exploited?

There is no known exploitation of CVE-2026-46498 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46498 and fix it if it is affected.

What it is: CVE-2026-46498 is a high-severity authentication bypass vulnerability in OpenIdentityPlatform OpenAM, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46498 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.openidentityplatform.openam:openam-oauth2 (Maven): affected all versions; fixed in 16.1.1
- org.openidentityplatform.openam:openam-oauth2 (Maven): affected all versions; fixed in 16.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46498/ (Markdown: https://insights.sbomify.com/CVE-2026-46498/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46498
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46498
- OSV: https://osv.dev/vulnerability/CVE-2026-46498

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46498/
Summaries are generated and may contain mistakes; the official description above is the record.