Loading vulnerability…
Jenkins Core contains an information disclosure vulnerability in the handling of Run Parameter values. In Jenkins 2.550 and earlier, and Jenkins LTS 2.541.1 and earlier, the application accepts Run Parameter values that reference builds the submitting user is not authorized to access. As a result, a user can supply references to jobs or builds outside their authorization scope and observe whether those objects exist. If a referenced build exists, Jenkins may also disclose its display name. The issue affects authorization enforcement around Run Parameter processing rather than permitting direct access to the underlying build contents.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Jenkins vulnerability that leaks build information.
A medium-severity Jenkins Core authorization flaw involving Run Parameter handling that allows unauthorized users to infer/query the existence of builds/jobs they should not be able to access, leading to information disclosure.
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.