CVE-2026-67354: Guzzle URI Fragments Disclosed Vulnerability
MODERATECVE-2026-67354 is a MODERATE (CVSS 5.9) uri fragments disclosed vulnerability (CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer) affecting Guzzle libraries in the Packagist ecosystem. The issue involves uri fragments disclosed in redirect referer headers. Remediation is available by upgrading affected packages to version 7.15.1.
CVE-2026-67354 at a Glance
Security Impact
CVSS: 5.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2026-67354
To remediate this vulnerability, upgrade all affected Guzzle dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade guzzlehttp/guzzle to 7.15.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for guzzlehttp/guzzle
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-67354, inspect your project dependencies for Guzzle:
inspect dependencies for guzzlehttp/guzzle
Analyze the terminal output to locate any version of Guzzle in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.15.1), 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-212: Improper Removal of Sensitive Information Before Storage or Transfer, where the product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors. In Guzzle, 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
CVE-2026-67354 Affected Guzzle Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
guzzlehttp/guzzle
|
Packagist |
< 7.15.1
|
7.15.1
|
References
Frequently Asked Questions
What is CVE-2026-67354?
Which Guzzle versions are affected?
What version fixes CVE-2026-67354?
Is guzzlehttp/guzzle affected?
What is the CVSS score of CVE-2026-67354?
What CWE is associated with CVE-2026-67354?
How can I check Packagist dependencies for CVE-2026-67354?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-h95v-h523-3mw8",
"modified" : "2026-08-04T12:53:53Z",
"published" : "2026-07-20T23:28:36Z",
"aliases" : [ "CVE-2026-67354" ],
"summary" : "Guzzle: URI fragments disclosed in redirect Referer headers",
"details" : "### Impact\n\nWhen the optional `referer` redirect setting is enabled, affected versions of `RedirectMiddleware` can copy the fragment from the referring request URI into a generated `Referer` header. A URI fragment is the part after `#`. It is handled locally by the client and is not part of the HTTP request target, so the server handling the original request does not receive it. A generated `Referer` tells the redirect destination which URI led to the request. Guzzle correctly removes user information from that value, but retains the fragment when it follows a redirect to the same scheme, such as HTTPS to HTTPS. For example, an initial URI ending in `#secret` is sent without the fragment, but the redirect destination can receive a `Referer` ending in `#secret`. This behavior affects both the cURL and stream handlers.\n\nAn attacker who controls the redirect destination can read the fragment from the incoming header, including through request logs or application code. If the fragment contains a one-time login secret, access token, state value, or other private client data, it is disclosed to a server that was never meant to receive it. Exploitation requires the application to enable `allow_redirects.referer`, make a request to a URI with a sensitive fragment, and follow a same-scheme redirect to a less-trusted destination.\n\nThe `referer` setting is disabled by default. Applications that leave it disabled, do not put sensitive data in URI fragments, do not follow redirects, or only redirect within the same trust boundary are not affected. Guzzle already omits the generated header when the scheme changes. This issue is limited to the fragment's inclusion. Reducing the path and query on cross-origin redirects is a separate privacy policy question.\n\n### Patches\n\nThe issue is patched in `7.15.1` and later. Starting in that release, Guzzle removes both user information and the fragment before generating a redirect `Referer` value. Other redirect behavior does not change. Guzzle retains the referring path and query, and continues to omit the header when the scheme changes. Versions before `7.15.1` are affected when the optional `referer` setting is enabled.\n\n### Workarounds\n\nIf you cannot upgrade immediately, leave automatic Referer generation disabled. It is off by default. If redirect options are configured explicitly, ensure that `referer` is `false`:\n\n```php\n$client->request('GET', $uri, [\n 'allow_redirects' => ['referer' => false],\n]);\n```\n\nAlternatively, disable automatic redirects and follow trusted destinations manually, or remove the fragment from the request URI before sending a request that may redirect. Do not rely on the fact that fragments are absent from the initial HTTP request target, because the affected middleware can reintroduce them in the generated header.\n\n### References\n\n* https://www.rfc-editor.org/rfc/rfc9110.html#section-10.1.3\n* https://www.rfc-editor.org/rfc/rfc3986.html#section-3.5\n* https://www.rfc-editor.org/rfc/rfc9700.html#section-4.2.3",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "guzzlehttp/guzzle"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "7.15.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/guzzle/guzzle/security/advisories/GHSA-h95v-h523-3mw8"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-67354"
}, {
"type" : "WEB",
"url" : "https://github.com/guzzle/guzzle/pull/3901"
}, {
"type" : "WEB",
"url" : "https://github.com/guzzle/guzzle/commit/7b68220d6543f6f80fe62e633361fc9d4ead14d4"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/guzzle/guzzle"
}, {
"type" : "WEB",
"url" : "https://github.com/guzzle/guzzle/releases/tag/7.15.1"
}, {
"type" : "WEB",
"url" : "https://www.vulncheck.com/advisories/guzzlehttp-guzzle-before-uri-fragment-disclosure-via-referer"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-201", "CWE-212" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-20T23:28:36Z",
"nvd_published_at" : null
}
}