Critical Jenkins Flaw Exposes Build Environments to XSS Attacks
On February 18, 2026, significant security vulnerabilities were identified in the core Jenkins software, widely used for building, testing, and deploying software. Two primary issues were detailed, impacting organizations that utilize Jenkins for…
On February 18, 2026, significant security vulnerabilities were identified in the core Jenkins software, widely used for building, testing, and deploying software. Two primary issues were detailed, impacting organizations that utilize Jenkins for continuous integration and delivery (CI/CD) pipelines.
The most critical of these vulnerabilities is a stored cross-site scripting (XSS) flaw. This issue allows attackers to inject malicious scripts into build environments, potentially leading to data theft or session hijacking. The vulnerability arises from how Jenkins processes node offline causes, where user input is improperly escaped and rendered as HTML. This can be exploited by users with certain permissions, such as Agent/Configure or Agent/Disconnect.
Another vulnerability involves information leaks through Run Parameters. Users with specific permissions can input parameters referencing builds they should not access, revealing job details and aiding in targeted attacks.
CVE ID CVSS Score Description
CVE-2026-27099 High (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H) Stored XSS in node offline causes a description; unescaped user input renders as HTML, exploitable by permitted users.
Two primary issues were detailed, impacting organizations that utilize Jenkins for continuous integration and delivery (CI/CD) pipelines.
CVE-2026-27100 Medium (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Run Parameter accepts invalid build references, leaking job/build existence and names to unauthorized users.
Type Affected Versions Fixed Versions
Weekly Up to 2.550 2.551
LTS Up to 2.541.1 2.541.2
It is advised to update Jenkins immediately to prevent exploitation. For Jenkins 2.539 and newer, the Content Security Policy (CSP) provides mitigation against the XSS vulnerability. Non-essential permissions such as Agent/Configure should be disabled for non-admin users. Detailed information can be found on the Jenkins Security Advisory .
Organizations should scan their CI/CD environments for exposed nodes and review offline logs to mitigate risks. Although no active exploits are public at this time, the vulnerabilities pose significant threats to development teams.
Based on reporting by GBHackers.
