CVE intelligence and bounded remediation
CVE-2026-49214 — guzzlehttp/psr7 is a PSR-7 HTTP message library implementation in PHP
guzzlehttp/psr7 is a PSR-7 HTTP message library implementation in PHP. Versions prior to 2.10.2 did not reject ASCII control characters, whitespace, or DEL in first-party URI host components. A vulnerable flow is: First, an application accepts a user-controlled URL. Second, the URL is used to construct a PSR-7 `Uri` or `Request`. Third, the host component contains CRLF or another header-unsafe character. Fourth, the host is copied into the PSR-7 `Host` header when no explicit `Host` header is provided. Finally, the request is serialized or sent by an HTTP client that does not independently reject the malformed host. In that flow, an attacker can cause the serialized request to contain additional attacker-controlled header lines. For example, a host containing `"\r\nX-Injected: yes"` can cause the generated `Host` header to span multiple HTTP header lines. Applications are affected when they use user-controlled URLs for outbound HTTP requests, URL forwarding, proxying, crawling, webhook delivery, or similar request-dispatch flows. In deployments involving HTTP/1.1 connection reuse, proxies, gateways, or load balancers, this malformed request may also contribute to request smuggling…
- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Published
- 2026-06-11
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-20, CWE-93, CWE-113
Affected products
- guzzlephp / psr-7
Matched remediation archetype
HTTP request smuggling and message-boundary ambiguity
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory every proxy, CDN, gateway, load balancer, service mesh, and application server hop on affected request paths.
- Compare documented parsing and normalization behavior for message length, transfer coding, duplicate headers, and protocol translation.
- Identify connection reuse and which downstream services trust headers added by intermediaries.
Remediate safely
- Update affected intermediaries and origin servers and align them on a single standards-compliant request framing policy.
- Reject ambiguous length, transfer-coding, duplicate, malformed, and unsupported framing before forwarding.
- Normalize or remove hop-by-hop and identity headers at one controlled boundary and add multi-hop regression tests.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.