How severe is GHSA-8v5x-6vv5-jv4g?

No CVSS score has been assigned to GHSA-8v5x-6vv5-jv4g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8v5x-6vv5-jv4g?

GHSA-8v5x-6vv5-jv4g affects the following packages: amphp/http (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-8v5x-6vv5-jv4g?

Update amphp/http to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8v5x-6vv5-jv4g is resolved across your whole dependency graph.

How do I detect GHSA-8v5x-6vv5-jv4g in my Packagist dependencies?

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

How do I mitigate GHSA-8v5x-6vv5-jv4g 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 GHSA-8v5x-6vv5-jv4g actively exploited in the wild?

No public exploit code has been indexed for GHSA-8v5x-6vv5-jv4g 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.

When was GHSA-8v5x-6vv5-jv4g published, and has it been updated?

GHSA-8v5x-6vv5-jv4g was published on May 15, 2024 and was last updated on November 29, 2024. 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

amphp/http Host Header Injection vulnerabilityGHSA-8v5x-6vv5-jv4g

Fix: amphp/http#4

GHSA-8v5x-6vv5-jv4g is a security vulnerability in amphp/http. A fix is available for amphp/http — see the affected versions and patch details below.

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘amphp/http

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

amphp/http versions before 1.0.1 allows an attacker to supply invalid input in the Host header which may lead to various type of Host header injection attacks.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`amphp/http`	all versions	1.0.1`composer require amphp/http:^1.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for amphp/http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update amphp/http to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8v5x-6vv5-jv4g 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

amphp/http versions before 1.0.1 allows an attacker to supply invalid input in the Host header which may lead to various type of Host header injection attacks.

O3 Security · Impact-Aware SCA

Is GHSA-8v5x-6vv5-jv4g in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works