Vulnerabilities in pkg:maven/org.openidentityplatform.openam/openam-auth-oauth2

PACKAGE
Advisory Identifier: GHSA-gf57-4mp6-m85x
Share
Advisory Summary

CVE-2026-46623 is a HIGH openam account takeover vulnerability (CWE-620: Unverified Password Change) affecting Openam auth oauth2 libraries in the Maven ecosystem. The issue involves openam account takeover via unverified password change in oauth2 module. Remediation is available by upgrading affected packages to version 16.1.1.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/org.openidentityplatform.openam/openam-auth-oauth2

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/org.openidentityplatform.openam/openam-auth-oauth2. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-gf57-4mp6-m85x CVE-2026-46623 HIGH OpenAM Account Takeover via Unverified Password Change in OAuth2 Module

CVE-2026-46623 at a Glance

CVE Identifier CVE-2026-46623
GHSA Identifier GHSA-gf57-4mp6-m85x
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-620: Unverified Password Change
Affected Product Openam auth oauth2
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-46623

To remediate this vulnerability, upgrade all affected Openam auth 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-auth-oauth2 fixed: 16.1.1 
<dependency>
    <groupId>org.openidentityplatform.openam</groupId>
    <artifactId>openam-auth-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-46623, 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 auth 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-620: Unverified Password Change, where when setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication. In Openam auth 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 Unverified Password Change (CWE-620) and Use of Weak Credentials (CWE-1391) issue in OpenAM's OAuth2 authentication module silently rewrites a local user's password to the literal string of their username on OAuth2 re-login of an existing account. The default ldapService chain then accepts the username as the password for that user, allowing an unauthenticated attacker to obtain a session via the standard authenticate endpoint with both username and password set to the username, without any IdP interaction. This affects OpenAM Community Edition through version 16.0.6 and was patched in version 16.1.1. ## Impact OpenAM Community Edition deployments through version 16.0.6 that use the OAuth2 authentication module with account creation enabled (the default) are potentially affected. After two OAuth logins of a given user, that user's local password becomes their username, and the account is reachable through the default ldapService chain with username as both identifier and password. For pre-existing users whose IdP profile resolves against an existing local identifier, the rewrite fires on the very first re-login. Usernames shorter than the default minimum password length have the rewrite silently denied (so very short administrative accounts are not affected), and the same update path marks accounts active on every OAuth login, silently reactivating disabled accounts. Successful exploitation grants an unauthenticated attacker a session carrying the victim principal's privileges. ## Patch This has been patched in OpenAM Community Edition version 16.1.1. Users are encouraged to update to the latest release.

CVE-2026-46623 Affected Openam auth oauth2 Versions

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

References

GitHub Advisory / Wiki ADVISORY
https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-gf57-4mp6-m85x
Openam auth oauth2 Source Repository REPOSITORY
https://github.com/OpenIdentityPlatform/OpenAM

Frequently Asked Questions

What is CVE-2026-46623?
CVE-2026-46623 is a security vulnerability in Openam auth oauth2 involving OpenAM Account Takeover via Unverified Password Change in OAuth2 Module under CWE-620: Unverified Password Change.
Which Openam auth oauth2 versions are affected?
Affected versions include releases prior to 16.1.1 across affected packages: org.openidentityplatform.openam:openam-auth-oauth2.
What version fixes CVE-2026-46623?
Upgrading to 16.1.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openam-auth-oauth2 affected?
Yes, org.openidentityplatform.openam:openam-auth-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-46623?
CVE-2026-46623 is classified under CWE-620: Unverified Password Change (When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.).
How can I check Maven dependencies for CVE-2026-46623?
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-gf57-4mp6-m85x",
  "modified" : "2026-06-26T17:33:35Z",
  "published" : "2026-06-26T17:33:35Z",
  "aliases" : [ "CVE-2026-46623" ],
  "summary" : "OpenAM Account Takeover via Unverified Password Change in OAuth2 Module",
  "details" : "## Summary\n\n**Description**\n\nAn Unverified Password Change (CWE-620) and Use of Weak Credentials (CWE-1391) issue in OpenAM's OAuth2 authentication module silently rewrites a local user's password to the literal string of their username on OAuth2 re-login of an existing account. The default ldapService chain then accepts the username as the password for that user, allowing an unauthenticated attacker to obtain a session via the standard authenticate endpoint with both username and password set to the username, without any IdP interaction. This affects OpenAM Community Edition through version 16.0.6 and was patched in version 16.1.1.\n\n## Impact\nOpenAM Community Edition deployments through version 16.0.6 that use the OAuth2 authentication module with account creation enabled (the default) are potentially affected. After two OAuth logins of a given user, that user's local password becomes their username, and the account is reachable through the default ldapService chain with username as both identifier and password. For pre-existing users whose IdP profile resolves against an existing local identifier, the rewrite fires on the very first re-login.\n\nUsernames shorter than the default minimum password length have the rewrite silently denied (so very short administrative accounts are not affected), and the same update path marks accounts active on every OAuth login, silently reactivating disabled accounts. \n\nSuccessful exploitation grants an unauthenticated attacker a session carrying the victim principal's privileges.\n\n## Patch\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:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.openidentityplatform.openam:openam-auth-oauth2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "16.1.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-gf57-4mp6-m85x"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OpenIdentityPlatform/OpenAM"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1391", "CWE-620" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T17:33:35Z",
    "nvd_published_at" : null
  }
}