CVE-2026-48717: Openam oauth2 OpenAM OAuth Authorization Bypass Vulnerability
MODERATECVE-2026-48717 is a MODERATE openam oauth authorization bypass vulnerability (CWE-285: Improper Authorization) affecting Openam oauth2 libraries in the Maven ecosystem. The issue involves openam oauth authorization bypass via pkce challenge. Remediation is available by upgrading affected packages to version 16.1.1.
CVE-2026-48717 at a Glance
How to Fix CVE-2026-48717
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.
<dependency>
<groupId>org.openidentityplatform.openam</groupId>
<artifactId>openam-oauth2</artifactId>
<version>16.1.1</version>
</dependency>
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-48717, 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-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. 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
CVE-2026-48717 Affected Openam oauth2 Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.openidentityplatform.openam:openam-oauth2
|
Maven |
< 16.1.1
|
16.1.1
|
References
Frequently Asked Questions
What is CVE-2026-48717?
Which Openam oauth2 versions are affected?
What version fixes CVE-2026-48717?
Is openam-oauth2 affected?
What CWE is associated with CVE-2026-48717?
How can I check Maven dependencies for CVE-2026-48717?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-4v2w-2wqp-mc85",
"modified" : "2026-06-29T17:46:06Z",
"published" : "2026-06-29T17:46:06Z",
"aliases" : [ "CVE-2026-48717" ],
"summary" : "OpenAM OAuth Authorization Bypass via PKCE Challenge",
"details" : "## Summary\n\n**Description**\n\nAn Improper Authorization (CWE-285) issue in OpenAM's OAuth2 authorization-code grant allows a PKCE-protected authorization code to be redeemed without the required code_verifier. This affects OpenAM Community Edition through version 16.0.6 and was patched in version 16.1.1.\n\nThe authorize endpoint stores a code_challenge on the issued code, but the token endpoint only requires a code_verifier when the realm-wide codeVerifierEnforced setting is enabled, which ships disabled by default. With that setting off, the stored challenge is checked only if the caller supplies a verifier, so omitting the parameter skips PKCE verification entirely.\n\n## Impact\nOpenAM Community Edition deployments through version 16.0.6 using the default OAuth2 provider configuration are potentially affected. For public clients, an attacker who intercepts an authorization code can exchange it for tokens without knowing the verifier. For confidential clients, the attacker additionally needs client authentication material or an execution context that can redeem the code. A token request supplying an incorrect verifier is still rejected. The bypass is specifically the missing-parameter path.\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:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.openidentityplatform.openam:openam-oauth2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "16.1.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 16.0.6"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-4v2w-2wqp-mc85"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/OpenIdentityPlatform/OpenAM"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-285" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-29T17:46:06Z",
"nvd_published_at" : null
}
}