{"answers":{"affected":"2 open source packages ship an affected version, including samlify. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-47949 in the wild and no public exploit code.","fix":"Upgrade samlify to 2.10.0 or later.","what":"CVE-2025-47949 is a critical authentication bypass vulnerability in tngan samlify, published on 19 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-47949 and fix it if it is affected.\n\nWhat it is: CVE-2025-47949 is a critical authentication bypass vulnerability in tngan samlify, published on 19 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-47949 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- samlify (npm): affected all versions; fixed in 2.10.0\n- samlify (npm): affected all versions; fixed in 2.10.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-47949/ (Markdown: https://insights.sbomify.com/CVE-2025-47949/index.md)","id":"CVE-2025-47949","markdown":"https://insights.sbomify.com/CVE-2025-47949/index.md","name":"CVE-2025-47949","record":{"aliases":["GHSA-r683-v43c-6xqv","ROOT-APP-NPM-CVE-2025-47949"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js SAML library","requires_auth":"none","summary":"Attackers can forge SAML responses to authenticate as any user in samlify, requiring a signed XML document from the identity provider.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"samlify","vendor":"samlify_project"}],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"samlify is a Node.js library for SAML single sign-on. A Signature Wrapping attack has been found in samlify prior to version 2.10.0, allowing an attacker to forge a SAML Response to authenticate as any user. An attacker would need a signed XML document by the identity provider. Version 2.10.0 fixes the issue.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"samlify SAML Signature Wrapping attack","id":"CVE-2025-47949","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"CoreDNS Vulnerable to DoQ Memory Exhaustion via Stream Amplification","id":"CVE-2025-47950"},"packages":[{"ecosystem":"npm","fixed":["2.10.0"],"introduced":["0"],"last_affected":[],"package":"samlify","purl":null,"source":"GHSA-r683-v43c-6xqv"},{"ecosystem":"npm","fixed":["2.10.0"],"introduced":["0"],"last_affected":[],"package":"samlify","purl":"pkg:npm/samlify","source":"GHSA-r683-v43c-6xqv"}],"prev":{"headline":"Cocotais Bot has builtin .echo command injection","id":"CVE-2025-47948"},"products":["samlify"],"published":"2025-05-19","related":[{"cvss_score":8.7,"headline":"samlify: XML Injection in AttributeValue Allows Privilege Escalation in Signed SAML Assertions","id":"CVE-2026-46490","kev_date_added":null,"published":"2026-06-08"},{"cvss_score":7.5,"headline":"Samlify vulnerable to Authentication Bypass by allowing tokens to be reused with different usernames","id":"CVE-2017-1000452","kev_date_added":null,"published":"2018-01-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-20","vendors":["tngan"]},"summary":"Attackers can forge SAML responses to authenticate as any user in samlify, requiring a signed XML document from the identity provider.","url":"https://insights.sbomify.com/CVE-2025-47949/"}