CVE-2026-46560

OpenAM Authentication Bypass via RADIUS Spoofing

Published Oct 30, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The RADIUS authentication module in OpenAM versions before 16.1.1 opens an unconnected UDP socket and trusts the first datagram it receives without validating the source IP, port, response identifier, or the RFC 2865 Response Authenticator. Because any non‑Reject/non‑Challenge packet, including forged Access‑Accept messages, is treated as a success, an attacker can create an authenticated session for any RADIUS‑mapped username without knowing the shared secret. The resulting session carries the impersonated principal’s privileges, allowing unauthorized access under the guise of that user.

Affected Systems

Affected deployments are systems using OpenIdentityPlatform OpenAM with a RADIUS authentication module enabled on a login chain, running any version prior to 16.1.1. Versions 16.1.1 and newer contain a fix that validates RADIUS responses properly and does not accept unverified packets.

Risk and Exploitability

The CVSS score of 7.5 indicates high severity. The vulnerability can be exploited remotely by sending forged UDP packets to the OpenAM RADIUS port, requiring only basic network connectivity to the service. Because it does not require shared secrets or complex cryptographic operations, the attack path is straightforward. The resulting authenticated session gives the attacker the privileges associated with the impersonated user. While the EPSS score is not available, the simplicity of the exploit and the high severity suggest a meaningful risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to OpenAM 16.1.1 or newer to apply the vendor patch that validates RADIUS responses.
  • Disable the RADIUS authentication module on any login chains that are not required or restrict its use to trusted internal networks.
  • Implement firewall rules to block unsolicited UDP traffic toward the RADIUS port used by OpenAM.
  • If an upgrade cannot be performed immediately, consider removing the RADIUS module from the deployment until a fix is applied.

Generated by OpenCVE AI on October 30, 2026 at 19:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-386j-6m86-78f9 OpenAM: Unauthenticated Authentication Bypass via RADIUS Spoofing
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Openidentityplatform
Openidentityplatform openam
Vendors & Products Openidentityplatform
Openidentityplatform openam
Type Values Removed Values Added
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.
Title OpenAM Authentication Bypass via RADIUS Spoofing
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 5, 2026, 2:27 AM
Reserved
May 14, 2026, 8:42 PM
Status
Awaiting Analysis
Published
Oct 30, 2026, 7:18 PM
Modified
Nov 5, 2026, 3:17 AM