Loading vulnerability…
Jenkins 2.579 and earlier and Jenkins LTS 2.568.2 and earlier fail to enforce the Item/Cancel permission when the CLI build command is invoked with the -s flag to wait for build completion. A user holding Item/Build can merge a CLI build request into an existing queue item and interrupt the waiting CLI client, cancelling a build initiated by another user without authorization to cancel it.
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 Jenkins/Jenkins LTS vulnerability addressed through FreeBSD package security updates; the content provides no vulnerability-class or technical-impact detail.
An authorization flaw in Jenkins' build CLI command. When the -s flag is used to cancel a build that was triggered to wait for completion, Jenkins fails to enforce the Item/Cancel permission, allowing a user with only Item/Build permission to cancel builds initiated by other users.
Unknown; the vulnerability is referenced as affecting the identified Jenkins release range, but no technical description is 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.