CVE-2025-48641

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-03-02. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.0EG
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.0Exploit: None knownExposed: 0

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

In multiple functions of Nfc.h, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity70% × 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 6, 2026
No patch confirmed yet.
generic

Android Security Bulletin—March 2026  |  Android Open Source Project

https://source.android.com/docs/security/bulletin/2026/2026-03-01

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 1× in last 7d / 6× 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-16 14:07 UTCEPSS rescore
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-01 04:38 UTCEPSS rescore
  5. 2026-08-26 14:45 UTCEPSS rescore
  6. 2026-08-24 14:16 UTCEPSS rescore
  7. 2026-08-14 21:02 UTCGHSA enrichment
  8. 2026-08-14 08:43 UTCGHSA enrichment
  9. 2026-08-13 00:34 UTCGHSA enrichment
  10. 2026-08-11 23:24 UTCGHSA enrichment
  11. 2026-08-11 05:58 UTCGHSA enrichment
  12. 2026-08-10 08:03 UTCGHSA enrichment
  13. 2026-08-09 19:28 UTCGHSA enrichment
  14. 2026-08-09 08:20 UTCEG score recompute
  15. 2026-08-09 08:20 UTCGHSA enrichment
  16. 2026-08-08 16:36 UTCEPSS rescore
  17. 2026-08-08 07:25 UTCGHSA enrichment
  18. 2026-08-07 20:17 UTCGHSA enrichment
  19. 2026-08-06 02:50 UTCEG score recompute
  20. 2026-08-06 02:50 UTCGHSA enrichment
  21. 2026-08-05 19:16 UTCEPSS rescore
  22. 2026-08-04 04:36 UTCGHSA enrichment
  23. 2026-08-02 19:11 UTCEG score recompute
  24. 2026-08-02 19:11 UTCGHSA enrichment
  25. 2026-07-27 13:57 UTCEG score recompute
Show 1 more
  1. 2026-07-27 13:57 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2025-48641?
CVE-2025-48641 is a high vulnerability published on March 2, 2026. In multiple functions of Nfc.h, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2025-48641 disclosed?
CVE-2025-48641 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-48641 actively exploited?
CVE-2025-48641 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 100.0% of all scored CVEs.
What is the CVSS score of CVE-2025-48641?
CVE-2025-48641 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2025-48641?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-48641, 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-48641

Explore →

Is Your Infrastructure Affected by CVE-2025-48641?

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