Skip to content
Web

CVE-2026-18092

8.1
High
EPSS 0.20%Patch availableAug 4, 2026

XML signature wrapping in Net::SAML2 allows SAML authentication bypass.

common questions

Is CVE-2026-18092 being exploited?

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

How severe is CVE-2026-18092?

CVE-2026-18092 is rated High with a CVSS score of 8.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-18092?

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

What does CVE-2026-18092 affect?

CVE-2026-18092 affects Net::SAML2 (< 0.86), Perl web apps using Net::SAML2, SAML Service Providers parsing untrusted Responses. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-18092?

Upgrade Net::SAML2 to >= 0.86 and validate assertions are covered by the signature.

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

executive summary
technical analysis
affected
Net::SAML2 (< 0.86)Perl web apps using Net::SAML2SAML Service Providers parsing untrusted Responses
impact

Authentication bypass: attacker with any valid signed assertion can add an unsigned assertion earlier in document order to impersonate arbitrary users.

action required

Immediate action required

affected versions
TIMLEGGE Net::SAML2
  • affected< 0.86

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