# CVE-2025-47949: samlify SAML Signature Wrapping attack

Source: https://junglewise.ai/threats/cve-2025-47949-samlify-saml-signature-wrapping-attack  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-05-19. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2025-47949 · Severity: medium · CVSS 4 · Published 2025-05-19

samlify is a Node.js library that handles SAML authentication, a common protocol for enterprise single sign-on. A signature wrapping attack in samlify allows attackers to forge SAML authentication responses and impersonate any user, provided they have access to a legitimate signed XML document from an identity provider. This could allow unauthorized access to applications relying on samlify for authentication.

Technologies: [samlify (npm)](https://junglewise.ai/threats/technologies/samlify). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2025-47949 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-47949 being exploited in the wild.

**How severe is CVE-2025-47949?** Medium severity, with a CVSS score of 4, published 19 May 2025.

**Which products and versions are affected?** samlify (npm) SEMVER:introduced=0,fixed=2.10.0.

**Is there a fix for CVE-2025-47949?** Yes. samlify (npm): upgrade to 2.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2025-47949 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2025-47949?** Check whether you run samlify (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- samlify (npm): upgrade to 2.10.0 or later

  ```sh
  npm install samlify@2.10.0
  ```


## Technical details

A Signature Wrapping attack (CWE-347) has been identified in samlify versions prior to 2.10.0. The vulnerability allows an attacker to manipulate SAML response messages by wrapping signed XML elements in such a way that the signature validation logic is bypassed or misinterpreted. An attacker with access to a legitimately signed XML document from an identity provider can craft a forged SAML Response that authenticates as any user. The attack is network-reachable and requires no authentication or user interaction. The vulnerability has been patched in version 2.10.0 and later.

## Affected products

- samlify samlify < 2.10.0

## Identifiers

- CVE-2025-47949
- GHSA-r683-v43c-6xqv

## Timeline

- 2025-05-19: disclosed
- 2025-05-19: patched: patched in version 2.10.0

## References

- [https://github.com/tngan/samlify/security/advisories/GHSA-r683-v43c-6xqv](https://github.com/tngan/samlify/security/advisories/GHSA-r683-v43c-6xqv)

## Related threats

- [tngan samlify XML injection in SAML AttributeValue](https://junglewise.ai/threats/cve-2026-46490-tngan-samlify-xml-injection-in-saml-attributevalue)
- [Samlify authentication bypass via XML signature wrapping](https://junglewise.ai/threats/cve-2017-1000452-samlify-authentication-bypass-via-xml-signature-wrapping)