{"answers":{"affected":"1 open source package ship an affected version, including xml_builder.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47080 exists.","fix":"Upgrade xml_builder to 2.4.1 or later.","what":"CVE-2026-47080 is a low-severity vulnerability in joshnuss xml_builder, published on 21 Aug 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-47080 and fix it if it is affected.\n\nWhat it is: CVE-2026-47080 is a low-severity vulnerability in joshnuss xml_builder, published on 21 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47080 exists.\n\nAffected packages and fixed versions:\n- xml_builder (Hex): affected from 0.0.7; fixed in 2.4.1\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-47080/ (Markdown: https://insights.sbomify.com/CVE-2026-47080/index.md)","id":"CVE-2026-47080","markdown":"https://insights.sbomify.com/CVE-2026-47080/index.md","name":"CVE-2026-47080","record":{"aliases":["EEF-CVE-2026-47080","GHSA-67r9-hmxw-h595"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir XML library","requires_auth":"none","summary":"Attackers can inject arbitrary XML markup by breaking out of CDATA sections in xml_builder, potentially corrupting downstream XML processing.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-91","name":"XML Injection"}],"description":"XML Injection vulnerability in joshnuss xml_builder (XmlBuilder module) allows Content Spoofing, XML Injection.\n\nThis vulnerability is associated with program files lib/xml_builder.ex and program routines XmlBuilder.generate/1, XmlBuilder.generate/2, XmlBuilder.escape/1.\n\nThe escape/1 clause for {:cdata, data} in lib/xml_builder.ex concatenates data verbatim between the CDATA opener \u003c![CDATA[ and closer ]]\u003e without rewriting or splitting on the embedded ]]\u003e sequence. Because CDATA sections have no internal escape mechanism, the only safe way to embed arbitrary bytes is to split on ]]\u003e and emit adjacent CDATA sections. An attacker who can supply input containing ]]\u003e closes the CDATA section early; any bytes that follow are parsed as ordinary XML markup by downstream consumers, allowing injection of arbitrary elements, text, or entity references into the output document.\n\nThis issue affects xml_builder: from 0.0.7 before 2.4.1.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"CDATA Section Breakout via Unsanitised ]]\u003e in xml_builder","id":"CVE-2026-47080","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"other","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Information disclosure in Cyrus IMAP","id":"CVE-2026-47081"},"packages":[{"ecosystem":"Hex","fixed":["2.4.1"],"introduced":["0.0.7"],"last_affected":[],"package":"xml_builder","purl":"pkg:hex/xml_builder","source":"EEF-CVE-2026-47080"}],"prev":{"headline":"Round-trip Corruption via Improper Entity Escaping in xml_builder","id":"CVE-2026-47079"},"products":["xml_builder"],"published":"2026-08-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["joshnuss"]},"summary":"Attackers can inject arbitrary XML markup by breaking out of CDATA sections in xml_builder, potentially corrupting downstream XML processing.","url":"https://insights.sbomify.com/CVE-2026-47080/"}