{"answers":{"affected":"3 open source packages ship an affected version, including signxml.","exploited":"There is no known exploitation of CVE-2025-48995 in the wild and no public exploit code.","fix":"Upgrade signxml to 4.0.4 or later.","what":"CVE-2025-48995 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-48995 and fix it if it is affected.\n\nWhat it is: CVE-2025-48995 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-48995 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-48995/ (Markdown: https://insights.sbomify.com/CVE-2025-48995/index.md)","id":"CVE-2025-48995","markdown":"https://insights.sbomify.com/CVE-2025-48995/index.md","name":"CVE-2025-48995","record":{"aliases":["DEBIAN-CVE-2025-48995","GHSA-gmhf-gg8w-jw42","PYSEC-2026-1922","UBUNTU-CVE-2025-48995"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Python XML signature library","requires_auth":"none","summary":"Attackers can exploit timing differences to reconstruct HMAC keys in SignXML when X509 validation is disabled, compromising signature integrity.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"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 timing attack. The verifier may leak information about the correct HMAC when comparing it with the user supplied hash, allowing users to reconstruct the correct HMAC for any data.","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 a timing attack","id":"CVE-2025-48995","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Unauthenticated Disclosure of PSU HAX CMS Site Listings via haxPsuUsage API Endpoint","id":"CVE-2025-48996"},"packages":[{"ecosystem":"PyPI","fixed":["4.0.4"],"introduced":["0"],"last_affected":[],"package":"signxml","purl":null,"source":"GHSA-gmhf-gg8w-jw42"},{"ecosystem":"PyPI","fixed":["4.0.4"],"introduced":["0"],"last_affected":[],"package":"signxml","purl":"pkg:pypi/signxml","source":"GHSA-gmhf-gg8w-jw42"},{"ecosystem":"PyPI","fixed":["4.0.4"],"introduced":["0"],"last_affected":[],"package":"signxml","purl":"pkg:pypi/signxml","source":"PYSEC-2026-1922"}],"prev":{"headline":"SignXML's signature verification with HMAC is vulnerable to an algorithm confusion attack","id":"CVE-2025-48994"},"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 exploit timing differences to reconstruct HMAC keys in SignXML when X509 validation is disabled, compromising signature integrity.","url":"https://insights.sbomify.com/CVE-2025-48995/"}