Quick answers
- Is CVE-2026-47080 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47080 being exploited in the wild.
- How severe is CVE-2026-47080?
- Informational severity, published 21 August 2026.
- Which products and versions are affected?
- Joshnuss Xml Builder 0.0.7 before 2.4.1.
- Is there a fix for CVE-2026-47080?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47080 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47080?
- Check whether you run Joshnuss Xml Builder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an XML injection flaw in the escape/1 function (specifically the {:cdata, data} clause) within lib/xml_builder.ex. The vulnerable code concatenates user-supplied data directly between CDATA markers <![CDATA[ and ]]> without splitting or escaping the CDATA terminator sequence ]]>. An attacker who controls input to XmlBuilder.generate/1 or XmlBuilder.generate/2 can embed ]]> to prematurely close the CDATA section, allowing injection of arbitrary XML markup that will be parsed as valid XML by downstream consumers. The attack requires the ability to supply input to the affected functions; no authentication or special preconditions are documented. The fix is available in version 2.4.1 and later; versions 0.0.7 through 2.4.0 are affected.
Affected products
- joshnuss xml_builder 0.0.7 before 2.4.1
Timeline
- 2026-08-21: disclosed