{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-40934 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-40934 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-40934 is a critical vulnerability in TIMLEGGE XML::Sig, published on 26 Nov 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-40934 and fix it if it is affected.\n\nWhat it is: CVE-2025-40934 is a critical vulnerability in TIMLEGGE XML::Sig, published on 26 Nov 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-40934 in the wild and no public exploit code.\n\nAffected product: TIMLEGGE XML::Sig. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-40934/ (Markdown: https://insights.sbomify.com/CVE-2025-40934/index.md)","id":"CVE-2025-40934","markdown":"https://insights.sbomify.com/CVE-2025-40934/index.md","name":"CVE-2025-40934","record":{"aliases":["GHSA-v825-mc9m-64qr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl XML signature library","requires_auth":"none","summary":"Attackers can bypass XML signature validation by removing signatures, allowing unsigned documents to pass verification checks in Perl applications.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"\\","vendor":"xml\\"}],"cvss":{"score":9.3,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"XML-Sig versions 0.27 through 0.67 for Perl incorrectly validates XML files if signatures are omitted.\n\nAn attacker can remove the signature from the XML document to make it pass the verification check.\n\nXML-Sig is a Perl module to validate signatures on XML files.  An unsigned XML file should return an error message.  The affected versions return true when attempting to validate an XML file that contains no signatures.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"XML-Sig prior to 0.68 for Perl improperly validates XML without signatures","id":"CVE-2025-40934","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in RUGGEDCOM RMC8388 V5.X","id":"CVE-2025-40935"},"packages":[],"prev":{"headline":"Apache::AuthAny::Cookie v0.201 or earlier for Perl generates session ids insecurely","id":"CVE-2025-40933"},"products":["XML::Sig"],"published":"2025-11-26","related":[{"cvss_score":9.1,"headline":"XML::Sig versions before 0.71 for Perl allow XPath injection in ID lookup","id":"CVE-2026-9390","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":9.1,"headline":"XML::Sig versions before 0.71 for Perl allow signature wrapping via duplicate ID","id":"CVE-2026-9487","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":7.5,"headline":"Security feature bypass in XML::Sig","id":"CVE-2026-18568","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":7.5,"headline":"XML external entity in perl-xml-atom","id":"CVE-2012-1102","kev_date_added":null,"published":"2021-07-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-11-28","vendors":["TIMLEGGE"]},"summary":"Attackers can bypass XML signature validation by removing signatures, allowing unsigned documents to pass verification checks in Perl applications.","url":"https://insights.sbomify.com/CVE-2025-40934/"}