Security Advisories (3)
CVE-2026-18089 (2026-08-03)

Net::SAML2 versions before 0.86 for Perl allow SAML authentication bypass by verifying responses against the response-embedded certificate in verify_xml when no trust anchor is configured. verify_xml in Net::SAML2::Role::VerifyXML runs "return if !$anchors && !$cacert;" as soon as the XML::Sig check succeeds, and that check uses the X.509 certificate taken from the response's own dsig:KeyInfo/dsig:X509Certificate element, so an unanchored response is checked only against the key it carries. Binding::POST declares cacert as an optional Maybe[Str] with no default, so a POST binding built without one takes that path, and _verify_encrypted_assertion returns early the same way with "return $xml unless $cacert;". Any caller that constructs Binding::POST or calls Assertion->new_from_xml without a cacert, cert_text, or anchors argument accepts a response signed by an attacker generated key whose self-signed certificate is embedded in that response, authenticating an arbitrary assertion.

CVE-2026-18092 (2026-08-03)

Net::SAML2 versions before 0.86 for Perl allow SAML authentication bypass via XML signature wrapping because new_from_xml reads assertion identity with document-wide XPath instead of the signed subtree. new_from_xml reads the NameID, attribute values, SessionIndex, audience and other identity fields with document-wide XPath, such as //saml:Assertion/saml:AttributeStatement/saml:Attribute and //saml:Subject/saml:NameID, which select the first matching element in document order rather than the element covered by the verified signature. handle_response confirms that a signature is present and, when a cacert is configured, that it chains to the CA, but XML::Sig verifies only the element named by the signature's Reference URI, so unsigned sibling assertions in the same document are not covered. An attacker who holds any one IdP-signed assertion can add an unsigned attacker-authored assertion earlier in document order; the signature still verifies and the document-order XPath returns the attacker's NameID and attributes. Any caller that passes an untrusted Response to new_from_xml can accept identity fields from an assertion the IdP never signed, even when a cacert trust anchor is configured, so a party holding one valid IdP-signed assertion can authenticate as an arbitrary user.

CVE-2026-18108 (2026-08-03)

Net::SAML2 versions before 0.86 for Perl allow authentication bypass because _verify_encrypted_assertion accepts an EncryptedAssertion whose decrypted content carries no signature. _verify_encrypted_assertion decrypts the EncryptedAssertion and returns it as verified when it carries no signature, via "return $xml unless $xpath->exists('dsig:Signature', $assert);". The signature check and the trust anchor check that follow run only when a signature is present, so a decrypted assertion with no dsig:Signature element reaches new_from_xml unverified and its NameID and attributes are read into the assertion object. An SP's encryption certificate is published in its SAML metadata so the IdP can encrypt to it, so any party can encrypt an unsigned assertion to that certificate, wrap it in a samlp:Response, and post it to the assertion consumer service. Any caller that configures a decryption key_file, and so accepts EncryptedAssertions, takes identity fields from an assertion that no trust anchor covers, and an unauthenticated party can authenticate as an arbitrary user. Callers with no key_file configured do not decrypt and are unaffected.

Changes for version 0.70 - 2023-07-04

  • Significant Changes since 0.69
    • Quite a few changes and improvements including
    • Support to obtain information about the AuthnStatement from the Assertion
    • Function to obtain key_name added to the SP
    • Verification of artifact responses based on an attribute ID ( via XML::Sig 0.64)
    • Improve Decryption of EncryptedData nodes for Assertions (via XML::Enc 0.12 and up)
    • Bumps the requirements new versions of:
    • XML::Enc => "0.12",
    • XML::Sig => "0.64",
    • XML::Generator => "1.13"
    • Miscelaneous:
    • testapp bug fixes and improvements
    • Github action improvements
    • Tested ADFS IdP again
    • Fixed issue DAKKAR reported to LWP::UserAgent Environment Variables
  • Change Log
    • 9d389f1 Decrypt an assertion with EncryptedData nodes
    • ae3888a Fix YAML syntax for linux workflow
    • 4d73198 Add verification for artifact responses on an attribute ID
    • 7869a2f Add tests for part encrypted/part decrypted assertions
    • 466e870 Add key_name function to SP
    • b4c70d8 testapp: option for acs_url_post in authnRequest
    • fa6c350 testapp: SingleLogoutService is not indexed
    • d2cf58a install Module::Pluggable
    • 2dfb0c1 Remove Pari Install from github action
    • 8932955 Bump requirement for XML::Generator
    • 11ba40d Create AuthnStatement object
    • 488a234 ADFS fully tested again and update repo version
    • 9dbd114 Fixes #169 tests fail when PERL_LWP_SSL_CA_* or HTTPS_CA_* env vars are set
    • a9aca61 Add XML declartion to generate_metadata
    • 7cfe56a Configure SP without Single Logout Service
    • ef16349 Fix version for release
    • accfc66 (timlegge/master) v0.69

Documentation

Modules

SAML2 bindings and protocol implementation
Net::SAML2::Binding::POST - HTTP POST binding for SAML
Net::SAML2::Binding::Redirect - HTTP Redirect binding for SAML
Net::SAML2::Binding::SOAP - SOAP binding for SAML
Net::SAML2::IdP - SAML Identity Provider object
Net::SAML2::Protocol::Artifact - SAML2 artifact object
Net::SAML2::Protocol::ArtifactResolve - ArtifactResolve protocol class
Net::SAML2::Protocol::Assertion - SAML2 assertion object
SAML2 AuthnRequest object
SAML2 LogoutRequest Protocol object
SAML2 LogoutResponse Protocol object
Common behaviour for Protocol messages
A role to verify the SAML response XML
Net::SAML2::SP - SAML Service Provider object
Custom Moose types for Net::SAML2
Utility functions for Net::SAML2
Net::SAML2 subclass of XML::Sig
Net::SAML2::XML::Util - XML Util class