Quick answers
- Is CVE-2026-66293 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66293 being exploited in the wild.
- How severe is CVE-2026-66293?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- Saxy 0.7.0 before 1.7.0.
- Is there a fix for CVE-2026-66293?
- Yes: fixed in 1.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66293 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-66293?
- Check whether you run Saxy 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.
How to fix
- Fixed in: 1.7.0
Technical details
The escape_comment/2 function in Saxy.Encoder fails to neutralize the -- sequence within XML comment content, allowing an attacker to close a comment prematurely with --> and inject sibling markup. The vulnerability exists in serialization paths via Saxy.XML.comment/1 and raw {:comment, text} forms, and requires the application to serialize attacker-controlled text as a comment; parsing-only usage is not affected.
Affected products
- Saxy Saxy 0.7.0 before 1.7.0
Timeline
- 2026-11-06: disclosed