Quick answers
- Is CVE-2026-66295 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66295 being exploited in the wild.
- How severe is CVE-2026-66295?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- Saxy 0.7.0 to before 1.7.0.
- Is there a fix for CVE-2026-66295?
- 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-66295 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-66295?
- 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 XML encoder concatenates processing instruction target and content directly between <? and ?> delimiters without validation or escaping. An attacker can include ?> in either field to prematurely terminate the construct and inject arbitrary XML elements, attributes, or further processing instructions at document level. The injected content parses silently because an appended <? keeps the encoder's own terminator well-formed, resulting in a tree discrepancy between what the application encodes and what a downstream parser reads.
Affected products
- Saxy Saxy 0.7.0 to before 1.7.0