# CVE-2026-46623: OpenAM Account Takeover via Unverified Password Change in OAuth2 Module

> Unauthenticated attackers can take over local accounts by exploiting missing attribute filtering in the OAuth2 module when account creation is enabled.

- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-gf57-4mp6-m85x, UBUNTU-CVE-2026-46623

## What is CVE-2026-46623?

CVE-2026-46623 is a high-severity authentication bypass vulnerability in OpenIdentityPlatform OpenAM, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, the OAuth2 authentication module updates an existing local account with profile attributes that can include userPassword and inetUserStatus, rewriting the password to the username and reactivating disabled accounts. The missing OAuth.removeRestrictedAccountUpdateAttributes filtering permits these credential and status fields to reach the account update. With account creation enabled, repeated OAuth login causes the default ldapService chain to accept the username as both identifier and password, allowing an unauthenticated attacker to take over the local account without interacting with the identity provider. The rewrite can be denied for usernames shorter than the configured minimum password length. This issue is fixed in version 16.1.1.

Weakness: CWE-620 (Unverified Password Change), CWE-1391 (Use of Weak Credentials)

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

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


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

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

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

## Is CVE-2026-46623 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46623 is a high-severity authentication bypass vulnerability in OpenIdentityPlatform OpenAM, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-46623 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.openidentityplatform.openam:openam-auth-oauth2 (Maven): affected all versions; fixed in 16.1.1
- org.openidentityplatform.openam:openam-auth-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-46623/ (Markdown: https://insights.sbomify.com/CVE-2026-46623/index.md)
```

## Sources

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

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