# CVE-2026-84669: Path traversal in Jenkins Allure Plugin

> Attackers with read permissions can read arbitrary files on the Jenkins controller via a path traversal flaw in the Allure Plugin.

- **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:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-5jp6-w4g2-655c

## What is CVE-2026-84669?

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

### Official description

A path traversal vulnerability in Jenkins Allure Plugin 2.35.2 and earlier allows attackers with Item/Read permission on jobs that publish Allure report results to read arbitrary files on the Jenkins controller's file system.

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

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


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

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

## Is CVE-2026-84669 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84669 is a high-severity path traversal vulnerability in Jenkins Allure 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-84669 in the wild and no public exploit code.

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

## Sources

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

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