CVE-2025-2713

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory published 2025-03-28. NVD baseline CVSS 7.8; sources differ by 0.0.

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

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

Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed unprivileged users to access restricted files. This occurred because the process initially ran with root-like permissions until the first fork.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.1%
KEV
Not listed

Published

March 28, 2025

Last Modified

September 26, 2025

References (1)

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-2713?
CVE-2025-2713 is a high vulnerability published on March 28, 2025. Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed unprivileged users to access restricted files. This occurred because the process initially ran with root-like permissions until the first fork.
When was CVE-2025-2713 disclosed?
CVE-2025-2713 was first published in the National Vulnerability Database on March 28, 2025, with the most recent update on September 26, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-2713 actively exploited?
CVE-2025-2713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-2713?
CVE-2025-2713 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-2713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-2713, 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-2713

Explore →

Is Your Infrastructure Affected by CVE-2025-2713?

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

Start Free Scan →Browse All CVEs