# CVE-2026-8274: npitre cramfs-tools Directory cramfsck.c do_directory path traversal

> Local attackers can exploit a path traversal flaw in cramfs-tools to read or modify files outside the intended directory.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-2x6r-r8j5-prxm, openSUSE-SU-2026:12210-1

## What is CVE-2026-8274?

CVE-2026-8274 is a medium-severity path traversal vulnerability in npitre cramfs-tools, published on 11 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability has been detected in npitre cramfs-tools up to 2.1. Affected is the function do_directory of the file cramfsck.c of the component Directory Handler. Such manipulation leads to path traversal. The attack can only be performed from a local environment. The exploit has been disclosed publicly and may be used. Upgrading to version 2.2 is able to address this issue. The name of the patch is 2fc492747115b24d8a07eddd27a2d45229cb273c. Upgrading the affected component is recommended.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cramfs-tools` | openSUSE:Tumbleweed | All versions | 2.2-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-8274 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8274 is a medium-severity path traversal vulnerability in npitre cramfs-tools, published on 11 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8274 exists.

Affected product: npitre cramfs-tools. 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-8274/ (Markdown: https://insights.sbomify.com/CVE-2026-8274/index.md)
```

## Sources

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

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