{"answers":{"affected":"3 open source packages ship an affected version, including signxml.","exploited":"There is no known exploitation of CVE-2025-48994 in the wild and no public exploit code.","fix":"Upgrade signxml to 4.0.4 or later.","what":"CVE-2025-48994 is a medium-severity vulnerability in XML-Security signxml, published on 2 Jun 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-48994 and fix it if it is affected.\n\nWhat it is: CVE-2025-48994 is a medium-severity vulnerability in XML-Security signxml, published on 2 Jun 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-48994 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- signxml (PyPI): affected all versions; fixed in 4.0.4\n- signxml (PyPI): affected all versions; fixed in 4.0.4\n- signxml (PyPI): affected all versions; fixed in 4.0.4\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-48994/ (Markdown: https://insights.sbomify.com/CVE-2025-48994/index.md)","id":"CVE-2025-48994","markdown":"https://insights.sbomify.com/CVE-2025-48994/index.md","name":"CVE-2025-48994","record":{"aliases":["DEBIAN-CVE-2025-48994","GHSA-6vx8-pcwv-xhf4","PYSEC-2026-1921","UBUNTU-CVE-2025-48994"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Python XML signature library","requires_auth":"none","summary":"Attackers can bypass signature verification in SignXML by exploiting algorithm confusion when X509 validation is disabled and HMAC keys are used.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-303","name":"Incorrect Implementation of Authentication Algorithm"}],"description":"SignXML is an implementation of the W3C XML Signature standard in Python. When verifying signatures with X509 certificate validation turned off and HMAC shared secret set (`signxml.XMLVerifier.verify(require_x509=False, hmac_key=...`), versions of SignXML prior to 4.0.4 are vulnerable to a potential algorithm confusion attack. Unless the user explicitly limits the expected signature algorithms using the `signxml.XMLVerifier.verify(expect_config=...)` setting, an attacker may supply a signature unexpectedly signed with a key other than the provided HMAC key, using a different (asymmetric key) signature algorithm. Starting with SignXML 4.0.4, specifying `hmac_key` causes the set of accepted signature algorithms to be restricted to HMAC only, if not already restricted by the user.","ecosystems":["PyPI"],"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":"SignXML's signature verification with HMAC is vulnerable to an algorithm confusion attack","id":"CVE-2025-48994","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"SignXML's signature verification with HMAC is vulnerable to a timing attack","id":"CVE-2025-48995"},"packages":[{"ecosystem":"PyPI","fixed":["4.0.4"],"introduced":["0"],"last_affected":[],"package":"signxml","purl":null,"source":"GHSA-6vx8-pcwv-xhf4"},{"ecosystem":"PyPI","fixed":["4.0.4"],"introduced":["0"],"last_affected":[],"package":"signxml","purl":"pkg:pypi/signxml","source":"GHSA-6vx8-pcwv-xhf4"},{"ecosystem":"PyPI","fixed":["4.0.4"],"introduced":["0"],"last_affected":[],"package":"signxml","purl":"pkg:pypi/signxml","source":"PYSEC-2026-1921"}],"prev":{"headline":"Group-Office vulnerable to reflected XSS via Look and Feel Formatting input","id":"CVE-2025-48993"},"products":["signxml"],"published":"2025-06-02","related":[],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-06-02","vendors":["XML-Security"]},"summary":"Attackers can bypass signature verification in SignXML by exploiting algorithm confusion when X509 validation is disabled and HMAC keys are used.","url":"https://insights.sbomify.com/CVE-2025-48994/"}