# CVE-2025-62356: Path traversal in Qodo Gen

> Attackers can read arbitrary local files on user systems via path traversal in Qodo Gen IDE, potentially exposing sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2025
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-8ff7-83pv-r7gf

## What is CVE-2025-62356?

CVE-2025-62356 is a high-severity path traversal vulnerability in Qodo Gen, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability in all versions of the Qodo Qodo Gen IDE enables a threat actor to read arbitrary local files in and outside of current projects on an end user’s system. The vulnerability can be reached directly and through indirect prompt injection.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

No fix has been published for CVE-2025-62356 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-62356 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62356 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62356 is a high-severity path traversal vulnerability in Qodo Gen, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62356 exists.

Affected product: Qodo Gen. 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-62356/ (Markdown: https://insights.sbomify.com/CVE-2025-62356/index.md)
```

## Sources

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

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