Loading vulnerability…
Jenkins Parameterized Remote Trigger Plugin 3.2.2 and earlier stores configured remote-trigger tokens without encryption in job configuration data on the Jenkins controller. Consequently, users granted Item/Extended Read permission, or principals with filesystem access to the controller, can recover these tokens.
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.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A plaintext credential-storage vulnerability in Jenkins Parameterized Remote Trigger Plugin 3.2.2 and earlier. Tokens stored in job config.xml files on the Jenkins controller can be disclosed to users with Item/Extended Read permission or filesystem access to the controller.
A Jenkins plugin vulnerability referenced by the 2026-09-02 Jenkins security advisory; technical details are not provided.
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.