Loading vulnerability…
Jenkins 2.579 and earlier and Jenkins LTS 2.568.2 and earlier improperly authorize agent-configuration updates through REST API and CLI endpoints. The endpoints accept submitted XML whose agent name can differ from the agent for which the requester holds Agent/Configure permission. A user authorized to configure one agent can therefore overwrite the configuration of a different agent identified in the XML document.
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 REST API and CLI agent-configuration update endpoints. An attacker with Agent/Configure permission for one agent can specify another agent's name in submitted XML, overwrite that agent's configuration, and obtain its inbound-agent secret and environment variables.
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.