{"affected":[{"package":{"ecosystem":"Hex","name":"saxy","purl":"pkg:hex/saxy"},"ranges":[{"events":[{"introduced":"0.7.0"},{"fixed":"1.7.0"}],"type":"SEMVER"}],"versions":["0.7.0","0.8.0","0.9.0","0.9.1","0.10.0","1.0.0","1.1.0","1.2.0","1.2.1","1.2.2","1.3.0","1.4.0","1.5.0","1.6.0","1.6.1"]},{"ranges":[{"events":[{"introduced":"7266632e9407842f28ffac254c56dc41210a5690"},{"fixed":"71d99fae12f1d6596f5edb57b71f26ba854f4d33"}],"repo":"https://github.com/qcam/saxy","type":"GIT"}]}],"aliases":["GHSA-hq6g-j46w-wx72","CVE-2026-66294"],"credits":[{"name":"Peter Ullrich","type":"FINDER"},{"name":"Peter Ullrich","type":"REPORTER"},{"name":"Peter Ullrich","type":"REMEDIATION_DEVELOPER"},{"name":"Cẩm Huỳnh","type":"REMEDIATION_REVIEWER"},{"name":"Jonatan Männchen / EEF","type":"ANALYST"},{"name":"Peter Ullrich","type":"COORDINATOR"}],"database_specific":{"capec_ids":["CAPEC-250"],"cpe_ids":["cpe:2.3:a:qcam:saxy:*:*:*:*:*:*:*:*"],"cwe_ids":["CWE-91"]},"details":"## Summary\n\nXML injection in the Saxy XML encoder. `Saxy.Encoder.cdata/1` serializes a `{:cdata, characters}` node by wrapping the supplied characters between `<![CDATA[` and `]]>` and passing the payload through byte for byte. The encoder's character-data and attribute-value paths escape the XML metacharacters `<`, `>`, `&`, `\"`, and `'`, but the CDATA path applies no neutralization at all. XML provides no character escaping mechanism inside a CDATA section, so the only correct way to represent a `]]>` substring is to split the section and rejoin it as `]]]]><![CDATA[>`. Saxy neither performs that split nor rejects the substring.\n\nAn application that renders untrusted text as CDATA, by building the node with `Saxy.XML.cdata/1` and serializing it with `Saxy.encode!/2` or `Saxy.encode_to_iodata!/2`, therefore lets an attacker terminate the section at a position of their choosing. Everything supplied after the `]]>` is emitted outside any CDATA context and is parsed as markup, so a single attacker-controlled text field becomes attacker-controlled document structure: arbitrary sibling elements and attributes that the application never built. Downstream consumers of the serialized document accept the injected markup as genuine. Services that generate SOAP envelopes, RSS or Atom feeds, sitemaps, SVG, or XML exports from user-supplied content can have trusted fields forged or overridden. Applications that never place untrusted text in a CDATA node are not affected.\n\nThis issue affects saxy: from 0.7.0 before 1.7.0.\n\n## Workarounds\n\nRender untrusted text as ordinary character data instead of CDATA, by passing a plain string or `Saxy.XML.characters/1` to the element builder. That encoder path escapes the XML metacharacters and preserves the same text content.\n\nIf a CDATA section is required, split the terminator in application code before building the node: replace every occurrence of `]]>` in the untrusted text with `]]]]><![CDATA[>` and pass the result to `Saxy.XML.cdata/1`. Once the encoder wraps that payload, the output is the standard split encoding.","id":"EEF-CVE-2026-66294","modified":"2026-11-06T10:16:50.022265Z","published":"2026-11-06T10:16:49.656Z","references":[{"type":"ADVISORY","url":"https://github.com/qcam/saxy/security/advisories/GHSA-hq6g-j46w-wx72"},{"type":"WEB","url":"https://cna.erlef.org/cves/CVE-2026-66294.html"},{"type":"WEB","url":"https://github.com/qcam/saxy/commit/7266632e9407842f28ffac254c56dc41210a5690"},{"type":"FIX","url":"https://github.com/qcam/saxy/commit/71d99fae12f1d6596f5edb57b71f26ba854f4d33"},{"type":"PACKAGE","url":"https://hex.pm/packages/saxy"}],"related":[],"schema_version":"1.7.3","severity":[{"score":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","type":"CVSS_V4"}],"summary":"XML injection in Saxy via unescaped CDATA section terminator","upstream":[]}