Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.2%top 87%

CVE-2026-53723: CWE-20: Improper Input Validation in guzzle guzzle-services

0
Medium
VulnerabilityCVE-2026-53723cvecve-2026-53723cwe-20cwe-91
Published: 06/11/2026 (06/11/2026, 12:42:42 UTC)
Source: CVE Database V5
Vendor/Project: guzzle
Product: guzzle-services

Description

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.

CVSS v3.1

Score 5.8medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Affected software

Packagistmore threats →ai
guzzle/guzzle-services
pkg:composer/guzzle/guzzle-services
Affected versions
<1.5.3

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/16/2026, 10:55:31 UTC

Technical Analysis

CVE-2026-53723 is an improper input validation vulnerability in guzzle-services prior to version 1.5.3. The XML request serializer uses CDATA sections to write values containing special characters, but does not safely handle embedded CDATA terminators ']]>'. If attacker-controlled input includes ']]>', the CDATA section closes prematurely, and the remainder is interpreted as XML markup, allowing injection of attacker-controlled elements into outgoing XML requests. This affects applications using guzzlehttp/guzzle-services to serialize outgoing requests with parameters or additionalParameters located in XML element text (not attributes), where the input is untrusted and unconstrained. The vulnerability can lead to altered operation semantics, smuggling of privileged fields, or conflicting duplicated elements in downstream services that parse the XML structurally. The vulnerability is patched in version 1.5.3 and later by splitting embedded CDATA terminators before serialization, preserving the original scalar value as XML text and preventing injection. Workarounds include constraining input to exclude ']]>' or avoiding serialization of untrusted data into XML element text until patched.

Potential Impact

The vulnerability allows an attacker controlling input serialized into XML element text to inject additional XML elements into outgoing requests by prematurely closing CDATA sections. This can alter the semantics of operations performed by downstream services, potentially smuggling privileged fields, bypassing parameter boundaries, or creating conflicting duplicated elements. There is no direct impact on confidentiality or availability, but integrity of outgoing XML request bodies can be compromised. The vulnerability does not affect response parsing unless attacker-controlled response data is later reused in requests. The CVSS 3.1 base score is 5.8 (medium severity) reflecting network attack vector, low complexity, no privileges required, no user interaction, scope change, no confidentiality impact, limited integrity impact, and no availability impact.

Mitigation Recommendations

A fix is available in guzzle-services version 1.5.3 and later, which safely handles embedded CDATA terminators to prevent injection. Users should upgrade to version 1.5.3 or newer. As a workaround before patching, constrain attacker-controlled XML element values with strict enums, patterns, or custom filters that exclude the CDATA terminator sequence ']]>', or avoid serializing untrusted input into XML element text parameters with location: xml. Review service descriptions for parameters using location: xml to identify affected areas. XML attributes are not affected by this issue. No action is required if only response deserialization is used without subsequent request serialization of untrusted data.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-06-10T16:43:31.242Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a2ac2f3815e7002b8f50211

Added to database: 06/11/2026, 14:15:15 UTC

Last enriched: 07/16/2026, 10:55:31 UTC

Last updated: 07/31/2026, 19:22:59 UTC

Views: 75

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses