Proxy credential disclosure via origin-bound header routing
Published Aug 1, 2026 · Updated Aug 1, 2026
Credential disclosure in Guzzle before 7.14.2 allows remote attackers to obtain proxy credentials via crafted request destinations. The cURL handlers place first-class Proxy-Authorization values in CURLOPT_HTTPHEADER and migrate them only when Guzzle predicts an HTTP proxy. Exposure requires an application-configured first-class proxy credential and a direct, bypassed, SOCKS, or cross-origin redirected route; an attacker-controlled origin can log and reuse the credential.
Summary
What happened
Credential disclosure in Guzzle before 7.14.2 allows remote attackers to obtain proxy credentials via crafted request destinations. The cURL handlers place first-class Proxy-Authorization values in CURLOPT_HTTPHEADER and migrate them only when Guzzle predicts an HTTP proxy. Exposure requires an application-configured first-class proxy credential and a direct, bypassed, SOCKS, or cross-origin redirected route; an attacker-controlled origin can log and reuse the credential.
The record
- CVE
- CVE-2026-67339
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- Guzzle
- Product
- Guzzle
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <7.14.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo