# CVE-2026-51873: Path traversal in n/a

> Attackers can write files outside the intended project workspace via directory traversal in Devika's code saving function.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-f262-872p-52hv

## What is CVE-2026-51873?

CVE-2026-51873 is a high-severity path traversal vulnerability in n/a, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Devika v1.0 is vulnerable to Directory Traversal in the Coder.save_code_to_project function, which allows attackers to write files outside the intended project workspace.

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

## Which versions are affected by CVE-2026-51873?


## How do I fix CVE-2026-51873?

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

## Is CVE-2026-51873 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-51873 and fix it if it is affected.

What it is: CVE-2026-51873 is a high-severity path traversal vulnerability in n/a, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51873 exists.

Affected product: n/a. 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-2026-51873/ (Markdown: https://insights.sbomify.com/CVE-2026-51873/index.md)
```

## Sources

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

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