Improper header validation in httpsoft/http-messageGHSA-9jxr-mwpp-w643
MEDIUMGHSA-9jxr-mwpp-w643 is a medium-severity (CVSS 5.3) vulnerability in httpsoft/http-message. A fix is available for httpsoft/http-message — see the affected versions and patch details below.
Real-World Exposure
httpsoft/http-messageReal-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 newline (\n) into both the header names and values. While the specification states that \r\n\r\n is used to terminate the header list, many servers in the wild will also accept \n\n.
Patches
The issue is patched in 1.0.12.
Workarounds
There are no known workarounds.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | httpsoft/http-message | all versions | 1.0.12composer require httpsoft/http-message:^1.0.12 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for httpsoft/http-message, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update httpsoft/http-message to 1.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jxr-mwpp-w643 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
Is GHSA-9jxr-mwpp-w643 in your dependencies?
Find it across Packagist, including transitive dependencies.