<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Jenkins — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/jenkins/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 29 Apr 2026 14:40:42 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/jenkins/feed.xml" rel="self" type="application/rss+xml"/><item><title>Jenkins Security Advisory Addressing Multiple Plugin Vulnerabilities</title><link>https://feed.craftedsignal.io/briefs/2026-04-jenkins-plugins/</link><pubDate>Wed, 29 Apr 2026 14:40:42 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-jenkins-plugins/</guid><description>Jenkins released a security advisory on April 29, 2026, detailing vulnerabilities in Credentials Binding Plugin, GitHub Plugin, GitHub Branch Source Plugin, HTML Publisher Plugin, Matrix Authorization Strategy Plugin, Microsoft Entra ID Plugin, and Script Security Plugin, urging users to apply necessary updates.</description><content:encoded><![CDATA[<p>On April 29, 2026, Jenkins issued a security advisory (AV26-403) addressing vulnerabilities across several plugins. These vulnerabilities affect Credentials Binding Plugin (version 719.v80e905ef14eb_ and prior), GitHub Plugin (version 1.46.0 and prior), GitHub Branch Source Plugin (version 1967.vdea_d580c1a_b_a_ and prior), HTML Publisher Plugin (version 427 and prior), Matrix Authorization Strategy Plugin (versions 2.0-beta-1 to 3.2.9), Microsoft Entra ID (previously Azure AD) Plugin (version 666.v6060de32f87d and prior), and Script Security Plugin (version 1399.ve6a_66547f6e1 and prior). The advisory emphasizes the importance of applying the necessary updates to mitigate potential risks. This broad range of affected plugins highlights the need for Jenkins administrators to promptly review and implement the provided security measures. The Cyber Centre encourages users to review the advisory.</p>
<h2 id="attack-chain">Attack Chain</h2>
<p>Given the nature of the advisory, a generic attack chain is described below. Specific steps depend on the exploited vulnerability in each plugin.</p>
<ol>
<li>An attacker identifies a vulnerable Jenkins plugin version.</li>
<li>The attacker crafts a malicious request targeting a specific endpoint of the vulnerable plugin.</li>
<li>The request exploits a vulnerability, such as arbitrary code execution, bypass authentication, or cross-site scripting (XSS).</li>
<li>The Jenkins server processes the malicious request, leading to unauthorized code execution.</li>
<li>The attacker gains access to sensitive information, such as credentials stored within Jenkins.</li>
<li>The attacker uses the compromised credentials to access other systems or escalate privileges within the Jenkins environment.</li>
<li>The attacker modifies build configurations to inject malicious code into software builds.</li>
<li>The attacker compromises software builds and injects malicious code, impacting downstream users of the software.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of these vulnerabilities could lead to unauthorized access to sensitive information, arbitrary code execution on the Jenkins server, and compromise of software builds. This can result in supply chain attacks, data breaches, and reputational damage. The scope of impact depends on the specific vulnerabilities exploited and the access level obtained by the attacker. The Jenkins Security Advisory addresses vulnerabilities in multiple plugins, any of which if exploited, could have significant impacts.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Review the Jenkins Security Advisory 2026-04-29 and identify vulnerable plugins in your environment.</li>
<li>Update the Credentials Binding Plugin to a version greater than 719.v80e905ef14eb_.</li>
<li>Update the GitHub Plugin to a version greater than 1.46.0.</li>
<li>Update the GitHub Branch Source Plugin to a version greater than 1967.vdea_d580c1a_b_a_.</li>
<li>Update the HTML Publisher Plugin to a version greater than 427.</li>
<li>Update the Matrix Authorization Strategy Plugin to a version greater than 3.2.9.</li>
<li>Update the Microsoft Entra ID (previously Azure AD) Plugin to a version greater than 666.v6060de32f87d.</li>
<li>Update the Script Security Plugin to a version greater than 1399.ve6a_66547f6e1.</li>
<li>Monitor Jenkins webserver logs (category <code>webserver</code>, product <code>linux</code>) for suspicious activity and unauthorized access attempts after applying the updates.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>jenkins</category><category>vulnerability</category><category>plugin</category></item></channel></rss>