CVE-2026-84668

8.8

Jenkins · Jenkins SAML Plugin

The Jenkins SAML Plugin contains a vulnerability allowing authenticated users to overwrite the SAML identity provider metadata file, leading to arbitrary user authentication.

Executive summary

A critical vulnerability in the Jenkins SAML Plugin allows authenticated attackers to bypass authentication controls by overwriting identity provider metadata, posing a severe risk to system integrity.

Vulnerability

The flaw resides in the Stapler data binding mechanism, which improperly validates input and permits the overwriting of the SAML identity provider metadata file. This vulnerability requires the attacker to hold low-level privileges to initiate the request.

Business impact

Successful exploitation of this vulnerability allows an attacker to manipulate the SAML authentication flow, effectively granting them the ability to impersonate any user within the Jenkins environment. Given the CVSS score of 8.8, this represents a high-severity risk that could lead to full unauthorized access, data exfiltration, and administrative compromise of the build pipeline and associated sensitive infrastructure.

Remediation

Immediate Action: Review the Jenkins security advisory at https://www.jenkins.io/security/advisory/2026-09-02/#SECURITY-4065 and apply the recommended plugin update as soon as it is made available by the vendor.

Proactive Monitoring: Review Jenkins access logs for unusual administrative activity or modifications to plugin configuration settings.

Compensating Controls: Restrict access to the Jenkins instance to trusted network segments and minimize the number of users with permissions required to interact with plugin configuration endpoints.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

Organizations utilizing the Jenkins SAML Plugin must prioritize this update, as the ability to forge authentication tokens or metadata poses an unacceptable risk to the security of the CI/CD pipeline. Security teams should monitor the official Jenkins security advisory page for the release of a patched version and deploy it immediately upon release to prevent potential exploitation.

More Jenkins CVEs

Sources