CVE-2026-66293
Low 2.1No known exploitationFix availableXML comment injection in Saxy encoder via unescaped double hyphen
Record last updated
CVSS score
Low on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
No EPSS score available
CISA remediation deadline
Not in the KEV catalog
Description
XML injection in the encoder of Saxy. Saxy.Encoder does not neutralize the -- sequence in XML comment content: escape_comment/2 returns the comment binary unchanged in every clause and only appends a space when the comment ends in a single -, so neither an interior -- nor a full --> is escaped or rejected before the encoder wraps the content in the delimiters. When an application serializes attacker-controlled text as a comment, through Saxy.XML.comment/1 or a raw {:comment, text} simple form child, the attacker can close the comment early with --> and inject arbitrary sibling markup into the serialized document. A downstream parser then sees elements, attributes, and text that the application never built. Where the document is rendered as HTML or SVG, the injected markup executes as stored cross-site scripting; where it is consumed by another XML processor, the attacker can forge data that the producing application never emitted. Documents that Saxy only parses are not a vector. This issue affects saxy: from 0.7.0 before 1.7.0.
Weakness: CWE-91
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Mitigation
- Reject or rewrite the -- sequence in untrusted text before passing it to Saxy.XML.comment/1, for example by replacing -- with - -. Alternatively, stop emitting untrusted data as XML comments. Comments carry no semantic payload for consumers, so the text can usually be moved into an element or a CDATA section instead. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| qcam | saxy | from 0.7.0 before 1.7.0 | 1.7.0 | CVE Program |
| qcam | saxy | from 7266632e9407842f28ffac254c56dc41210a5690 before 6d12ee12b9e32e86ef598b3f3cafccd1840b2f41 | 6d12ee12b9e32e86ef598b3f3cafccd1840b2f41 | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit 6d12ee1 in qcam/saxy (opens in a new tab)patch
- https://github.com/qcam/saxy/security/advisories/GHSA-mm3m-xwmf-v698 (opens in a new tab)vendor-advisory, related
- EEF CNA record for CVE-2026-66293 (opens in a new tab)related
- Introducing commit 7266632 in qcam/saxy (opens in a new tab)related
- OSV record EEF-CVE-2026-66293 (opens in a new tab)related