Is CVE-2026-66294 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-66294 being exploited in the wild.

How severe is CVE-2026-66294?

Informational severity, published 6 November 2026.

Is there a fix for CVE-2026-66294?

Yes: fixed in Saxy 1.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-66294 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-66294?

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.

CVE-2026-66294: Saxy XML encoder CDATA injection

CVE-2026-66294 · Severity: info · Published 2026-11-06

Saxy is an XML encoder used to serialize data into XML documents. When applications use Saxy to wrap untrusted text in CDATA sections, an attacker can inject the CDATA terminator sequence to break out and inject arbitrary XML markup, potentially forging trusted fields in SOAP envelopes, RSS feeds, sitemaps, or other XML exports. Applications that never place untrusted text in CDATA nodes are unaffected.

Technologies: Saxy. Vendors: Saxy.

Quick answers

Is CVE-2026-66294 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-66294 being exploited in the wild.
How severe is CVE-2026-66294?: 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-66294?: Yes: fixed in Saxy 1.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-66294 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-66294?: 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: Saxy 1.7.0

Technical details

Saxy.Encoder.cdata/1 fails to escape or reject the ]]> sequence within CDATA sections; XML provides no character escaping inside CDATA, so the correct mitigation is to split the CDATA at ]]> boundaries. An attacker supplying the ]]> substring in untrusted text can terminate the CDATA section prematurely, causing subsequent payload to parse as XML markup rather than character data. This is a structural XML injection affecting applications that build CDATA nodes from user input and serialize them with Saxy.encode!/2 or Saxy.encode_to_iodata!/2.

Affected products

Saxy Saxy 0.7.0 before 1.7.0

Timeline

2026-11-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.