# CVE-2025-2713: Improper File Permission Handling in Google gVisor runsc

> Unprivileged users can escalate privileges and read restricted files in gVisor runsc due to improper permission handling during process initialization.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2025
- **Updated:** 8 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-2713, GHSA-4fj4-9m67-3mj3, UBUNTU-CVE-2025-2713

## What is CVE-2025-2713?

CVE-2025-2713 is a medium-severity vulnerability in Google gVisor, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-2713?

It affects 1 product.


Products: Google Gvisor.

## How do I fix CVE-2025-2713?

Apply the vendor's patch.

## Is CVE-2025-2713 being exploited?

There is no known exploitation of CVE-2025-2713 in the wild and no public exploit code.

## Other vulnerabilities in Google gVisor

- [CVE-2018-19333](https://insights.sbomify.com/CVE-2018-19333/): Use after free in n/a (critical 9.8)
- [CVE-2018-16359](https://insights.sbomify.com/CVE-2018-16359/): Path traversal in n/a (medium 6.8)
- [CVE-2024-10026](https://insights.sbomify.com/CVE-2024-10026/): Improved Seeding and Hashing In gVisor (medium 6.3)
- [CVE-2024-10603](https://insights.sbomify.com/CVE-2024-10603/): Information disclosure in gVisor (medium 6.3)
- [CVE-2018-20168](https://insights.sbomify.com/CVE-2018-20168/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2713 and fix it if it is affected.

What it is: CVE-2025-2713 is a medium-severity vulnerability in Google gVisor, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2713 in the wild and no public exploit code.

Affected product: Google gVisor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2713/ (Markdown: https://insights.sbomify.com/CVE-2025-2713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2713
- OSV: https://osv.dev/vulnerability/CVE-2025-2713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2713/
Summaries are generated and may contain mistakes; the official description above is the record.