Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-69246— Guzzle: Noncanonical host can bypass host-based checks

Quick assessment

Affected
guzzle guzzle
Exploitation
Public or AI PoC available; prioritize validation
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

guzzle是guzzle组织的一款HTTP客户端Web组件。 Guzzle 7.15.2之前版本和8.0.1之前版本存在安全漏洞,该漏洞源于处理请求URI与Host头时存在解析差异,可能导致攻击者绕过主机访问限制,访问应用程序检查排除的主机并读取其响应信息。

CVSS 7.2 · High EPSS 0.37% · P28

Possible ATT&CK Techniques 1 AI

T1557 · Adversary-in-the-Middle

Affected Version Matrix 2

VendorProduct Version RangeStatus
guzzle guzzle >= 8.0.0, < 8.0.1 affected
< 7.15.2 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-69246

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Guzzle: Noncanonical host can bypass host-based checks
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
不正确的行为次序:规范化之前验证
Source: CVE Program / CVE List V5
Vulnerability Title
Guzzle 处理逻辑错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
guzzle是guzzle组织的一款HTTP客户端Web组件。 Guzzle 7.15.2之前版本和8.0.1之前版本存在安全漏洞,该漏洞源于处理请求URI与Host头时存在解析差异,可能导致攻击者绕过主机访问限制,访问应用程序检查排除的主机并读取其响应信息。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
guzzle guzzle >= 8.0.0, < 8.0.1 -

II. Public POCs for CVE-2026-69246

# POC Description Source Link Shenlong Link
AI-Generated POC Premium
Qwen3.6-35B-A3B · 9306 chars
Pro+ exclusive includes:
Vulnerability reproduction recording (real sandbox build + trigger, exclusive)
In-depth vulnerability mechanism
Trigger conditions & impact
Full executable POC code
Exploit chain & mitigation
POC zip download
100+ AI POC generations per month

III. Intelligence Information for CVE-2026-69246

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-69246 (2)

Vendor Advisories for CVE-2026-69246 (1)

Vendor Pages for CVE-2026-69246 (1)

Other References for CVE-2026-69246 (1)

IV. Related Vulnerabilities

V. Comments for CVE-2026-69246

No comments yet


Leave a comment