Loading vulnerability…
Jenkins 2.540 and earlier, and Jenkins LTS 2.528.2 and earlier, store build authorization tokens unencrypted in job configuration files (config.xml) on the Jenkins controller. As a result, sensitive build authorization tokens are recoverable in plaintext by users who have Item/Extended Read permission and can read job configuration, or by anyone with access to the Jenkins controller file system. The advisory also notes related UI exposure of these tokens, but this CVE specifically concerns their unencrypted storage at rest in job config.xml files.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Item/Extended Read permission to only fully trusted users, minimize and audit access to the Jenkins controller file system, and review exposure of job config.xml files through backups, exports, or administrative tooling. Consider rotating existing build authorization tokens after remediation, especially if unauthorized access to job configuration or controller storage may have occurred.Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.