# CVE-2026-84666: Path traversal in Jenkins Job Configuration History Plugin

> Attackers can overwrite history recording configuration via Stapler data binding to redirect storage to arbitrary directories and modify settings.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 2 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-9prm-5833-4v96

## What is CVE-2026-84666?

CVE-2026-84666 is a medium-severity path traversal vulnerability in Jenkins Job Configuration History Plugin, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Job Configuration History Plugin 1367.vc8fa_b_15101dc and earlier allows overwriting the plugin's history recording configuration through Stapler data binding, allowing attackers to redirect history storage to an attacker-specified directory and modify history recording settings.

Weakness: CWE-494 (Download of Code Without Integrity Check), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-84666 being exploited?

There is no known exploitation of CVE-2026-84666 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84666 is a medium-severity path traversal vulnerability in Jenkins Job Configuration History Plugin, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84666 in the wild and no public exploit code.

Affected product: Jenkins Job Configuration History Plugin. 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-84666/ (Markdown: https://insights.sbomify.com/CVE-2026-84666/index.md)
```

## Sources

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

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