Jenkins is widely used in CI/CD; a controller file-read by authenticated users can expose secrets and compromise pipelines across organizations.
CVE-2026-84669
Path traversal in Allure Jenkins plugin allows reading arbitrary controller files.
Is CVE-2026-84669 being exploited?
Not confirmed. CVE-2026-84669 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-84669?
CVE-2026-84669 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-84669?
Yes. A fix has been recorded for CVE-2026-84669. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84669 affect?
CVE-2026-84669 affects Jenkins Allure Plugin <= 2.35.2, Jenkins controller (file system). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84669?
Upgrade Allure Plugin to >2.35.2 and restrict Item/Read permissions on jobs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users with Item/Read on affected jobs can read arbitrary files on the Jenkins controller, exposing secrets and configs.
Immediate action required
- affected<= 2.35.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.