CVE-2025-2713: Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling

Q: How do I fix CVE-2025-2713?

gvisor: upgrade to 20240325.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-2713 being exploited?

CVE-2025-2713 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-2713 affect?

CVE-2025-2713 affects gvisor. Severity is high (CVSS 7.8). 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 initia

Routine

HIGH 7.8UPGRADE

CVE-2025-2713 is a high-severity flaw (CVSS 7.8) affecting gvisor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 100%)
CISA exploited list	No
Weakness	CWE-266
Published	2025-03-28
Last modified	2026-06-17

Publisher (CNA): Google Inc. · Vendor: google

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-28 16:15 UTCPublished CVE record published
2026-06-17 09:07 UTCUpdated Record last modified

google gvisor UPGRADE

Affected: < 20240325.0

Fixed in: 20240325.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy gvisor || rpm -q gvisor || gvisor --version

2. UPGRADE to 20240325.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gvisor

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gvisor

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-2713?

gvisor: upgrade to 20240325.0. Exact commands for each OS are on this page.

Is CVE-2025-2713 being exploited?

CVE-2025-2713 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-2713 affect?

CVE-2025-2713 affects gvisor. Severity is high (CVSS 7.8). 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 initia

How urgent is CVE-2025-2713?

Priority 27/100. High severity

Related CVEs

CVE-2024-10603 MEDIUM 5.3 UPGRADE Weaknesses in the generation of TCP/UDP source ports and some other header values in Google's gVisor allowed t
CVE-2024-10026 MEDIUM 5.3 UPGRADE A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to

References

← Back to latest CVEs