{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-9390 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9390 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9390 is a critical code injection vulnerability in TIMLEGGE XML::Sig, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-9390 and fix it if it is affected.\n\nWhat it is: CVE-2026-9390 is a critical code injection vulnerability in TIMLEGGE XML::Sig, published on 3 Aug 2026. 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-2026-9390 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-2026-9390/ (Markdown: https://insights.sbomify.com/CVE-2026-9390/index.md)","id":"CVE-2026-9390","markdown":"https://insights.sbomify.com/CVE-2026-9390/index.md","name":"CVE-2026-9390","record":{"aliases":["GHSA-mhmm-7px6-jx3j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl XML signing library","requires_auth":"none","summary":"Attackers can inject XPath expressions to bypass XML signature verification, allowing them to validate malicious documents as legitimate.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"\\","vendor":"xml\\"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-643","name":"Improper Neutralization of Data within XPath Expressions"},{"id":"CWE-1287","name":"Improper Validation of Specified Type of Input"}],"description":"XML::Sig versions before 0.71 for Perl allow XPath injection in ID lookup.\n\nverify() and _get_signed_xml() in lib/XML/Sig.pm build XPath expressions by concatenating the SignedInfo/Reference/@URI value read from the document being verified. The value is neither escaped nor checked against the NCName grammar that XML requires of an ID, so a URI containing a single quote closes the string literal in the generated expression and appends arbitrary XPath operators.\n\nA crafted URI can make the lookup match elements the reference does not name, or every element in the document, so which node is selected for digest verification is decided by the injected expression rather than by the reference.","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 versions before 0.71 for Perl allow XPath injection in ID lookup","id":"CVE-2026-9390","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"H3C Magic B0 aspForm Edit_BasicSSID_5G buffer overflow","id":"CVE-2026-9393"},"packages":[],"prev":{"headline":"Tenda F456 L7Im frmL7ImForm buffer overflow","id":"CVE-2026-9389"},"products":["XML::Sig"],"published":"2026-08-03","related":[{"cvss_score":9.3,"headline":"XML-Sig prior to 0.68 for Perl improperly validates XML without signatures","id":"CVE-2025-40934","kev_date_added":null,"published":"2025-11-26"},{"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":"total"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["TIMLEGGE"]},"summary":"Attackers can inject XPath expressions to bypass XML signature verification, allowing them to validate malicious documents as legitimate.","url":"https://insights.sbomify.com/CVE-2026-9390/"}