CVE-2021-21609 is an incorrect authorization vulnerability in Jenkins 2.274 and earlier and Jenkins LTS 2.263.1 and earlier. Jenkins incorrectly compared requested URLs with its list of always-accessible paths. As a result, plugin-provided URLs using certain always-accessible path prefixes could be treated as readable even when the requester lacked the Overall/Read permission.
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 missing-permission-check vulnerability affecting paths with a specific prefix.
A Jenkins vulnerability caused by a missing permission check for paths with a specific prefix.
An incorrect authorization vulnerability in Jenkins URL access-control matching. Unauthenticated or otherwise unauthorized attackers can access certain URLs as though they possess Jenkins Overall/Read permission, potentially exposing application data. Red Hat rates it Low with CVSS 3.1 score 5.3.
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.