CVE-2026-66293
Last modified
CVE-2026-66293 is a low-severity vulnerability rated 2.1/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| qcam | saxy | >= 0.7.0, < 1.7.0 |
| qcam | saxy | >= 7266632e9407842f28ffac254c56dc41210a5690, < 6d12ee12b9e32e86ef598b3f3cafccd1840b2f41 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-66293?
How severe is CVE-2026-66293?
How do I fix CVE-2026-66293?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-66279In Connect SDK 4.3.1 and earlier and Flex SDK 3.7.7 and earl…7.2
- CVE-2026-6628A flaw has been found in phili67 Ecclesia CRM up to 8.0.0. T…6.3
- CVE-2026-66280Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-66281In EmberZNet 9.1.1 and earlier, a malformed Discover Attribu…7.5
- CVE-2026-66282In EmberZNet 9.1.1 and earlier, a malformed Publish Billing …7.5
- CVE-2026-6629A vulnerability has been found in Metasoft 美特软件 MetaCRM up t…7.3
- CVE-2026-66294XML injection in the Saxy XML encoder. Saxy.Encoder.cdata/1 …2.1
- CVE-2026-66295Saxy's XML encoder writes the target and the content of a pr…2.1
- CVE-2026-66296Improper Neutralization of Input During Web Page Generation …6.1
- CVE-2026-66297Improper Neutralization of Special Elements used in an OS Co…8
- CVE-2026-66298Origin Validation Error vulnerability in livebook-dev livebo…8.8
- CVE-2026-66299Uncontrolled Resource Consumption vulnerability in Apache To…5.3
Are you affected by CVE-2026-66293?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
