OpenAM Authentication Bypass via RADIUS Spoofing
Affects OpenAM Community Edition through 16.0.6 where a RADIUS module instance is enabled on a login chain. No vendor severity rating is given. Fixed in 16.1.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 16.1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, the `RADIUS` authentication module opens an unconnected datagram socket and trusts the first UDP datagram received on the client source port. The receive path does not verify the source IP and port, match the response identifier to the outstanding request, or verify the RFC 2865 `Response Authenticator`; the RFC 2869 `Message-Authenticator` is neither sent nor required. Any non-Reject/non-Challenge packet is treated as success. On a deployment with a `RADIUS` module instance enabled on a login chain, an unauthenticated network attacker can race the real server on-path or spray forged `Access-Accept` packets off-path and obtain a session for any `RADIUS`-mapped username without knowing the shared secret. Unlike CVE-2024-3596, exploitation requires no MD5 chosen-prefix forgery because no response authenticator is checked. The resulting session carries the impersonated principal's privileges. This issue is fixed in version 16.1.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- OpenIdentityPlatform OpenAM
fixed in 16.1.1
- org.openidentityplatform.openam:openam-radiusMaven
fixed in 16.1.1
References 3
GitHub · OpenIdentityPlatform/OpenAM
Questions about CVE-2026-46560
What does this mean?
A spoofed RADIUS Access-Accept response can make OpenAM accept a login. An attacker can then obtain an OpenAM session for any RADIUS username without knowing the shared secret.Source: github.com
Am I affected, and how do I check?
OpenAM Community Edition through version 16.0.6 is affected, but only where an administrator has enabled a RADIUS module instance on a login chain. Check the installed OpenAM version and whether a RADIUS module instance is enabled on any login chain.Source: github.com
What should I do about it?
Upgrade to OpenAM Community Edition 16.1.1, which contains the patch. The org.openidentityplatform.openam:openam-radius package is also fixed in 16.1.1.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data