CVE-2026-89042

passport-saml-encrypted through 0.1.13 Authentication Bypass via Missing Signature Verification

Published Sep 10, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
passport-saml-encrypted through 0.1.13 makes SAML signature verification conditional on an optional cert option, allowing attackers to bypass authentication by submitting unsigned SAML responses. Attackers can post forged SAML responses with arbitrary NameID and attributes to the assertion consumer service endpoint to receive authenticated profiles without valid signatures.

Analysis

AI-generated

Technical impact

passport-saml-encrypted through version 0.1.13 performs signature verification only when an optional certificate option is provided; when omitted, the library skips signature validation. This allows an attacker to construct a forged, unsigned SAML response containing arbitrary NameID and attributes, submit it to the assertion consumer service, and obtain an authenticated profile without a valid signature, effectively bypassing authentication and compromising integrity.

Affected Systems

The vulnerable component is the krakenjs passport-saml-encrypted package, specifically versions 0.1.13 and earlier. Any project that incorporates this library for SAML assertion handling is susceptible unless a later fix or environmental constraints have been applied.

Risk and Exploitability

The CVSS score of 9.3 indicates critical severity and the flaw is remotely exploitable over the network via the SAML assertion consumer service endpoint. While an EPSS score is not available, the lack of protection for unsigned responses creates a high likelihood of exploitation in systems that accept SAML assertions. The high severity warrants immediate remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to passport-saml-encrypted version 0.1.14 or later, which enforces signature verification regardless of certificate configuration.
  • Configure the SAML service provider to reject unsigned assertions by enabling strict signature validation in its settings.
  • As a temporary measure, modify local code or apply a patch that forces signature verification even when the optional cert option is omitted.

Generated by OpenCVE AI on September 11, 2026 at 00:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Krakenjs
Krakenjs passport-saml-encrypted
Vendors & Products Krakenjs
Krakenjs passport-saml-encrypted
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Description passport-saml-encrypted through 0.1.13 makes SAML signature verification conditional on an optional cert option, allowing attackers to bypass authentication by submitting unsigned SAML responses. Attackers can post forged SAML responses with arbitrary NameID and attributes to the assertion consumer service endpoint to receive authenticated profiles without valid signatures.
Title passport-saml-encrypted through 0.1.13 Authentication Bypass via Missing Signature Verification
Weaknesses CWE-347
References
Metrics cvssV3_1

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

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 11, 2026, 8:32 PM
Reserved
Sep 10, 2026, 4:45 PM
Status
Deferred
Published
Sep 10, 2026, 6:18 PM
Modified
Sep 11, 2026, 9:17 PM