CVE-2025-21481

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-24. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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

Memory corruption while performing private key encryption in trusted application.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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%
Automatability0% × 15%
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

Published

September 24, 2025

Last Modified

September 25, 2025

Advisory Details (1)

Auto-updated Sep 27, 2026
No fix on record yet.
generic

Qualcomm Documentation

https://docs.qualcomm.com/product/publicresources/securitybulletin/september-2025-bulletin.html

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-21481?
CVE-2025-21481 is a high vulnerability published on September 24, 2025. Memory corruption while performing private key encryption in trusted application.
When was CVE-2025-21481 disclosed?
CVE-2025-21481 was first published on September 24, 2025, with the most recent update on September 25, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-21481 actively exploited?
CVE-2025-21481 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21481?
CVE-2025-21481 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-21481?
No fix for CVE-2025-21481 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-21481

Explore →

Is Your Infrastructure Affected by CVE-2025-21481?

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

Book a Demo →Browse All CVEs