Loading vulnerability…
CVE-2026-42523 is a stored cross-site scripting vulnerability in Jenkins GitHub Plugin 1.46.0 and earlier. The flaw is caused by improper processing of the current job URL in JavaScript used to validate the "GitHub hook trigger for GITScm polling" feature. Because attacker-controlled or insufficiently sanitized data is incorporated into stored content that is later rendered in the Jenkins web UI, a non-anonymous attacker with Overall/Read permission can inject malicious JavaScript that executes in another user's browser when the affected page is viewed.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity stored XSS vulnerability in the Jenkins GitHub Plugin that allows low-privileged authenticated attackers to inject malicious JavaScript into the application.
A stored cross-site scripting vulnerability in Jenkins GitHub Plugin 1.46.0 and earlier caused by improper processing of the current job URL in JavaScript validation logic for the "GitHub hook trigger for GITScm polling" feature.
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.