Loading vulnerability…
Jenkins Credentials Binding Plugin 719.v80e905ef14eb_ and earlier does not properly sanitize file names associated with file and zip file credentials. This allows an attacker who is able to provide credentials to a job to influence the filesystem path used when those credentials are materialized on the Jenkins node, resulting in arbitrary file write outside the intended directory. The issue is a path traversal flaw in the plugin’s handling of file and zip file credential names. In environments where Jenkins permits a low-privileged user to configure file or zip file credentials for a job that runs on the built-in node, the arbitrary file write can be leveraged to achieve remote code execution.
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.
7 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.