Loading vulnerability…
CVE-2021-21606 is an improper input-validation flaw in Jenkins fingerprint metadata existence checks. Jenkins 2.274 and earlier and Jenkins LTS 2.263.1 and earlier do not fully validate a supplied fingerprint ID before using it to check for fingerprint XML metadata. A malformed ID can be used to probe whether XML files exist on the Jenkins controller filesystem when the target can be represented by a relative short path.
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 vulnerability enabling arbitrary file-existence checks through file fingerprints.
A Jenkins vulnerability allowing arbitrary file-existence checks through file fingerprints.
A moderate-severity Jenkins improper input-validation vulnerability in fingerprint-ID format validation. An authenticated low-privilege network attacker can determine whether XML files exist at short paths, causing a low confidentiality impact.
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.