CVE-2026-18089: CWE-347 Improper Verification of Cryptographic Signature in TIMLEGGE Net::SAML2
Net::SAML2 versions before 0.86 for Perl contain a vulnerability that allows SAML authentication bypass. The verify_xml function verifies responses against a certificate embedded within the response itself when no trust anchor is configured, enabling attackers to authenticate arbitrary assertions using self-signed certificates. This occurs because the code returns early if no trust anchors or CA certificates are provided, trusting the embedded certificate without external validation.
AI Analysis
Technical Summary
CVE-2026-18089 affects Net::SAML2 versions prior to 0.86. The vulnerability arises from improper verification of cryptographic signatures (CWE-347) in the verify_xml method of Net::SAML2::Role::VerifyXML. When no trust anchor or CA certificate is configured, the function accepts the X.509 certificate embedded in the SAML response itself for signature verification. This allows an attacker to craft a response with a self-signed certificate embedded in the dsig:KeyInfo/dsig:X509Certificate element, bypassing authentication and accepting arbitrary assertions. The issue is particularly present when Binding::POST is constructed without specifying a cacert parameter, leading to unanchored verification.
Potential Impact
An attacker can bypass SAML authentication by submitting a response signed with a self-signed certificate embedded in the response, effectively authenticating arbitrary assertions without possessing a valid trust anchor. This compromises the integrity of the authentication process, potentially allowing unauthorized access to systems relying on Net::SAML2 for SAML authentication.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, ensure that all SAML response verifications are configured with proper trust anchors or CA certificates. Avoid using Binding::POST or Assertion->new_from_xml without specifying a trusted cacert, cert_text, or anchors parameter to prevent acceptance of untrusted certificates embedded in responses.
CVE-2026-18089: CWE-347 Improper Verification of Cryptographic Signature in TIMLEGGE Net::SAML2
Description
Net::SAML2 versions before 0.86 for Perl contain a vulnerability that allows SAML authentication bypass. The verify_xml function verifies responses against a certificate embedded within the response itself when no trust anchor is configured, enabling attackers to authenticate arbitrary assertions using self-signed certificates. This occurs because the code returns early if no trust anchors or CA certificates are provided, trusting the embedded certificate without external validation.
CVSS v3.1
Score 7.5high
Affected software
TIMLEGGE
Net::SAML2
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-18089 affects Net::SAML2 versions prior to 0.86. The vulnerability arises from improper verification of cryptographic signatures (CWE-347) in the verify_xml method of Net::SAML2::Role::VerifyXML. When no trust anchor or CA certificate is configured, the function accepts the X.509 certificate embedded in the SAML response itself for signature verification. This allows an attacker to craft a response with a self-signed certificate embedded in the dsig:KeyInfo/dsig:X509Certificate element, bypassing authentication and accepting arbitrary assertions. The issue is particularly present when Binding::POST is constructed without specifying a cacert parameter, leading to unanchored verification.
Potential Impact
An attacker can bypass SAML authentication by submitting a response signed with a self-signed certificate embedded in the response, effectively authenticating arbitrary assertions without possessing a valid trust anchor. This compromises the integrity of the authentication process, potentially allowing unauthorized access to systems relying on Net::SAML2 for SAML authentication.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, ensure that all SAML response verifications are configured with proper trust anchors or CA certificates. Avoid using Binding::POST or Assertion->new_from_xml without specifying a trusted cacert, cert_text, or anchors parameter to prevent acceptance of untrusted certificates embedded in responses.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-07-28T16:26:10.967Z
- State
- PUBLISHED
Threat ID: 6a7098b0bf32cb7a34a822a3
Added to database: 08/03/2026, 13:33:36 UTC
Last enriched: 08/10/2026, 14:54:55 UTC
Last updated: 09/17/2026, 22:01:33 UTC
Views: 31
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.