Skip to content
major vulnerability· requires attention

Jenkins is widely used in CI/CD; an auth bypass enabling account takeover across orgs is broadly impactful and newsworthy.

Applications

CVE-2026-84668

8.8
High
EPSS 0.26%Patch availableSep 3, 2026

Jenkins SAML plugin allows IdP metadata overwrite, enabling authentication as any user.

common questions

Is CVE-2026-84668 being exploited?

Not confirmed. CVE-2026-84668 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.

How severe is CVE-2026-84668?

CVE-2026-84668 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-84668?

Yes. A fix has been recorded for CVE-2026-84668. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-84668 affect?

CVE-2026-84668 affects Jenkins SAML Plugin <= 4.618.v441a_27fa_46d2, Jenkins instances using SAML authentication. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-84668?

Upgrade SAML Plugin to the patched version immediately; restrict admin access and rotate credentials.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Jenkins SAML Plugin <= 4.618.v441a_27fa_46d2Jenkins instances using SAML authentication
impact

Overwrite SAML IdP metadata via Stapler data binding to authenticate as any user, enabling full account takeover.

action required

Immediate action required

affected versions
Jenkins Project Jenkins SAML Plugin
  • affected<= 4.618.v441a_27fa_46d2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free