Loading story…
Jenkins, a widely used open-source automation server, has released critical security updates to address multiple high-severity vulnerabilities that could expose CI/CD pipelines to significant risks. The most severe flaw, tracked as CVE-2025-67635, affects Jenkins versions 2.540 and earlier (including LTS 2.528.2 and earlier) and allows unauthenticated attackers to trigger denial-of-service (DoS) attacks via the HTTP-based command-line interface. This vulnerability arises from improper connection handling, where corrupted HTTP CLI streams are not properly closed, enabling attackers to exhaust server resources and render Jenkins instances unresponsive. Organizations relying on Jenkins are urged to upgrade to version 2.541 or LTS 2.528.3 to mitigate this risk.
In addition to the DoS vulnerability, another high-severity issue, CVE-2025-67641, was identified in the Jenkins Coverage Plugin. This flaw allows attackers with "Item/Configure" permissions to exploit coverage reports for stored cross-site scripting (XSS) attacks by submitting malicious JavaScript via the REST API. If an administrator views a compromised report, the script executes, potentially leading to session hijacking. Both vulnerabilities have been addressed in the latest Jenkins security updates, and immediate patching is recommended to protect against exploitation.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
4 events from the most recent confirmed update back to the earliest known activity.
By 2025-12-10, Jenkins' advisory also identified CVE-2025-67642, a medium-severity vulnerability in the HashiCorp Vault Plugin, as not yet patched. Administrators were advised to review the advisory and take mitigating action where possible.
On 2025-12-10, Jenkins released fixes for CVE-2025-67635, a high-severity denial-of-service vulnerability affecting Jenkins 2.540 and earlier and LTS 2.528.2 and earlier. Patched versions 2.541 and LTS 2.528.3 prevent malformed HTTP CLI requests from exhausting server resources.
On 2025-12-10, Jenkins publicly disclosed CVE-2025-67641, a high-severity stored XSS flaw in Coverage Plugin versions 2.3054.ve1ff7b_a_a_123b_ and earlier. The issue allows an attacker with Item/Configure permission to inject a malicious javascript: URL as a coverage results ID via the REST API.
On 2025-12-10, Jenkins released a security advisory covering multiple vulnerabilities in Jenkins core and several plugins, including BlazeMeter, Coverage, Git client, HashiCorp Vault, and Redpen - Pipeline Reporter for Jira. The advisory urged administrators to review affected versions and apply recommended updates.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
4 references tracked. Mallory keeps watching after this page renders.
securityonline.info
Open sourcecybersecuritynews.com
Open sourcecvefeed.io
Open sourcecyber.gc.ca
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Jenkins has released fixes in **Jenkins 2.568** and **Jenkins LTS 2.555.3** for multiple vulnerabilities affecting the automation server, including a high-impact unsafe deserialization flaw tracked as **`CVE-2026-53435`**. According to the disclosure, attackers with **Overall/Read** permission and additional access such as a valid user account or the ability to post `config.xml` data could trigger deserialization of Jenkins core or plugin types, potentially leading to **user impersonation, arbitrary HTTP requests, possible Script Console code execution, and arbitrary file reads** from the Jenkins controller. The issues affect **Jenkins 2.567 and earlier** and **Jenkins LTS 2.555.2 and earlier**. The advisory also addresses several additional weaknesses, including **open redirect** bugs in the login flow, a **missing permission check** in HTTP endpoints, an **unsafe redirect** in the "Delegate to servlet container" security realm, a **stored XSS** issue through offline cause descriptions, and exposure of **plaintext secrets** through `config.xml` handling. Organizations running self-managed Jenkins instances should prioritize upgrading to the fixed releases and review controller exposure, user permissions, and configuration handling paths that could allow low-privileged users to reach sensitive functionality.
Jun 29, 2026
Jenkins published a security advisory covering multiple vulnerabilities in widely used plugins, with fixes released for affected versions. The disclosed issues span **missing permission checks**, **unsafe deserialization**, **stored cross-site scripting**, and an **open redirect**, affecting plugins including **Script Security**, **Credentials Binding**, **Matrix Authorization Strategy**, **GitHub Branch Source**, **GitHub**, **HTML Publisher**, and **Microsoft Entra ID**. The most serious issue is an **arbitrary file write** flaw that can lead to **remote code execution**, while other bugs could let attackers abuse low-privilege access such as `Overall/Read`, `Item/Configure`, or the ability to supply credentials to a job. Jenkins said the advisory includes severity ratings, attribution, and patched plugin versions, and urged administrators to update impacted plugins to the fixed releases.
Jun 29, 2026
Jenkins disclosed two Jenkins Core vulnerabilities affecting **Jenkins 2.550 and earlier** and **LTS 2.541.1 and earlier**: a **high-severity stored XSS** issue (**CVE-2026-27099 / SECURITY-3669**) and a **medium-severity information disclosure** issue via Run Parameter handling (**CVE-2026-27100 / SECURITY-3658**). The XSS flaw stems from improper escaping of user-supplied HTML in the node “offline cause” description (specifically the “Mark temporarily offline” reason), enabling attackers with `Agent/Configure` or `Agent/Disconnect` permissions to inject JavaScript that can execute in other users’ sessions. Jenkins fixed both issues in **Jenkins 2.551** and **LTS 2.541.2** by escaping the offline-cause description and rejecting Run Parameter values that reference builds the submitting user cannot access. For CVE-2026-27099, Jenkins noted that on **Jenkins 2.539+**, enforcing **Content Security Policy (CSP)** can mitigate the impact (with partial protection referenced for newer versions). Both vulnerabilities were reported via the **Jenkins Bug Bounty Program** sponsored by the European Commission, and organizations running affected versions should prioritize upgrading to the patched releases to reduce risk to CI/CD build environments.
Jun 29, 2026