CVE-2024-32962Public exploitNetwork attack vector

Signature verification bypass via attacker-supplied certificate

Published May 2, 2024 · Updated Feb 13, 2025

Signature verification bypass in node-saml xml-crypto 4.0.0 through 5.x allows remote attackers to pass modified XML as trusted. The verifier selects an X.509 certificate from attacker-controlled KeyInfo before a configured publicCert, then validates the replacement signature with that key. Default certificate extraction makes unauthenticated spoofing possible when an application validates untrusted signed XML, allowing tampered content to inherit the trust assigned to an authorized signer.

CVSS severity10.0
Critical
EPSS probability0.83%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Signature verification bypass in node-saml xml-crypto 4.0.0 through 5.x allows remote attackers to pass modified XML as trusted. The verifier selects an X.509 certificate from attacker-controlled KeyInfo before a configured publicCert, then validates the replacement signature with that key. Default certificate extraction makes unauthenticated spoofing possible when an application validates untrusted signed XML, allowing tampered content to inherit the trust assigned to an authorized signer.

The record

CVE
CVE-2024-32962
Published
May 2, 2024
Updated
Feb 13, 2025
Vendor
node-saml
Product
xml-crypto
Classifications
CWE-347
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 2, 2024CVE publishedPublication date reported by the CVE source.
  2. Feb 13, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 4.0.0, < 6.0.0
  2. Affected versionversion=4.0.0 <6.0.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

node-saml · xml-cryptoversion=>= 4.0.0, < 6.0.0; version=4.0.0 <6.0.0

Published CVSS scores

10.0GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo