CVE-2026-47079
Inappropriate Encoding for Output Context vulnerability in joshnuss …
Inappropriate Encoding for Output Context vulnerability in joshnuss xml_builder (XmlBuilder module) allows Content Spoofing, Cross-site Scripting. This vulnerability is associated with program files lib/xml_builder.ex and program routines XmlBuilder.generate/1, XmlBuilder.generate/2, XmlBuilder.escape_string/1, XmlBuilder.escape_entity/1. XmlBuilder.generate/1 does not escape literal & characters in text or attribute values when they are followed by an entity-like token (lt;, gt;, amp;, quot;, apos;). As a result, attacker-supplied input such as <script> is emitted verbatim into the serialized XML rather than being escaped to &lt;script&gt;. When a downstream XML parser later reads the document, it decodes the entity sequences into the literal characters <script>, promoting inert-looking text into real markup. This allows an attacker to bypass upstream filters that block raw < and > characters, injecting markup into any downstream consumer that parses the produced XML and renders the text content in a markup-sensitive context (HTML, SVG, RSS/Atom feeds). Both element text and attribute values are affected. This issue affects xml_builder: from 0.0.6 before 2.4.1.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- cna.erlef.org/cves/CVE-2026-47079.html
- github.com/joshnuss/xml_builder/commit/c3390e2046ec297b3bb8c30d5779cdfd6508c275
- github.com/joshnuss/xml_builder/security/advisories/GHSA-5hjx-8g53-cmvm
- osv.dev/vulnerability/EEF-CVE-2026-47079
- github.com/joshnuss/xml_builder/commit/aae31e6e8ac837bcbb8afb816c0d14324b5cfe2b
- nvd.nist.gov/vuln/detail/CVE-2026-47079
- cve.org/CVERecord?id=CVE-2026-47079
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.