# CVE-2026-121549: nnn through 5.3 Insecure Temporary File Symlink Overwrite via pdfread and nuke Plugins


- **Severity:** Medium 4.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-121549, GHSA-p7pp-h3gc-2v7m, UBUNTU-CVE-2026-121549

## What is CVE-2026-121549?

CVE-2026-121549 is a medium-severity vulnerability in jarun nnn, published on 3 Nov 2026. 

### Official description

nnn through 5.3 contains an insecure temporary file vulnerability in the pdfread and nuke plugins that allows local attackers to overwrite files by exploiting predictable paths in /tmp. Attackers can pre-create a symlink at the name-derived or PID-derived path so the victim's plugin truncates and overwrites any file the victim can write.

Weakness: CWE-377 (DEPRECATED: Insecure Temporary File)

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


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

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

## Is CVE-2026-121549 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121549 is a medium-severity vulnerability in jarun nnn, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121549 exists.

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

## Sources

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

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