Critical Jenkins Vulnerabilities Expose CI/CD Servers to RCE Attacks
## Cybersecurity Advisory: Critical Jenkins Vulnerabilities
Cybersecurity Advisory: Critical Jenkins Vulnerabilities
On March 18, 2026, a security advisory was issued addressing multiple high-severity vulnerabilities in Jenkins core and the LoadNinja plugin. These vulnerabilities could allow attackers to execute arbitrary code, fully compromising continuous integration and continuous deployment pipelines.
The most severe vulnerability, tracked as CVE-2026-33001, involves the handling of symbolic links when extracting .tar and .tar.gz archives. Attackers with item configuration permissions can craft malicious archives to write files to arbitrary locations on the file system. This flaw allows threat actors to write malicious scripts to the init.groovy.d/ directory or deploy rogue plugins to the plugins/ folder, granting remote code execution capabilities.
A second high-severity issue, identified as CVE-2026-33002, involves a DNS rebinding flaw within the WebSocket command-line interface origin validation. Attackers can bypass this validation by tricking a victim into visiting a malicious website, establishing an unauthorized WebSocket connection to the CLI endpoint. If Jenkins is configured to allow anonymous user permissions and operates over plain HTTP, this can lead to remote code execution.
On March 18, 2026, a security advisory was issued addressing multiple high-severity vulnerabilities in Jenkins core and the LoadNinja plugin.
A medium-severity vulnerability within the LoadNinja Plugin, tracked under CVE-2026-33003 and CVE-2026-33004, pertains to insecure storage and lack of masking for API keys. The plugin historically stored API keys in an unencrypted format within job configuration files, exposing them to users with extended read permissions or file system access.
According to the Jenkins Project security advisory , administrators should upgrade to Jenkins 2.555 (weekly) or 2.541.3 (LTS), and update the LoadNinja plugin to version 2.2 if immediate patching isn't feasible. Temporary workarounds for the DNS rebinding flaw include configuring strict authentication for the controller and removing permissions for the anonymous user.
Based on reporting by Cyber Security News.
