Quick answers
- Is CVE-2026-84648 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84648 being exploited in the wild.
- How severe is CVE-2026-84648?
- High severity, with a CVSS score of 8.8, published 2 September 2026.
- Which products and versions are affected?
- Jenkins 2.579 and earlier, LTS 2.568.2 and earlier.
- Is there a fix for CVE-2026-84648?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-84648 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-84648?
- Check whether you run Jenkins at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a stored cross-site scripting (XSS) flaw in Jenkins' system log viewer component. The root cause is insufficient output encoding of log record metadata fields (source, level, timestamp) before rendering in HTML. Attackers with control over agent processes can inject JavaScript payloads into log records; when an administrator views the system logs, the malicious script executes in their browser context. No authentication is required beyond agent process control. The fix in Jenkins 2.580 and LTS 2.568.3 properly escapes these metadata fields. Content Security Policy (CSP) provides partial mitigation on Jenkins 2.539+ and LTS 2.541.1+.
Affected products
- Jenkins Jenkins 2.579 and earlier, LTS 2.568.2 and earlier
Timeline
- 2026-09-02: disclosed