CVE-2026-55568: Guzzle is an extensible PHP HTTP client

Q: How do I fix CVE-2026-55568?

guzzle: upgrade to 7.12.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-55568 being exploited?

CVE-2026-55568 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-55568 affect?

CVE-2026-55568 affects guzzle. Severity is medium (CVSS 5.9). Guzzle is an extensible PHP HTTP client. Prior to 7.12.1, in certain configurations, traffic expected to be protected by TLS on the hop to the proxy is transmitted in cleartext. Proxy authentication credentials (the Proxy-Authorization head

Q: How urgent is CVE-2026-55568?

Priority 27/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2026-55568 is a medium-severity flaw (CVSS 5.9) affecting guzzle. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Guzzle is an extensible PHP HTTP client. Prior to 7.12.1, in certain configurations, traffic expected to be protected by TLS on the hop to the proxy is transmitted in cleartext. Proxy authentication credentials (the Proxy-Authorization header, proxy userinfo in the proxy URL, or CURLOPT_PROXYUSERPWD) are sent without encryption, and the CONNECT target host and port for tunneled HTTPS requests are exposed. The built-in cURL handlers (GuzzleHttp\Ha

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.1% (top 96%)
CISA exploited list	No
Weakness	CWE-311, CWE-319, CWE-636
Published	2026-06-23
Last modified	2026-06-26

Publisher (CNA): GitHub, Inc. · Vendor: guzzlephp

Last updated 2026-06-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-23 16:17 UTCPublished CVE record published
2026-06-26 19:34 UTCUpdated Record last modified

guzzlephp guzzle UPGRADE

Affected: < 7.12.1

Fixed in: 7.12.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy guzzle || rpm -q guzzle || guzzle --version

2. UPGRADE to 7.12.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade guzzle

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade guzzle

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-55568?

guzzle: upgrade to 7.12.1. Exact commands for each OS are on this page.

Is CVE-2026-55568 being exploited?

CVE-2026-55568 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-55568 affect?

CVE-2026-55568 affects guzzle. Severity is medium (CVSS 5.9). Guzzle is an extensible PHP HTTP client. Prior to 7.12.1, in certain configurations, traffic expected to be protected by TLS on the hop to the proxy is transmitted in cleartext. Proxy authentication credentials (the Proxy-Authorization head

How urgent is CVE-2026-55568?

Priority 27/100. Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities · curl vulnerabilities

Related CVEs

CVE-2026-55767 MEDIUM 5.8 UPGRADE Guzzle is an extensible PHP HTTP client
CVE-2026-59883 MEDIUM 4.7 UPGRADE Guzzle is an extensible PHP HTTP client

References

← Back to latest CVEs