CVE-2026-66294 is an XML injection vulnerability in the Saxy XML encoder used by the qcam project. The flaw occurs because the encoder's CDATA serialization does not properly handle the substring ]]> inside CDATA sections, allowing an attacker to prematurely terminate the CDATA block and inject arbitrary XML markup. This can lead to forged or overridden XML elements and attributes in documents such as SOAP envelopes, RSS/Atom feeds, sitemaps, SVG, or other XML exports that include untrusted text in CDATA nodes. Versions of saxy from 0.7.0 up to but not including 1.7.0 are affected. The issue is fixed in version 1.7.0.
CVE-2026-66295 is an XML Injection vulnerability in the qcam saxy XML encoder versions from 0.7.0 up to but not including 1.7.0. The vulnerability arises because the encoder writes processing instruction targets and content verbatim without validation or escaping, allowing attackers to inject arbitrary XML constructs. This can cause the serialized XML document to differ from the intended structure, potentially leading to forged records, injected stylesheets, or malicious content in XML or SVG outputs. The issue is fixed in version 1.7.0.
CVE-2026-66293 is an XML injection vulnerability in the Saxy encoder component of the qcam saxy library. The encoder fails to properly neutralize the '--' sequence within XML comment content, allowing an attacker to prematurely close comments and inject arbitrary sibling markup. This can lead to stored cross-site scripting (XSS) when rendered as HTML or SVG, or data forgery when processed by other XML consumers. The vulnerability affects saxy versions from 0.7.0 up to but not including 1.7.0. A fix is available starting from version 1.7.0.
CVE-2026-53582 is an XML Injection vulnerability in the OPNsense core Trust module prior to version 26.1.10. It allows users with CA Manager or Certificate Manager privileges to inject crafted refid values into XPath expressions, enabling them to recover sensitive configuration data character by character. Exposed data may include password hashes, API credentials, private keys, and VPN key material, potentially leading to privilege escalation and compromise of other security domains. The issue is fixed in OPNsense version 26.1.10.
CVE-2026-102037 is a high-severity XML Injection vulnerability in the Unified Threat Management daemon (utmd) of Juniper Networks Junos OS on SRX Series devices. It allows an unauthenticated network attacker to execute arbitrary device configuration commands with root privileges by exploiting a malicious response from a configured custom URL-feed server. The vulnerability affects multiple versions of Junos OS prior to specific patch releases. The CVSS score is 8.1, indicating a high impact on confidentiality, integrity, and availability.
Adobe Experience Manager 6.5 contains an XML Injection (Blind XPath Injection) vulnerability that allows a low-privileged attacker to bypass security features and gain unauthorized read and limited write access. Exploitation does not require user interaction. The vulnerability affects versions up to and including 6.5.25. The CVSS score is 7.1, indicating a high severity issue.
CVE-2026-102116 is a path traversal vulnerability in Kiteworks Email Protection Gateway that allows an authenticated administrator to write files outside intended directories. This can lead to execution of arbitrary files by the application, potentially resulting in remote code execution with the privileges of the service account.
CVE-2026-103044 is a critical XML injection vulnerability, also known as blind XPath injection, in the Mediawiki EasyTimeline extension maintained by The Wikimedia Foundation. This flaw allows attackers to inject malicious XML content, potentially impacting confidentiality, integrity, and availability. The vulnerability affects versions before 1.43.10, 1.45.5, and 1.46.1 of the EasyTimeline extension. It has a high CVSS score of 9.8, indicating severe risk if exploited.
ManageEngine OpManager versions 12.8.709 and below contain an XML Injection vulnerability (CWE-91) in the Rule Tracking Compare Policies feature. This vulnerability allows an attacker with low privileges to perform blind XPath injection, potentially leading to unauthorized data disclosure. The vulnerability has a high severity with a CVSS score of 7.7. No known exploits are reported in the wild, and no official patch information is provided in the input data.
NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause an XML injection. A successful exploit of this vulnerability might lead to data tampering and denial of service.
IBM webMethods Integration Server 11.1 is affected by an XML external entity (XXE) injection vulnerability, also known as Blind XPath Injection (CWE-91). This vulnerability allows a remote attacker with limited privileges to exploit XML processing to potentially expose sensitive information or cause resource exhaustion. The vulnerability has a high severity rating with a CVSS score of 7.8.
CVE-2026-48590 is an XML Injection vulnerability in the joshnuss xml_builder library affecting versions from 0.0.1 up to but not including 2.4.1. The vulnerability arises because element names, attribute names, and doctype identifiers are inserted into XML output without proper validation or escaping of special characters. This allows an attacker who can control these inputs to inject arbitrary XML markup, potentially leading to content spoofing or manipulation of the XML document structure. The CVSS score is low (2.1), indicating limited impact and attack complexity.
CVE-2026-47080 is an XML Injection vulnerability in the joshnuss xml_builder library affecting versions from 0.0.7 up to but not including 2.4.1. The flaw arises because the escape/1 function does not properly handle embedded CDATA section terminators (]]>) in user-supplied input, allowing an attacker to prematurely close CDATA sections and inject arbitrary XML content. This can lead to content spoofing and XML injection attacks. The vulnerability has a low CVSS 4.0 score of 2.1, indicating limited impact and complexity.
Astro is a web framework for content-driven websites. In versions 1.0.0 through 4.0.18, the source.title and enclosure.type item fields in packages/astro-rss/src/index.ts are interpolated directly into XML template strings without XML-character escaping before being parsed by fast-xml-parser. Both fields are validated only as z.string(), placing no restriction on XML special characters. An attacker who controls these values can inject arbitrary XML into the generated RSS feed: a value containing " can break out of an attribute (as with enclosure.type), and a value containing </source> can close an element early and inject additional nodes (as with source.title). This corrupts feed structure, injects false metadata (for example, a fake <link> pointing to a malicious URL), and can cause feed readers to misparse or display attacker-controlled content. In SSR mode (output: 'server'), the poisoned feed is served on every request to all subscribers. This issue has been fixed in version 4.0.19.
Improper output neutralization (XML injection) in QDom comment, CDATA, and processing-instruction serialization in Qt XML from 4.0.0 through 6.11 allows untrusted text serialized by an application into those nodes to inject arbitrary XML markup, because the node terminators are not escaped under the default InvalidDataPolicy (AcceptInvalidChars). Fixed in Qt 6.12.
Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's self-hosted SAML application IdP built the signed SAML response and assertion by string-substituting user-controlled profile attributes such as name, email, and custom attribute-mapping values into element-text placeholders of a SAML XML template using samlify 2.10.0, which left those placeholders unescaped. An authenticated low-privilege user could place XML markup in a profile attribute so Logto signed a forged SAML attribute, such as an arbitrary role, allowing privilege escalation at relying Service Providers that authorize on SAML attributes. This issue is fixed in version 1.41.0.
Guzzle Services versions prior to 1.5.3 improperly serialize scalar XML element values containing the CDATA terminator ']]>', causing early CDATA section closure and injection of attacker-controlled XML elements in outgoing requests. This vulnerability affects applications that serialize untrusted input into XML element text parameters with location: xml, potentially allowing alteration of operation semantics or injection of conflicting elements. The issue does not affect response parsing directly and is fixed in version 1.5.3 by safely handling embedded CDATA terminators.
CVE-2026-46490 is an XML Injection vulnerability in the Node.js library samlify prior to version 2.13.0. The issue arises because samlify escapes only attribute contexts during template substitution, but does not escape values inserted into element text such as <saml:AttributeValue>. This allows an attacker to inject XML markup into attribute values, resulting in additional <saml:Attribute> elements inside signed assertions. Consequently, the Identity Provider (IdP) signs tampered assertions, and the Service Provider (SP) accepts injected attributes as trusted, enabling privilege escalation when attributes control authorization. The vulnerability has been patched in samlify version 2.13.0.
pam_usb versions prior to 0.9.0 are vulnerable to an XML Injection (Blind XPath Injection) due to improper validation of user- and device-supplied identifiers used in XPath queries against /etc/pamusb.conf. This allows injection of arbitrary XPath predicates. The vulnerability is fixed in version 0.9.0. The CVSS score is 6.5, indicating a medium severity issue.
authentik is an open-source identity provider. Versions 2025.12.4 and prior, and versions 2026.2.0-rc1 through 2026.2.2 were vulnerable to Authentication Bypass through SAML NameID XML Comment Injection. Due to how authentik extracted the NameID value from a SAML assertion, it was possible for an attacker to trick authentik into only seeing a part of the NameID value, potentially allowing an attacker to gain access to other accounts. This issue could be exploited on an authentik instance with a SAML Source, where the attacker had an account on the SAML Source and the ability to modify their NameID value (commonly username or E-mail), and XML Signing was enabled. The attacker could modify the SAML assertion given to authentik by injecting a comment within the NameID value, which effectively truncated the NameID value to the snippet before the comment, and gave the attacker access to any user account. This issue has been fixed in versions 2025.12.5 and 2026.2.3.