Loading vulnerability…
Jenkins 2.274 and earlier and Jenkins LTS 2.263.1 and earlier insufficiently validate agent names supplied by users with Agent/Configure permission. A crafted agent name can traverse the intended storage location and overwrite unrelated Jenkins configuration files, including the global configuration. Jenkins 2.275 and LTS 2.263.2 introduced validation requiring agent names to be valid item names.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced by this OpenShift Container Platform security advisory; no further details are provided in the content.
A Jenkins path-traversal vulnerability involving agent names.
A path-traversal vulnerability in Jenkins agent names.
An important Jenkins improper-input-validation/path-traversal flaw allowing users with Agent/Configure permission to select agent names that overwrite the global config.xml file, threatening confidentiality, integrity, and availability.
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.