# CVE-2026-92812: Decap CMS < 3.11.0 Path Traversal via Sibling Directory Prefix Matching

> Attackers can bypass containment guards to read, write, or delete files in sibling directories outside the intended repository root.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-5rrq-v82w-qpfr, GHSA-fjm6-6gxh-mvf2

## What is CVE-2026-92812?

CVE-2026-92812 is a critical path traversal vulnerability in decaporg decap-cms, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Decap CMS before 3.11.0 contains a path traversal vulnerability in the local proxy containment guard that uses plain string prefix comparison without path separator validation. Attackers can access sibling directories whose names begin with the repository directory name to read, write, or delete files outside the intended repository root.

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

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


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

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

## Is CVE-2026-92812 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92812 is a critical path traversal vulnerability in decaporg decap-cms, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92812 exists.

Affected product: decaporg decap-cms. 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-92812/ (Markdown: https://insights.sbomify.com/CVE-2026-92812/index.md)
```

## Sources

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

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