Skip to content
Cryptography

CVE-2026-9487

9.1
Critical
EPSS 0.17%Patch availableAug 4, 2026

XML::Sig signature wrapping via duplicate ID enables SAML assertion tampering.

common questions

Is CVE-2026-9487 being exploited?

Not confirmed. CVE-2026-9487 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.17% probability of exploitation in the next 30 days.

How severe is CVE-2026-9487?

CVE-2026-9487 is rated Critical with a CVSS score of 9.1. 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-9487?

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

What does CVE-2026-9487 affect?

CVE-2026-9487 affects Perl XML::Sig versions < 0.71, Applications using XML::Sig for XML Signature verification, SAML2 Service Providers and Identity Providers using this module. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-9487?

Upgrade to XML::Sig 0.71+ and enforce unique ID resolution and strict signature validation.

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

executive summary
technical analysis
affected
Perl XML::Sig versions < 0.71Applications using XML::Sig for XML Signature verificationSAML2 Service Providers and Identity Providers using this module
impact

Signature wrapping lets attacker substitute a signed element (e.g., SAML Assertion), enabling auth bypass, impersonation, and unauthorized access.

action required

Immediate action required

affected versions
TIMLEGGE XML::Sig
  • affected< 0.71

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