CVE-2026-46560

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-114320 (ENISA EUVD) · GHSA-386j-6m86-78f9 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 25, 2026

Last Modified

November 5, 2026

Advisory Details (3)

Auto-updated Oct 30, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available

16.1.1

Patch available: OpenIdentityPlatform/OpenAM 16.1.1

https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.1.1
GitHub commit

commit 5a0c10eccd1d (OpenIdentityPlatform/OpenAM)

Fix landed in OpenIdentityPlatform/OpenAM commit 5a0c10eccd1d — awaiting tagged release

https://github.com/OpenIdentityPlatform/OpenAM/commit/5a0c10eccd1d45aaeb5575bbe7f7b1d01964a775
GitHub advisoryMentions a patch (unverified)

OpenAM Authentication Bypass via RADIUS Spoofing · Advisory · OpenIdentityPlatform/OpenAM · GitHub

Affected: version 16.1.1.

https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-386j-6m86-78f9

Vendor Advisories for CVE-2026-46560(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.openidentityplatform.openam:openam-radius @ 16.1.1 (fixes < 16.1.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.openidentityplatform.openam:openam-radius14.5.2 ... 16.1.0 (40 versions)
  • every version up to 16.1.1: fixed in 16.1.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-11-12 08:33 UTCEchelonGraph re-scored
  4. 2026-11-12 08:33 UTCGHSA enrichmentGHSA-386j-6m86-78f9 · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-11-05 03:27 UTCEchelonGraph re-scored
  13. 2026-11-05 03:27 UTCGHSA enrichmentGHSA-386j-6m86-78f9 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-05 02:34 UTCEchelonGraph re-scored
  15. 2026-11-05 02:34 UTCGHSA enrichmentGHSA-386j-6m86-78f9 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-11-01 07:48 UTCGHSA enrichmentGHSA-386j-6m86-78f9 · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-01 07:48 UTCEchelonGraph re-scored
  22. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-30 21:02 UTCENISA EUVD ID recordedEUVD-2026-114320 · Source: ENISA EUVD
  24. 2026-10-30 19:28 UTCEchelonGraph re-scored
  25. 2026-10-25 14:25 UTCEchelonGraph re-scored
Show 9 more
  1. 2026-10-18 03:37 UTCEchelonGraph re-scored
  2. 2026-10-12 16:02 UTCEchelonGraph re-scored
  3. 2026-10-11 19:45 UTCEchelonGraph re-scored
  4. 2026-10-11 17:00 UTCEchelonGraph re-scored
  5. 2026-10-11 14:25 UTCEchelonGraph re-scored
  6. 2026-07-30 14:02 UTCEchelonGraph re-scored
  7. 2026-07-26 14:57 UTCEchelonGraph re-scored
  8. 2026-07-23 03:17 UTCEchelonGraph re-scored
  9. 2026-06-25 17:46 UTCEchelonGraph re-scored

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46560?
CVE-2026-46560 is a high-severity vulnerability; its CVE record was published on June 25, 2026. 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…
When was the CVE record for CVE-2026-46560 published?
The CVE record for CVE-2026-46560 was published on June 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-46560 actively exploited?
CVE-2026-46560 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46560?
CVE-2026-46560 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46560?
A fix for CVE-2026-46560 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46560 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46560

Explore →

Is Your Infrastructure Affected by CVE-2026-46560?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs