GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins Allure Plugin: path traversal lets Item/Read users read arbitrary controller files

CVE-2026-84669Control plane, storage & DevOpscurated

Impact

A path traversal in the Allure report path lets any user with Item/Read on a job that publishes Allure results read arbitrary files from the Jenkins controller filesystem. The controller's filesystem is where credentials.xml, the master key and secret files, SSH keys for the fleet and any cached kubeconfig live, so arbitrary file read is effectively credential disclosure for whatever the controller can reach - clusters, registries, storage. Item/Read is the permission handed to everyone who wants to look at test results, which makes the population of potential attackers the whole engineering org rather than a privileged subset. Affects Allure Plugin 2.35.2 and earlier.

Who can reach it

Any authenticated user holding Item/Read on a job that publishes Allure report results. No user interaction required.

What to do

Update the Allure Plugin past 2.35.2 and restart the controller; the record does not name the fixed release. If you believe it was exploited, rotate anything reachable from the controller filesystem - the credentials store, agent keys, registry tokens - because a plugin upgrade does not invalidate what was already read. Short CI outage.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.