{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-86144 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-86144 is a medium-severity server-side request forgery vulnerability in Xmlsoft Libxml2, published on 5 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-86144 and fix it if it is affected.\n\nWhat it is: CVE-2026-86144 is a medium-severity server-side request forgery vulnerability in Xmlsoft Libxml2, published on 5 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-86144 in the wild and no public exploit code.\n\nAffected product: Xmlsoft Libxml2. 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-86144/ (Markdown: https://insights.sbomify.com/CVE-2026-86144/index.md)","id":"CVE-2026-86144","markdown":"https://insights.sbomify.com/CVE-2026-86144/index.md","name":"CVE-2026-86144","record":{"aliases":["AZL-99702","BELL-CVE-2026-86144","DEBIAN-CVE-2026-86144","ECHO-0085-7842-c8d6","GHSA-h6w8-m27h-f268","ROOT-OS-DEBIAN-12-CVE-2026-86144","UBUNTU-CVE-2026-86144"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"libxml2 XML library","requires_auth":"none","summary":"Attackers can trigger SSRF or DoS via XInclude processing in libxml2 due to missing parse flag propagation, affecting applications using the library.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libxml2","vendor":"xmlsoft"}],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-669","name":"Incorrect Resource Transfer Between Spheres"}],"description":"In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags. This has security relevance for, for example, the XML_PARSE_NONET flag, if (without it) a custom resource loader accesses the internet and triggers XML external entity injection, SSRF, or a denial of service (e.g., for an attacker-controlled internet resource that is intentionally slow).","ecosystems":[],"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":"Server-side request forgery in libxml2","id":"CVE-2026-86144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"xmlsoft:libxml2","products":["xmlsoft:libxml2"],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in PCRE2","id":"CVE-2026-86145"},"packages":[],"prev":{"headline":"Integer overflow in libxml2","id":"CVE-2026-86143"},"products":["libxml2"],"published":"2026-09-05","related":[{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2017-16931","kev_date_added":null,"published":"2017-11-23"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2017-8872","kev_date_added":null,"published":"2017-05-10"},{"cvss_score":8.1,"headline":"Use after free in libxml2","id":"CVE-2022-49043","kev_date_added":null,"published":"2025-01-26"},{"cvss_score":8,"headline":"Memory corruption in libxml2","id":"CVE-2026-86140","kev_date_added":null,"published":"2026-09-05"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2024-34459","kev_date_added":null,"published":"2024-05-13"},{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2024-25062","kev_date_added":null,"published":"2024-02-04"},{"cvss_score":7.5,"headline":"Nokogiri gem, via libxml, is affected by DoS vulnerabilities","id":"CVE-2017-16932","kev_date_added":null,"published":"2017-11-23"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["xmlsoft"]},"summary":"Attackers can trigger SSRF or DoS via XInclude processing in libxml2 due to missing parse flag propagation, affecting applications using the library.","url":"https://insights.sbomify.com/CVE-2026-86144/"}