Synced 16 Jun 2026 15:24 UTC Account
← Guzzle

Guzzle vulnerabilities: known CVEs & security history

Guzzle · Library / PHP · 5 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Guzzle release lines — 5 in total. A CVE here doesn't mean your version is affected — check Guzzle's current status and the safe version to run.

5
known CVEs
0
actively exploited (KEV)
0
critical severity
0
ransomware-linked

Known Guzzle CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2022-29248 high 8 1% 2022
CVE-2022-31091 high 7.7 1% 2022
CVE-2022-31090 high 7.7 1% 2022
CVE-2022-31043 high 7.5 2% 2022
CVE-2022-31042 high 7.5 2% 2022

Is my Guzzle version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Guzzle version → · Monitor Guzzle for new CVEs →

Guzzle vulnerabilities — frequently asked

How many known vulnerabilities does Guzzle have?

IsItPatched tracks 5 CVEs for Guzzle. 0 are critical-severity and 5 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Guzzle have any actively-exploited vulnerabilities?

None of Guzzle's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Guzzle vulnerability?

Among tracked issues, CVE-2022-29248 (HIGH, CVSS 8) ranks highest — a Information disclosure weakness.

Is Guzzle safe to use?

It depends on the version. The latest supported Guzzle release (7.11.1) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Guzzle security status · Guzzle end-of-life · actively-exploited CVEs. Always verify against Guzzle's advisories — see our disclaimer.