CVE-2026-53723: Guzzlehttp/guzzle services Guzzlehttp/guzzle-services' XML Request Serialization Vulnerable Vulnerability

MODERATE
Advisory Identifier: GHSA-q8r6-5hfw-5jff
CVSS 5.8
CWE-91 CWE-20
Published
Advisory Summary

CVE-2026-53723 is a MODERATE (CVSS 5.8) guzzlehttp/guzzle-services' xml request serialization vulnerable vulnerability (CWE-91: XML Injection (aka Blind XPath Injection)) affecting Guzzlehttp/guzzle services libraries in the Packagist ecosystem. The issue involves guzzlehttp/guzzle-services' xml request serialization vulnerable to xml injection via cdata terminator. Remediation is available by upgrading affected packages to version 1.5.4.

CVE-2026-53723 at a Glance

CVE Identifier CVE-2026-53723
GHSA Identifier GHSA-q8r6-5hfw-5jff
Severity MODERATE
CVSS v3.1 Base Score 5.8
CWE Classification CWE-91: XML Injection (aka Blind XPath Injection)
Affected Product Guzzlehttp/guzzle services
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 5.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N).

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

How to Fix CVE-2026-53723

To remediate this vulnerability, upgrade all affected Guzzlehttp/guzzle services dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

guzzlehttp/guzzle-services fixed: 1.5.4
Upgrade guzzlehttp/guzzle-services to 1.5.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for guzzlehttp/guzzle-services

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-53723, inspect your project dependencies for Guzzlehttp/guzzle services:

inspect dependencies for guzzlehttp/guzzle-services

Analyze the terminal output to locate any version of Guzzlehttp/guzzle services in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.5.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-91: XML Injection (aka Blind XPath Injection), where the product does not properly neutralize special elements that are used in xml, allowing attackers to modify the syntax, content, or commands of the xml before it is processed by an end system. In Guzzlehttp/guzzle services, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `guzzlehttp/guzzle-services` does 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: 1. The application uses `guzzlehttp/guzzle-services` to serialize outgoing requests. 2. A request parameter or `additionalParameters` schema uses `location: xml`. 3. The value is serialized as XML element text, not an XML attribute. 4. The value can contain attacker-controlled, user-controlled, tenant-controlled, or otherwise untrusted input. 5. The value is not constrained by a safe `enum`, `pattern`, or custom filter that excludes `]]>`. 6. 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. Example fixed service description: ```php 'DisplayName' => ['location' => 'xml', 'type' => 'string'] ``` If an attacker-controlled display name is: ```text Alice]]></DisplayName><Role>admin</Role><DisplayName><![CDATA[ ``` the vulnerable serializer can emit an injected element outside the intended `DisplayName` text node: ```xml <Request><DisplayName><![CDATA[Alice]]></DisplayName><Role>admin</Role><DisplayName><![CDATA[]]></DisplayName></Request> ``` If the downstream service treats `<Role>` as meaningful, the attacker has set a field the modeled `DisplayName` parameter was not intended to set. ### Patches The issue is patched in `1.5.4` and later by safely splitting embedded CDATA terminators before serialization. The fix preserves the original scalar value as XML text and prevents injected nodes. ### Workarounds If you cannot upgrade immediately, 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. ### References - https://www.w3.org/TR/xml/#sec-cdata-sect - https://www.php.net/manual/en/xmlwriter.writecdata.php - https://www.php.net/manual/en/xmlwriter.text.php

CVE-2026-53723 Affected Guzzlehttp/guzzle services Versions

1 component(s)
Fixed Versions:
1.5.4
Product / Package Ecosystem Affected Versions Fixed Version
guzzlehttp/guzzle-services
Packagist
< 1.5.4
1.5.4

References

Frequently Asked Questions

What is CVE-2026-53723?
CVE-2026-53723 is a security vulnerability in Guzzlehttp/guzzle services involving guzzlehttp/guzzle-services' XML Request Serialization Vulnerable to XML Injection via CDATA Terminator under CWE-91: XML Injection (aka Blind XPath Injection).
Which Guzzlehttp/guzzle services versions are affected?
Affected versions include releases prior to 1.5.4 across affected packages: guzzlehttp/guzzle-services.
What version fixes CVE-2026-53723?
Upgrading to 1.5.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is guzzlehttp/guzzle-services affected?
Yes, guzzlehttp/guzzle-services is affected in releases prior to 1.5.4. Upgrade your dependency to 1.5.4 or later.
What is the CVSS score of CVE-2026-53723?
CVE-2026-53723 has a CVSS v3.1 base score of 5.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N.
What CWE is associated with CVE-2026-53723?
CVE-2026-53723 is classified under CWE-91: XML Injection (aka Blind XPath Injection) (The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.).
How can I check Packagist dependencies for CVE-2026-53723?
Run the dependency tree command: 'inspect dependencies for guzzlehttp/guzzle-services'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q8r6-5hfw-5jff",
  "modified" : "2026-07-15T21:58:16Z",
  "published" : "2026-06-11T13:05:01Z",
  "aliases" : [ "CVE-2026-53723" ],
  "summary" : "guzzlehttp/guzzle-services' XML Request Serialization Vulnerable to XML Injection via CDATA Terminator",
  "details" : "### Impact\n\n`guzzlehttp/guzzle-services` does 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.\n\nUsers are affected when all of the following are true:\n\n1. The application uses `guzzlehttp/guzzle-services` to serialize outgoing requests.\n2. A request parameter or `additionalParameters` schema uses `location: xml`.\n3. The value is serialized as XML element text, not an XML attribute.\n4. The value can contain attacker-controlled, user-controlled, tenant-controlled, or otherwise untrusted input.\n5. The value is not constrained by a safe `enum`, `pattern`, or custom filter that excludes `]]>`.\n6. The downstream service parses the generated XML structurally and may act on unexpected, duplicated, or injected elements.\n\nApplications 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.\n\nUsers 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.\n\nExample fixed service description:\n\n```php\n'DisplayName' => ['location' => 'xml', 'type' => 'string']\n```\n\nIf an attacker-controlled display name is:\n\n```text\nAlice]]></DisplayName><Role>admin</Role><DisplayName><![CDATA[\n```\n\nthe vulnerable serializer can emit an injected element outside the intended `DisplayName` text node:\n\n```xml\n<Request><DisplayName><![CDATA[Alice]]></DisplayName><Role>admin</Role><DisplayName><![CDATA[]]></DisplayName></Request>\n```\n\nIf the downstream service treats `<Role>` as meaningful, the attacker has set a field the modeled `DisplayName` parameter was not intended to set.\n\n### Patches\n\nThe issue is patched in `1.5.4` and later by safely splitting embedded CDATA terminators before serialization. The fix preserves the original scalar value as XML text and prevents injected nodes.\n\n### Workarounds\n\nIf you cannot upgrade immediately, 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.\n\nTo 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.\n\n### References\n\n- https://www.w3.org/TR/xml/#sec-cdata-sect\n- https://www.php.net/manual/en/xmlwriter.writecdata.php\n- https://www.php.net/manual/en/xmlwriter.text.php",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "guzzlehttp/guzzle-services"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.5.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/guzzle/guzzle-services/security/advisories/GHSA-q8r6-5hfw-5jff"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-53723"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/guzzlehttp/guzzle-services/CVE-2026-53723.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/guzzle/guzzle-services"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-91" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-11T13:05:01Z",
    "nvd_published_at" : "2026-06-11T14:16:31Z"
  }
}