CVE-2026-86304
Last modified
CVE-2026-86304 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. MojoX::Authentication versions before 0.006 for Perl allow SAML authentication bypass because parse_assertion builds Net::SAML2::Binding::POST without a trust anchor. parse_assertion in MojoX::Authentication::Model::SAML2 calls Net::SAML2::Binding::POST->new with no cacert, cert_text or anchors argument, then passes the returned XML to Net::SAML2::Protocol::Assertion->new_from_xml with the IdP signing certificate as cacert. In Net::SAML2 before 0.86 that certificate guards only encrypted assertions, so the signature on an unencrypted assertion is checked against the certificate the response itself carries. An attacker starts a SAML login, then posts a response signed with a certificate of their own. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
Description
MojoX::Authentication versions before 0.006 for Perl allow SAML authentication bypass because parse_assertion builds Net::SAML2::Binding::POST without a trust anchor. parse_assertion in MojoX::Authentication::Model::SAML2 calls Net::SAML2::Binding::POST->new with no cacert, cert_text or anchors argument, then passes the returned XML to Net::SAML2::Protocol::Assertion->new_from_xml with the IdP signing certificate as cacert. In Net::SAML2 before 0.86 that certificate guards only encrypted assertions, so the signature on an unencrypted assertion is checked against the certificate the response itself carries. An attacker starts a SAML login, then posts a response signed with a certificate of their own. The audience, InResponseTo and timestamp checks that follow are all satisfiable by the attacker, so the response authenticates any NameID it carries.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| — | — | < 0.006 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-86304?
How severe is CVE-2026-86304?
How do I fix CVE-2026-86304?
How Strix Helps
- Same Subject, Wrong User: A Cross-Issuer Account Takeover in n8nStrix found an identity-binding bug in n8n's token-exchange flow enabling account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-86299A vulnerability was detected in Linksys RE7000 2.0.15. This …9.9
- CVE-2026-8630justhtml before 1.12.0 (versions <= 1.11.0) contains a mutat…6.1
- CVE-2026-86300A flaw has been found in Tenda AC9 15.03.05.14. This impacts…7.3
- CVE-2026-86301A vulnerability has been found in code-projects Hospital Inf…3.5
- CVE-2026-86302A vulnerability was found in code-projects Hospital Informat…5.3
- CVE-2026-86303A vulnerability was determined in 92181 markdown up to 058ca…7.3
- CVE-2026-86305A security flaw has been discovered in light0011 cms c774dce…7.3
- CVE-2026-86306A weakness has been identified in light0011 cms c774dce31c6d…7.3
- CVE-2026-86307A security vulnerability has been detected in light0011 cms …4.3
- CVE-2026-86308A vulnerability was detected in light0011 cms c774dce31c6df0…5.3
- CVE-2026-86309A flaw has been found in itsourcecode Sales and Inventory Sy…6.3
- CVE-2026-8631A potential security vulnerability has been identified in th…9.8
Are you affected by CVE-2026-86304?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
