7.2
HIGH CVSS 3.1
CVE-2026-69246
Guzzle: Noncanonical host can bypass host-based checks
Description

Guzzle is an extensible PHP HTTP client. Prior to 7.15.2 and 8.0.1, Guzzle gives a transport the request URI as text and supplies the Host header separately. The cURL handlers set CURLOPT_URL to the URI exactly as written and push that Host into CURLOPT_HTTPHEADER; StreamHandler does the same through fopen(). libcurl then parses the authority itself, percent-decoding it and, on an IDN-capable build, applying IDNA mapping, and uses the result to resolve, connect, name the TLS peer and address a proxy CONNECT, while the supplied Host suppresses the aligned one libcurl would have generated. For a URI host written as 127.0.0.%31, filter_var() rejects the host as an IP literal, yet libcurl decodes it to 127.0.0.1 and reaches loopback with no DNS lookup while the server receives Host: 127.0.0.%31. An attacker who influences a fetched URI can therefore reach a host the application's checks excluded and read whatever the host exposes of the response. The same divergence moves Guzzle's own decisions onto a spelling the transport does not use: no_proxy selects proxy routing from the literal host, and RedirectMiddleware decides from it whether to strip Authorization and Cookie. Exploitation requires the application to build a request URI from untrusted input and to make a host decision before handing it to Guzzle. This issue is fixed in versions 7.15.2 and 8.0.1.

INFO

Published Date :

Aug. 3, 2026, 9:16 p.m.

Last Modified :

Aug. 3, 2026, 9:16 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-69246 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH [email protected]
Solution
Update Guzzle to 7.15.2 or 8.0.1 to fix URI parsing and host resolution issues.
  • Update Guzzle to version 7.15.2 or 8.0.1.
  • Validate and sanitize all user-supplied URI input.
  • Re-evaluate host validation logic within the application.
  • Ensure Host header matches the resolved URI.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-69246 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-69246 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-69246 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Aug. 03, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'guzzle', 'product': 'guzzle', 'versions': [{'status': 'affected', 'version': '>= 8.0.0, < 8.0.1'}, {'status': 'affected', 'version': '< 7.15.2'}]}]
    Added Description Guzzle is an extensible PHP HTTP client. Prior to 7.15.2 and 8.0.1, Guzzle gives a transport the request URI as text and supplies the Host header separately. The cURL handlers set CURLOPT_URL to the URI exactly as written and push that Host into CURLOPT_HTTPHEADER; StreamHandler does the same through fopen(). libcurl then parses the authority itself, percent-decoding it and, on an IDN-capable build, applying IDNA mapping, and uses the result to resolve, connect, name the TLS peer and address a proxy CONNECT, while the supplied Host suppresses the aligned one libcurl would have generated. For a URI host written as 127.0.0.%31, filter_var() rejects the host as an IP literal, yet libcurl decodes it to 127.0.0.1 and reaches loopback with no DNS lookup while the server receives Host: 127.0.0.%31. An attacker who influences a fetched URI can therefore reach a host the application's checks excluded and read whatever the host exposes of the response. The same divergence moves Guzzle's own decisions onto a spelling the transport does not use: no_proxy selects proxy routing from the literal host, and RedirectMiddleware decides from it whether to strip Authorization and Cookie. Exploitation requires the application to build a request URI from untrusted input and to make a host decision before handing it to Guzzle. This issue is fixed in versions 7.15.2 and 8.0.1.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
    Added CWE CWE-918
    Added CWE CWE-436
    Added CWE CWE-180
    Added CWE CWE-941
    Added Reference https://github.com/guzzle/guzzle/commit/3aeea0406aab88cbbd86531313d7cebf8ae149a4
    Added Reference https://github.com/guzzle/guzzle/commit/744101956d78b7c1384d0cbf379db13e859167bf
    Added Reference https://github.com/guzzle/guzzle/pull/3907
    Added Reference https://github.com/guzzle/guzzle/pull/3908
    Added Reference https://github.com/guzzle/guzzle/releases/tag/7.15.2
    Added Reference https://github.com/guzzle/guzzle/releases/tag/8.0.1
    Added Reference https://github.com/guzzle/guzzle/security/advisories/GHSA-v5mv-p594-2x33
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.