CVE-2026-49214

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 or cache poisoning, depending on how downstream components parse the request. The issue is patched in 2.10.2 and later. 1.x is end-of-life and will not receive a patch. As a workaround, validate and reject all untrusted URI strings before constructing PSR-7 Uri or Request instances. Reject input containing ASCII control characters, whitespace, or DEL, including CRLF, tab, space, NUL, or DEL characters. Applications that forward requests should also ensure the final HTTP client or serializer rejects invalid URI and header data before writing requests to the network.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
8.7%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
Patch available. Sources: github.
github Patch Available

CRLF Injection via URI Host Component in guzzlehttp/psr7 · Advisory · guzzle/psr7 · GitHub

https://github.com/guzzle/psr7/security/advisories/GHSA-hq7v-mx3g-29hw

Vendor Advisories for CVE-2026-49214(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
guzzlehttp/psr71.0.0 ... 2.9.1 (55 versions)2.10.2

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 03:15 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 14:12 UTCEG score recompute
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 14:32 UTCEG score recompute
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 14:50 UTCEG score recompute
  9. 2026-07-02 13:34 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 13:23 UTCEG score recompute
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 13:40 UTCEG score recompute
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 11:19 UTCEG score recompute
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 11:39 UTCEG score recompute
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 11:58 UTCEG score recompute
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-26 12:11 UTCEG score recompute
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 10:28 UTCEG score recompute
Show 34 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-24 10:47 UTCEG score recompute
  3. 2026-06-23 21:33 UTCEPSS rescore
  4. 2026-06-23 21:33 UTCEPSS rescore
  5. 2026-06-23 10:54 UTCEG score recompute
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-22 14:25 UTCEPSS rescore
  8. 2026-06-22 11:12 UTCEG score recompute
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 10:13 UTCEG score recompute
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-20 10:31 UTCEG score recompute
  15. 2026-06-19 19:26 UTCEPSS rescore
  16. 2026-06-19 19:26 UTCEPSS rescore
  17. 2026-06-19 10:44 UTCEG score recompute
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-18 11:03 UTCEG score recompute
  21. 2026-06-17 17:53 UTCEPSS rescore
  22. 2026-06-17 11:18 UTCEG score recompute
  23. 2026-06-16 17:53 UTCEPSS rescore
  24. 2026-06-16 11:38 UTCEG score recompute
  25. 2026-06-15 17:49 UTCEPSS rescore
  26. 2026-06-15 17:49 UTCEPSS rescore
  27. 2026-06-15 11:57 UTCEG score recompute
  28. 2026-06-14 23:18 UTCEPSS rescore
  29. 2026-06-14 12:12 UTCEG score recompute
  30. 2026-06-13 12:31 UTCEG score recompute
  31. 2026-06-12 23:12 UTCEPSS rescore
  32. 2026-06-12 23:12 UTCEPSS rescore
  33. 2026-06-12 12:50 UTCEG score recompute
  34. 2026-06-11 13:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49214?
CVE-2026-49214 is a medium vulnerability published on June 11, 2026. 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…
When was CVE-2026-49214 disclosed?
CVE-2026-49214 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49214 actively exploited?
CVE-2026-49214 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49214?
CVE-2026-49214 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-49214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49214, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49214

Explore →

Is Your Infrastructure Affected by CVE-2026-49214?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.