Token disclosure via plaintext job configuration storage
Published Sep 2, 2026 · Updated Sep 2, 2026
Missing encryption in Jenkins Project Parameterized Remote Trigger 3.2.2 and earlier allows remote authenticated users to read stored tokens. The plugin serializes build authorization tokens as plaintext values in each affected job's config.xml file on the Jenkins controller. Item/Extended Read permission or controller filesystem access is required, and exposure is limited to tokens stored for configured remote builds.
Summary
What happened
Missing encryption in Jenkins Project Parameterized Remote Trigger 3.2.2 and earlier allows remote authenticated users to read stored tokens. The plugin serializes build authorization tokens as plaintext values in each affected job's config.xml file on the Jenkins controller. Item/Extended Read permission or controller filesystem access is required, and exposure is limited to tokens stored for configured remote builds.
The record
- CVE
- CVE-2026-84676
- Published
- Sep 2, 2026
- Updated
- Sep 2, 2026
- Vendor
- Jenkins Project
- Product
- Parameterized Remote Trigger
- Classifications
- CWE-311, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 2, 2026CVE publishedPublication date reported by the CVE source.
- Sep 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo