CVE-2025-59600

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-02. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

Memory Corruption when adding user-supplied data without checking available buffer space.

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

Published

March 2, 2026

Last Modified

June 17, 2026

Advisory Details (1)

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

Qualcomm Documentation

https://docs.qualcomm.com/product/publicresources/securitybulletin/march-2026-bulletin.html

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 19× 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-19 15:42 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:07 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:11 UTCEPSS rescore
  10. 2026-09-01 13:53 UTCEPSS rescore
  11. 2026-08-30 19:16 UTCEPSS rescore
  12. 2026-08-28 21:40 UTCEPSS rescore
  13. 2026-08-27 14:24 UTCEPSS rescore
  14. 2026-08-26 14:45 UTCEPSS rescore
  15. 2026-08-25 13:48 UTCEPSS rescore
  16. 2026-08-24 14:16 UTCEPSS rescore
  17. 2026-08-23 00:18 UTCEPSS rescore
  18. 2026-08-21 23:48 UTCEPSS rescore
  19. 2026-08-20 22:54 UTCEPSS rescore
  20. 2026-08-19 17:03 UTCEPSS rescore
  21. 2026-08-16 14:55 UTCEPSS rescore
  22. 2026-08-16 02:13 UTCEPSS rescore
  23. 2026-08-15 01:29 UTCEPSS rescore
  24. 2026-08-14 21:32 UTCGHSA enrichment
  25. 2026-08-14 08:44 UTCGHSA enrichment
Show 27 more
  1. 2026-08-13 00:36 UTCGHSA enrichment
  2. 2026-08-11 23:26 UTCEG score recompute
  3. 2026-08-11 23:26 UTCGHSA enrichment
  4. 2026-08-11 13:42 UTCEPSS rescore
  5. 2026-08-11 06:00 UTCGHSA enrichment
  6. 2026-08-10 09:58 UTCGHSA enrichment
  7. 2026-08-09 21:11 UTCEG score recompute
  8. 2026-08-09 21:11 UTCGHSA enrichment
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-09 08:22 UTCEG score recompute
  11. 2026-08-09 08:22 UTCGHSA enrichment
  12. 2026-08-08 16:36 UTCEPSS rescore
  13. 2026-08-08 09:07 UTCGHSA enrichment
  14. 2026-08-07 20:19 UTCEG score recompute
  15. 2026-08-07 20:19 UTCGHSA enrichment
  16. 2026-08-07 16:26 UTCEPSS rescore
  17. 2026-08-06 13:46 UTCEPSS rescore
  18. 2026-08-06 02:51 UTCEG score recompute
  19. 2026-08-06 02:51 UTCGHSA enrichment
  20. 2026-08-05 19:16 UTCEPSS rescore
  21. 2026-08-04 10:37 UTCEPSS rescore
  22. 2026-08-04 04:37 UTCGHSA enrichment
  23. 2026-08-02 19:12 UTCEG score recompute
  24. 2026-08-02 19:12 UTCGHSA enrichment
  25. 2026-07-28 15:35 UTCEPSS rescore
  26. 2026-07-27 13:59 UTCEG score recompute
  27. 2026-07-27 13:59 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2025-59600?
CVE-2025-59600 is a high vulnerability published on March 2, 2026. Memory Corruption when adding user-supplied data without checking available buffer space.
When was CVE-2025-59600 disclosed?
CVE-2025-59600 was first published in the National Vulnerability Database on March 2, 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-59600 actively exploited?
CVE-2025-59600 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 99.9% of all scored CVEs.
What is the CVSS score of CVE-2025-59600?
CVE-2025-59600 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-59600?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-59600, 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-59600

Explore →

Is Your Infrastructure Affected by CVE-2025-59600?

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

Start Free Scan →Browse All CVEs