CVE-2024-3596

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2024-07-09. NVD baseline CVSS 9.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 15%CVSS: 9.0Exploit: NoneExposed: 0

A fix is available — apply it.

RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature.

CVSS v3
9.0
EG Score
9.0(medium)
EPSS
96.3%
KEV
Not listed

Published

July 9, 2024

Last Modified

June 9, 2026

Advisory Details (8)

Auto-updated May 12, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

draft-ietf-radext-deprecating-radius-09 - Deprecating Insecure Practices in RADIUS

https://datatracker.ietf.org/doc/draft-ietf-radext-deprecating-radius/
generic

oss-security - CVE-2024-3596: RADIUS/UDP vulnerable to improved MD5 collision attack

http://www.openwall.com/lists/oss-security/2024/07/09/4
generic🟡 PoC Available

BLAST RADIUS

https://www.blastradius.fail/
generic

RFC 2865 - Remote Authentication Dial In User Service (RADIUS)

https://datatracker.ietf.org/doc/html/rfc2865

Vendor Advisories for CVE-2024-3596(2)

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

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibfreeradius3 (3.2.5+dfsg-3~ubuntu24.04.1) @ noble2026-05-22ubuntu
ubuntulibkrb5support0 (1.21.3-3ubuntu0.1) @ oracular2026-05-22ubuntu
redhatrhoai/odh-kf-notebook-controller-rhel8:sha256:3e670a110eb3a6e59c6051b485bc88d39cb921b31854f36073f2088d52b53ce12024-12-05redhat
redhatkrb5-0:1.21.1-2.el9_4.12024-11-13redhat
redhatkrb5-0:1.21.1-4.el9_52024-11-12redhat
redhatkrb5-0:1.18.2-30.el8_102024-11-05redhat
redhatkrb5-0:1.18.2-16.el8_6.22024-11-04redhat
redhatkrb5-0:1.18.2-9.el8_4.22024-11-04redhat
redhatkrb5-0:1.15.1-55.el7_9.32024-11-04redhat
redhatkrb5-0:1.18.2-26.el8_8.32024-11-04redhat
redhatkrb5-0:1.17-19.el8_2.22024-11-04redhat
redhatkrb5-0:1.19.1-16.el9_0.22024-10-29redhat
redhatkrb5-0:1.20.1-9.el9_2.22024-10-24redhat
redhatfreeradius:3.0-8100020230904084920.69ef70f82024-07-31redhat
redhatfreeradius-0:3.0.21-40.el9_42024-07-31redhat
redhatfreeradius-0:3.0.20-1.el7_9.12024-07-30redhat
redhatfreeradius:3.0-8020020240726095340.ce27ea5e2024-07-30redhat
redhatfreeradius-0:3.0.21-26.el9_0.12024-07-30redhat
redhatfreeradius:3.0-8040020240719063921.9ab73fbf2024-07-25redhat
redhatfreeradius:3.0-8060020240719034751.830b6f112024-07-24redhat
redhatfreeradius-0:3.0.21-38.el9_2.22024-07-24redhat
redhatfreeradius:3.0-8080020240719112231.b012cf7d2024-07-24redhat

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.

Weakness Classification(2)

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

Additional Vendor Advisories

(21)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 101 total refreshes for this CVE.

  1. 2026-07-15 16:56 UTCEPSS rescore
  2. 2026-07-15 16:56 UTCEPSS rescore
  3. 2026-07-15 01:59 UTCEPSS rescore
  4. 2026-07-15 01:59 UTCEPSS rescore
  5. 2026-07-13 22:29 UTCEPSS rescore
  6. 2026-07-12 05:45 UTCEPSS rescore
  7. 2026-07-12 05:45 UTCEPSS rescore
  8. 2026-07-11 08:26 UTCEPSS rescore
  9. 2026-07-11 03:41 UTCOSV refresh
  10. 2026-07-09 19:09 UTCEPSS rescore
  11. 2026-07-09 19:09 UTCEPSS rescore
  12. 2026-07-08 15:14 UTCEPSS rescore
  13. 2026-07-07 13:45 UTCEPSS rescore
  14. 2026-07-06 02:22 UTCEPSS rescore
  15. 2026-07-06 02:22 UTCEPSS rescore
  16. 2026-07-04 06:30 UTCEPSS rescore
  17. 2026-07-01 15:05 UTCEPSS rescore
  18. 2026-06-30 23:21 UTCEPSS rescore
  19. 2026-06-30 23:21 UTCEPSS rescore
  20. 2026-06-29 14:05 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 14:06 UTCEPSS rescore
  23. 2026-06-28 04:55 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-27 03:07 UTCEPSS rescore
Show 75 more
  1. 2026-06-27 03:07 UTCEPSS rescore
  2. 2026-06-25 13:49 UTCEPSS rescore
  3. 2026-06-24 14:04 UTCEPSS rescore
  4. 2026-06-24 14:04 UTCEPSS rescore
  5. 2026-06-23 21:32 UTCEPSS rescore
  6. 2026-06-23 21:32 UTCEPSS rescore
  7. 2026-06-22 14:25 UTCEPSS rescore
  8. 2026-06-22 14:25 UTCEPSS rescore
  9. 2026-06-22 11:02 UTCOSV refresh
  10. 2026-06-21 01:58 UTCEPSS rescore
  11. 2026-06-21 01:58 UTCEPSS rescore
  12. 2026-06-19 19:25 UTCEPSS rescore
  13. 2026-06-19 19:25 UTCEPSS rescore
  14. 2026-06-18 17:52 UTCEPSS rescore
  15. 2026-06-18 17:51 UTCEPSS rescore
  16. 2026-06-17 17:52 UTCEPSS rescore
  17. 2026-06-16 17:52 UTCEPSS rescore
  18. 2026-06-16 17:52 UTCEPSS rescore
  19. 2026-06-15 17:47 UTCEPSS rescore
  20. 2026-06-14 23:16 UTCEPSS rescore
  21. 2026-06-12 23:11 UTCEPSS rescore
  22. 2026-06-11 13:59 UTCEPSS rescore
  23. 2026-06-10 22:17 UTCEPSS rescore
  24. 2026-06-10 13:21 UTCEPSS rescore
  25. 2026-06-07 15:24 UTCEPSS rescore
  26. 2026-06-07 15:24 UTCEPSS rescore
  27. 2026-06-06 13:46 UTCEPSS rescore
  28. 2026-06-06 13:46 UTCEPSS rescore
  29. 2026-06-05 22:46 UTCEPSS rescore
  30. 2026-06-05 22:46 UTCEPSS rescore
  31. 2026-06-05 06:09 UTCEPSS rescore
  32. 2026-06-05 06:09 UTCEPSS rescore
  33. 2026-06-04 15:09 UTCOSV refresh
  34. 2026-06-04 13:11 UTCEPSS rescore
  35. 2026-06-04 13:11 UTCEPSS rescore
  36. 2026-06-02 20:12 UTCEPSS rescore
  37. 2026-06-01 13:51 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-05-31 22:30 UTCEPSS rescore
  40. 2026-05-31 22:30 UTCEPSS rescore
  41. 2026-05-31 00:15 UTCEPSS rescore
  42. 2026-05-31 00:15 UTCEPSS rescore
  43. 2026-05-29 13:43 UTCEPSS rescore
  44. 2026-05-28 13:44 UTCEPSS rescore
  45. 2026-05-28 13:44 UTCEPSS rescore
  46. 2026-05-28 13:44 UTCEPSS rescore
  47. 2026-05-27 13:40 UTCEPSS rescore
  48. 2026-05-27 13:40 UTCEPSS rescore
  49. 2026-05-27 13:40 UTCEPSS rescore
  50. 2026-05-26 13:43 UTCEPSS rescore
  51. 2026-05-26 13:43 UTCEPSS rescore
  52. 2026-05-26 07:18 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-22 21:16 UTCEPSS rescore
  56. 2026-05-22 21:16 UTCEPSS rescore
  57. 2026-05-22 21:16 UTCEPSS rescore
  58. 2026-05-22 21:16 UTCEPSS rescore
  59. 2026-05-22 00:27 UTCEG score recompute
  60. 2026-05-22 00:27 UTCVendor advisory
  61. 2026-05-22 00:26 UTCGHSA enrichment
  62. 2026-05-21 22:42 UTCEPSS rescore
  63. 2026-05-21 22:42 UTCEPSS rescore
  64. 2026-05-20 22:37 UTCEPSS rescore
  65. 2026-05-20 22:37 UTCEPSS rescore
  66. 2026-05-20 22:37 UTCEPSS rescore
  67. 2026-05-20 22:37 UTCEPSS rescore
  68. 2026-05-20 11:21 UTCEPSS rescore
  69. 2026-05-20 11:21 UTCEPSS rescore
  70. 2026-05-20 11:21 UTCEPSS rescore
  71. 2026-05-20 11:21 UTCEPSS rescore
  72. 2026-05-20 11:21 UTCEPSS rescore
  73. 2026-05-18 21:30 UTCEPSS rescore
  74. 2026-05-18 21:30 UTCEPSS rescore
  75. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCalperenugurlu/CVE-2024-3596-Detector
    First seen Jul 9, 2024
    Open source ↗

Frequently asked(5)

What is CVE-2024-3596?
CVE-2024-3596 is a critical vulnerability published on July 9, 2024. RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature.
When was CVE-2024-3596 disclosed?
CVE-2024-3596 was first published in the National Vulnerability Database on July 9, 2024, with the most recent update on June 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-3596 actively exploited?
CVE-2024-3596 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-3596?
CVE-2024-3596 has a CVSS v3.1 base score of 9.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2024-3596?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-3596, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-3596

Explore →

Is Your Infrastructure Affected by CVE-2024-3596?

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