CVE-2025-5245

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2025-05-27. the CNA's CVSS baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vuldb, epss, ghsa
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

A vulnerability classified as critical has been found in GNU Binutils up to 2.44. This affects the function debug_type_samep of the file /binutils/debug.c of the component objdump. The manipulation leads to memory corruption. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.

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

Published

May 27, 2025

Last Modified

July 14, 2026

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(5)

What is CVE-2025-5245?
CVE-2025-5245 is a medium vulnerability published on May 27, 2025. A vulnerability classified as critical has been found in GNU Binutils up to 2.44. This affects the function debugtypesamep of the file /binutils/debug.c of the component objdump. The manipulation leads to memory corruption. Local access is required to approach this attack. The exploit has been…
When was CVE-2025-5245 disclosed?
CVE-2025-5245 was first published in the National Vulnerability Database on May 27, 2025, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-5245 actively exploited?
CVE-2025-5245 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 79.4% of all scored CVEs.
What is the CVSS score of CVE-2025-5245?
CVE-2025-5245 has a CVSS v4.0 base score of 5.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-5245?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-5245, 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-2025-5245

Explore →

Is Your Infrastructure Affected by CVE-2025-5245?

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