GHSA-f6p5-76fp-m248 — zendframework/zend-diacto…
GHSA-f6p5-76fp-m248 is a security vulnerability in zendframework/zend-diactoros. A fix is available for zendframework/zend-diactoros — see the affected versions and patch details below.
URL Rewrite vulnerability in multiple zendframework components
Real-World Exposure
zendframework/zend-diactoros🐘zendframework/zend-feed🐘zendframework/zend-httpReal-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
zend-diactoros (and, by extension, Expressive), zend-http (and, by extension, Zend Framework MVC projects), and zend-feed (specifically, its PubSubHubbub sub-component) each contain a potential URL rewrite exploit. In each case, marshaling a request URI includes logic that introspects HTTP request headers that are specific to a given server-side URL rewrite mechanism.
When these headers are present on systems not running the specific URL rewriting mechanism, the logic would still trigger, allowing a malicious client or proxy to emulate the headers to request arbitrary content.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | zendframework/zend-diactoros | all versions | 1.8.4composer require zendframework/zend-diactoros:^1.8.4 |
| 🐘Packagist | zendframework/zend-feed | all versions | 2.10.3composer require zendframework/zend-feed:^2.10.3 |
| 🐘Packagist | zendframework/zend-http | all versions | 2.8.1composer require zendframework/zend-http:^2.8.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zend-diactoros, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zendframework/zend-diactoros to 1.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f6p5-76fp-m248 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f6p5-76fp-m248 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-f6p5-76fp-m248. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f6p5-76fp-m248 in your dependencies?
O3 Security finds GHSA-f6p5-76fp-m248 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.