Detections
Analytics

SCA: security update for guzzlehttp/guzzle-services (GHSA-q8r6-5hfw-5jff)

medium Tenable Self-Hosted Container Security Plugin ID 443086

Description

There are packages installed that are affected by a vulnerability referenced in the following CVE:

 - 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. (CVE-2026-53723)

Solution

Update the guzzlehttp/guzzle-services library and its related packages to version 1.5.4 or later.

See Also

https://github.com/advisories/GHSA-q8r6-5hfw-5jff

Plugin Details

Severity: Medium

ID: 443086

Version: Revision 1.3

Type: Local

Family: SCA Checks

Published: 6/11/2026

Updated: 7/2/2026

Supported Sensors: Tenable Cloud Security, Tenable Self-Hosted Container Security

Risk Information

VPR

Risk Factor: Low

Score: 1.2

Percentile: 0.01

Vendor

Vendor Severity: Medium

CVSS v2

Risk Factor: Medium

Base Score: 5

Temporal Score: 3.7

Vector: CVSS2#AV:N/AC:L/Au:N/C:N/I:P/A:N

CVSS Score Source: CVE-2026-53723

CVSS v3

Risk Factor: Medium

Base Score: 5.8

Temporal Score: 5.1

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

Exploit Ease: No known exploits are available

Patch Publication Date: 6/11/2026

Vulnerability Publication Date: 6/11/2026

Reference Information

CVE: CVE-2026-53723