How severe is CVE-2022-24775?

CVE-2022-24775 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-24775?

CVE-2022-24775 affects the following packages: guzzlehttp/psr7 (Packagist), guzzlehttp/psr7 (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-24775?

Update guzzlehttp/psr7 to 1.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24775 is resolved across your whole dependency graph.

How do I detect CVE-2022-24775 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for guzzlehttp/psr7, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-24775 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-24775 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-24775 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-24775?

CVE-2022-24775 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-24775?

CVE-2022-24775 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-24775 published, and has it been updated?

CVE-2022-24775 was published on March 21, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2022-24775 — psr7

HIGHFix: guzzle/psr7#485

CVE-2022-24775 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in guzzlehttp/psr7. A fix is available for guzzlehttp/psr7 — see the affected versions and patch details below.

Improper Input Validation in guzzlehttp/psr7

Also known asBIT-drupal-2022-24775DRUPAL-CORE-2022-006GHSA-q7rv-6hp3-vh96

Published

Mar 21, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-24775.

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘guzzlehttp/psr7🐘guzzlehttp/psr7

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Improper header parsing. An attacker could sneak in a carriage return character (\r) and pass untrusted values in both the header names and values.

Patches

The issue is patched in 1.8.4 and 2.1.1.

Workarounds

There are no known workarounds.

References

https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`guzzlehttp/psr7`	all versions	1.8.4`composer require guzzlehttp/psr7:^1.8.4`
🐘Packagist	`guzzlehttp/psr7`	≥ 2.0.0&&< 2.1.1	2.1.1`composer require guzzlehttp/psr7:^2.1.1`

Affected Products

2 products · 4 configurations

Application

drupaldrupal

≥ 9.3.0 && < 9.3.9

range

Application

psr-7guzzlephp

≥ 2.0.0 && < 2.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for guzzlehttp/psr7, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update guzzlehttp/psr7 to 1.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24775 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Improper header parsing. An attacker could sneak in a carriage return character (`\r`) and pass untrusted values in both the header names and values. ### Patches The issue is patched in 1.8.4 and 2.1.1. ### Workarounds There are no known workarounds. ### References * https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4