CVE-2026-46560: OpenAM Authentication Bypass Vulnerability
HIGHCVE-2026-46560 is a HIGH (CVSS 7.5) authentication bypass vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting OpenAM libraries in the Maven ecosystem. The issue involves unauthenticated authentication bypass via radius spoofing. Remediation is available by upgrading affected packages to version 16.1.1.
CVE-2026-46560 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-46560
To remediate this vulnerability, upgrade all affected OpenAM 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-radius</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.openamHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-46560, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.openidentityplatform.openamAnalyze the terminal output to locate any version of OpenAM 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-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In OpenAM, 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-46560 Affected OpenAM Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.openidentityplatform.openam:openam-radius
|
Maven |
< 16.1.1
|
16.1.1
|
References
Frequently Asked Questions
What is CVE-2026-46560?
Which OpenAM versions are affected?
What version fixes CVE-2026-46560?
Is openam-radius affected?
What is the CVSS score of CVE-2026-46560?
What CWE is associated with CVE-2026-46560?
How can I check Maven dependencies for CVE-2026-46560?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-386j-6m86-78f9",
"modified" : "2026-06-25T17:22:24Z",
"published" : "2026-06-25T17:22:24Z",
"aliases" : [ "CVE-2026-46560" ],
"summary" : "OpenAM: Unauthenticated Authentication Bypass via RADIUS Spoofing",
"details" : "## Summary\n\n**Description**\n\nAn Improper Verification of Cryptographic Signature (CWE-347) issue in OpenAM's RADIUS authentication module allows an unauthenticated network attacker to spoof an Access-Accept response and obtain an OpenAM session for any RADIUS username, without knowing the configured shared secret. This affects OpenAM Community Edition through version 16.0.6 and was patched in version 16.1.1.\n\nThe RADIUS client opens an unconnected datagram socket and treats the first UDP datagram delivered to its source port as authoritative. The receive path does not check the source IP/port, does not match the response identifier to the outstanding request, and does not verify the Response Authenticator (RFC 2865 §3); the RFC 2869 Message-Authenticator is neither sent nor required. Any non-Reject/non-Challenge packet is treated as success, so a forged Access-Accept is accepted as a valid login.\n\n## Impact\nOpenAM Community Edition deployments through version 16.0.6 where an administrator has enabled a RADIUS module instance on a login chain are potentially affected. An attacker either races the real server on-path, or off-path sprays forged Access-Accept packets at the OpenAM client port. Because the client performs no verification of the response authenticator, no MD5 chosen-prefix forgery is required, which is is materially stronger than the BlastRADIUS family (CVE-2024-3596), in which an attacker must still forge a valid authenticator.\n\nSuccessful exploitation yields pre-authentication impersonation of any RADIUS-mapped user in any affected realm. The resulting session is indistinguishable from a legitimate RADIUS login and carries the named 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_V3",
"score" : "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.openidentityplatform.openam:openam-radius"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "16.1.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-386j-6m86-78f9"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/OpenIdentityPlatform/OpenAM"
}, {
"type" : "WEB",
"url" : "https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.1.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-347" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-25T17:22:24Z",
"nvd_published_at" : null
}
}