Description
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.
Published: 2026-08-03
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Net::SAML2 library incorrectly accepts decrypted EncryptedAssertions that lack a digital signature. Because the signature verification is bypassed, an attacker can forge an unsigned assertion, encrypt it with the service provider’s certificate, and send it to the Assertion Consumer Service, causing the library to unconditionally populate the user identity fields. This allows the issuer to authenticate as any arbitrary user without authentication, constituting a CWE‑347 design flaw.

Affected Systems

The vulnerability affects the Net::SAML2 library from the TIMLEGGE vendor, specifically all versions earlier than 0.86. Versions 0.86 and later implement stricter checks that require the signature to chain to a trusted anchor.

Risk and Exploitability

The flaw poses a high‑risk authentication bypass that receives a CVSS score of 9.8 and can be exploited remotely over HTTPS by an unauthenticated attacker who can acquire or construct an unsigned SAML response. The EPSS score is not available, but the lack of signature protection makes exploitation straightforward once the service is misconfigured to decrypt assertions. The vulnerability is not listed in CISA’s KEV catalog. Attackers could claim arbitrary identities and potentially gain privileged access to protected resources.

Generated by OpenCVE AI on August 4, 2026 at 10:24 UTC.

Remediation

Vendor Solution

Upgrade to Net::SAML2 0.86 or later, which refuses to extract assertion content unless a signature covering the assertion chains to the configured trust anchor.


Vendor Workaround

For deployments that cannot upgrade to 0.86, do not configure a decryption key_file, so EncryptedAssertions are never decrypted and consumed.


OpenCVE Recommended Actions

  • Upgrade Net::SAML2 to version 0.86 or later, which rejects unsigned assertions.
  • If an upgrade is not possible, remove the decryption key_file configuration so that the library never decrypts encrypted assertions.
  • Enforce signature validation on all SAML responses or configure the application to reject unsigned or untrusted assertions.

Generated by OpenCVE AI on August 4, 2026 at 10:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 03 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 03 Aug 2026 16:15:00 +0000

Type Values Removed Values Added
First Time appeared Timlegge
Timlegge net::saml2
Vendors & Products Timlegge
Timlegge net::saml2

Mon, 03 Aug 2026 13:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Net::SAML2 versions before 0.86 for Perl allow authentication bypass because _verify_encrypted_assertion accepts an EncryptedAssertion whose decrypted content carries no signature
Weaknesses CWE-347
References

Subscriptions

Timlegge Net::saml2 Net\
cve-icon MITRE

Status: PUBLISHED

Assigner: CPANSec

Published:

Updated: 2026-08-03T19:57:38.266Z

Reserved: 2026-07-28T17:55:20.903Z

Link: CVE-2026-18108

cve-icon Vulnrichment

Updated: 2026-08-03T19:57:32.876Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-03T14:16:25.157

Modified: 2026-08-06T18:37:01.630

Link: CVE-2026-18108

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T10:30:07Z

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature