CVE-2025-69646

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-03-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Elevated
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debug_rnglists data. A logic error in the handling of the debug_rnglists header can cause objdump to repeatedly print the same warning message and fail to terminate, resulting in an unbounded logging loop until the process is interrupted. The issue was observed in binutils 2.44. A local attacker can exploit this vulnerability by supplying a malicious input file, leading to excessive CPU and I/O usage and preventing completion of the objdump analysis.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity55% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

March 6, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

33638 – objdump enters infinite warning-print loop on crafted input

https://sourceware.org/bugzilla/show_bug.cgi?id=33638

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatbinutils-main-2.45.1-5.hum12026-04-08redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
binutils2.35.2-2 ... 2.47-2 (213 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
binutils2.40-2 ... 2.47.50.20260901-1 (122 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
binutils2.44-3 ... 2.47.50.20260901-1 (48 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
binutils2.44-3 ... 2.45.90.20260201-1 (33 versions)2.46-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 24× 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.

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

Frequently asked(5)

What is CVE-2025-69646?
CVE-2025-69646 is a medium vulnerability published on March 6, 2026. Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debugrnglists data. A logic error in the handling of the debugrnglists header can cause objdump to repeatedly print the same warning message and fail to terminate, resulting in an…
When was CVE-2025-69646 disclosed?
CVE-2025-69646 was first published in the National Vulnerability Database on March 6, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-69646 actively exploited?
CVE-2025-69646 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.0% of all scored CVEs.
What is the CVSS score of CVE-2025-69646?
CVE-2025-69646 has a CVSS v3.1 base score of 5.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-69646?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-69646, 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-69646

Explore →

Is Your Infrastructure Affected by CVE-2025-69646?

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