XML injection via embedded CDATA terminator
Published Jun 11, 2026 · Updated Jun 11, 2026
XML injection in Guzzle Services before 1.5.4 allows remote attackers to alter outgoing XML request bodies through crafted element values. The XML request serializer passes reserved-character text to XMLWriter::writeCData without splitting an embedded CDATA terminator, so trailing input becomes markup. Exploitation requires untrusted text in a location: xml element parameter and a downstream service that acts on injected or duplicated elements.
Summary
What happened
XML injection in Guzzle Services before 1.5.4 allows remote attackers to alter outgoing XML request bodies through crafted element values. The XML request serializer passes reserved-character text to XMLWriter::writeCData without splitting an embedded CDATA terminator, so trailing input becomes markup. Exploitation requires untrusted text in a location: xml element parameter and a downstream service that acts on injected or duplicated elements.
The record
- CVE
- CVE-2026-53723
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Guzzle
- Product
- Guzzle Services
- Classifications
- CWE-20, CWE-91, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.5.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo