CVE-2025-4432

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 45% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw was found in Rust's Ring package. A panic may be triggered when overflow checking is enabled. In the QUIC protocol, this flaw allows an attacker to induce this panic by sending a specially crafted packet. It will likely occur unintentionally in 1 out of every 2**32 packets sent or received.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
54.9%
KEV
Not listed

Published

May 9, 2025

Last Modified

June 30, 2026

Advisory Details (7)

Auto-updated Jun 25, 2026
Patch available. Sources: redhat, github_commit, github_pr.
generic

RUSTSEC-2025-0009: ring: Some AES functions may panic when overflow checking is enabled. › RustSec Advisory Database

https://rustsec.org/advisories/RUSTSEC-2025-0009.html
github_pr

aes: Avoid unwanted overflow check when using u32::MAX as the counter.

Fix merged in briansmith/ring PR #2447 on 2025-03-05 — awaiting tagged release

https://github.com/briansmith/ring/pull/2447
github_commit

commit ec2d3cf1d91f (briansmith/ring)

Fix landed in briansmith/ring commit ec2d3cf1d91f — awaiting tagged release

https://github.com/briansmith/ring/commit/ec2d3cf1d91f148c84e4806b4f0b3c98f6df3b38
generic

ring/RELEASES.md at main · briansmith/ring · GitHub

https://github.com/briansmith/ring/blob/main/RELEASES.md#version-01712-2025-03-05
generic

GitHub - briansmith/ring: An experiment. · GitHub

https://github.com/briansmith/ring
redhat

2350655 – (CVE-2025-4432, GHSA-4p46-pwfr-66x6) CVE-2025-4432 ring: Some AES functions may panic when overflow checking is enabled in ring

https://bugzilla.redhat.com/show_bug.cgi?id=2350655
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2025-4432

Vendor Advisories for CVE-2025-4432(1)

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

Affected Packages

(2 across 2 ecosystems)
crates.io(1)
PackageVulnerable rangeFixed inDependents
ring—0.17.12—
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/briansmith/ring———

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 51× 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 131 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-4432?
CVE-2025-4432 is a medium vulnerability published on May 9, 2025. A flaw was found in Rust's Ring package. A panic may be triggered when overflow checking is enabled. In the QUIC protocol, this flaw allows an attacker to induce this panic by sending a specially crafted packet. It will likely occur unintentionally in 1 out of every 232 packets sent or received.
When was CVE-2025-4432 disclosed?
CVE-2025-4432 was first published in the National Vulnerability Database on May 9, 2025, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-4432 actively exploited?
CVE-2025-4432 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-4432?
CVE-2025-4432 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2025-4432?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-4432, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-4432

Explore →

Is Your Infrastructure Affected by CVE-2025-4432?

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

Start Free Scan →Browse All CVEs