How severe is CVE-2025-2713?

CVE-2025-2713 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-2713 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-2713?

CVE-2025-2713 affects Google Gvisor. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-2713?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-2713 have an EU (EUVD) identifier?

Yes. CVE-2025-2713 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-8644.

When was CVE-2025-2713 published?

CVE-2025-2713 was published on 2025-03-28 and last updated on 2026-06-17.

CVE-2025-2713

CVE-2025-2713 is a high-severity vulnerability in Google Gvisor with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-266.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v4: 6.8
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-8644
Weakness: CWE-266
Affected product: Google Gvisor
Published: 2025-03-28
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2025-2713?: 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.
How severe is CVE-2025-2713?: CVE-2025-2713 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-2713 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-2713?: CVE-2025-2713 affects Google Gvisor. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-2713?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-2713 have an EU (EUVD) identifier?: Yes. CVE-2025-2713 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-8644.
When was CVE-2025-2713 published?: CVE-2025-2713 was published on 2025-03-28 and last updated on 2026-06-17.

References

https://github.com/google/gvisor/commit/586c38d70081b13b2ed494cef48e99b93956843e

Affected products (1)

cpe:2.3:a:google:gvisor:*:*:*:*:*:*:*:*

More vulnerabilities in Google Gvisor

CVE-2018-19333 — Critical (CVSS 9.8): pkg/sentry/kernel/shm/shm.go in Google gVisor before 2018-11-01 allows attackers to overwrite memory locations in…
CVE-2018-16359 — Medium (CVSS 6.8): Google gVisor before 2018-08-23, within the seccomp sandbox, permits access to the renameat system call, which allows…
CVE-2018-20168 — Medium (CVSS 5.5): Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact, which…
CVE-2024-10603 — Medium (CVSS 5.3): Weaknesses in the generation of TCP/UDP source ports and some other header values in Google's gVisor allowed them to be…
CVE-2024-10026 — Medium (CVSS 5.3): A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to calculate…
CVE-2023-7258 — Medium (CVSS 4.8): A denial of service exists in Gvisor Sandbox where a bug in reference counting code in mount point tracking could lead…

All CVEs affecting Google Gvisor →

Other CWE-266 (Incorrect Privilege Assignment) vulnerabilities

CVE-2026-23800 — Critical (CVSS 10.0): Incorrect Privilege Assignment vulnerability in Modular DS modular-connector allows Privilege Escalation.This issue…
CVE-2025-41115 — Critical (CVSS 10.0): SCIM provisioning was introduced in Grafana Enterprise and Grafana Cloud in April to improve how organizations manage…
CVE-2024-9479 — Critical (CVSS 10.0): Improper Privilege Management vulnerability in upKeeper Solutions upKeeper Instant Privilege Access allows Privilege…
CVE-2024-9478 — Critical (CVSS 10.0): Improper Privilege Management vulnerability in upKeeper Solutions upKeeper Instant Privilege Access allows Privilege…
CVE-2026-42368 — Critical (CVSS 9.9): A privilege escalation vulnerability exists in the Web Interface functionality of GeoVision LPC2011/LPC2211 1.10. A…
CVE-2026-32922 — Critical (CVSS 9.9): OpenClaw before 2026.3.11 contains a privilege escalation vulnerability in device.token.rotate that allows callers with…

Browse all CWE-266 (Incorrect Privilege Assignment) vulnerabilities →