{"answers":{"affected":"2 open source packages ship an affected version, including libxmljs. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25341 exists.","fix":"No fix has been published for CVE-2025-25341 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25341 is a high-severity denial of service vulnerability in n/a, published on 26 Dec 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-25341 and fix it if it is affected.\n\nWhat it is: CVE-2025-25341 is a high-severity denial of service vulnerability in n/a, published on 26 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25341 exists.\n\nAffected packages and fixed versions:\n- libxmljs (npm): affected all versions up to 1.0.11; no fix listed\n- libxmljs (npm): affected all versions up to 1.0.11; no fix listed\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-25341/ (Markdown: https://insights.sbomify.com/CVE-2025-25341/index.md)","id":"CVE-2025-25341","markdown":"https://insights.sbomify.com/CVE-2025-25341/index.md","name":"CVE-2025-25341","record":{"aliases":["GHSA-jv72-59wq-8rxm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js XML library","requires_auth":"none","summary":"Attackers can cause a segmentation fault and denial of service in libxmljs by parsing specially crafted XML documents.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libxmljs","vendor":"libxmljs_project"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"A vulnerability exists in the libxmljs 1.0.11 when parsing a specially crafted XML document. Accessing the internal _ref property on entity_ref and entity_decl nodes causes a segmentation fault, potentially leading to a denial-of-service (DoS).","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"libxmljs has segmentation fault, potentially leading to a denial-of-service (DoS)","id":"CVE-2025-25341","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-25343"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.11"],"package":"libxmljs","purl":null,"source":"GHSA-jv72-59wq-8rxm"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.11"],"package":"libxmljs","purl":"pkg:npm/libxmljs","source":"GHSA-jv72-59wq-8rxm"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-25334"},"products":["n/a"],"published":"2025-12-26","related":[{"cvss_score":8.1,"headline":"libxmljs attrs type confusion RCE","id":"CVE-2024-34391","kev_date_added":null,"published":"2024-05-02"},{"cvss_score":8.1,"headline":"libxmljs namespaces type confusion RCE","id":"CVE-2024-34392","kev_date_added":null,"published":"2024-05-02"},{"cvss_score":7.5,"headline":"Denial of Service (DoS)","id":"CVE-2022-21144","kev_date_added":null,"published":"2022-05-01"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-26","vendors":["n/a"]},"summary":"Attackers can cause a segmentation fault and denial of service in libxmljs by parsing specially crafted XML documents.","url":"https://insights.sbomify.com/CVE-2025-25341/"}