# CVE-2026-53723: guzzlehttp/guzzle-services' XML Request Serialization Vulnerable to XML Injection via CDATA Terminator > Attackers can inject XML markup into outgoing requests via CDATA terminator bypass, potentially altering service semantics or bypassing parameter boundaries. - **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Jun 2026 - **Updated:** 11 Jun 2026 - **Also known as:** GHSA-q8r6-5hfw-5jff ## What is CVE-2026-53723? CVE-2026-53723 is a medium-severity vulnerability in guzzle-services, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Guzzle Services provides an implementation of the Guzzle Command library that uses Guzzle service descriptions to describe web services, serialize requests, and parse responses into easy to use model structures. Versions prior ro 1.5.4 do not safely serialize scalar XML element values containing the CDATA terminator `]]>`. The XML request serializer writes values containing `<`, `>`, or `&` with `XMLWriter::writeCData($value)`. If attacker-controlled input contains `]]>`, the CDATA section closes early and the remainder is interpreted as XML markup. This is an outgoing request-body integrity issue, not a response parsing issue. The attacker does not need to control the service description or schema. Users are affected when all of the following are true: the application uses `guzzlehttp/guzzle-services` to serialize outgoing requests; a request parameter or `additionalParameters` schema uses `location: xml`; the value is serialized as XML element text, not an XML attribute; the value can contain attacker-controlled, user-controlled, tenant-controlled, or otherwise untrusted input; the value is not constrained by a safe `enum`, `pattern`, or custom filter that excludes `]]>`; and the downstream service parses the generated XML structurally and may act on unexpected, duplicated, or injected elements. Applications that serialize untrusted input into `location: xml` request parameters can emit XML containing attacker-controlled elements outside the intended text node. Depending on the receiving service, this can alter operation semantics, smuggle privileged fields, bypass modeled parameter boundaries, or create conflicting duplicated elements. Fixed service descriptions are sufficient if they contain an XML element parameter populated from attacker-controlled input. Users are not directly affected if they only use Guzzle Services to deserialize HTTP response bodies. Response XML parsing uses the response XML location visitor and does not invoke the vulnerable request XML serializer. Response bodies matter only in a second-order flow, such as parsing attacker-controlled response XML, storing or forwarding a parsed string value, and later using it as a `location: xml` request parameter. The issue is patched in `1.5.3` and later by safely splitting embedded CDATA terminators before serialization. The fix preserves the original scalar value as XML text and prevents injected nodes. As a workaround, constrain attacker-controlled XML element values with a strict `enum`, `pattern`, or custom filter that excludes `]]>`, or avoid serializing untrusted data into `location: xml` element text until patched. Where appropriate for the service schema, XML attributes are not affected because they are written with XMLWriter attribute APIs rather than CDATA sections. To determine whether action is needed, search service descriptions for request parameters using `location: xml`, including operation `parameters` and `additionalParameters`. Response-only `models` are not directly affected unless parsed values are reused for request serialization. For object and array parameters, review nested scalar properties because leaf element values can still be affected. Weakness: CWE-91 (XML Injection), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2026-53723? 2 open source packages ship an affected version, including guzzlehttp/guzzle-services. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `guzzlehttp/guzzle-services` | Packagist | All versions | 1.5.4 | | `guzzlehttp/guzzle-services` | Packagist | All versions | 1.5.4 | ## How do I fix CVE-2026-53723? Upgrade guzzlehttp/guzzle-services to 1.5.4 or later. ## Is CVE-2026-53723 being exploited? There is no known exploitation of CVE-2026-53723 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-53723 and fix it if it is affected. What it is: CVE-2026-53723 is a medium-severity vulnerability in guzzle-services, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-53723 in the wild and no public exploit code. Affected packages and fixed versions: - guzzlehttp/guzzle-services (Packagist): affected all versions; fixed in 1.5.4 - guzzlehttp/guzzle-services (Packagist): affected all versions; fixed in 1.5.4 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-53723/ (Markdown: https://insights.sbomify.com/CVE-2026-53723/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53723 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53723 - OSV: https://osv.dev/vulnerability/CVE-2026-53723 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-53723/ Summaries are generated and may contain mistakes; the official description above is the record.