Denial of Service vulnerability in @podium/layout and @podium/proxyGHSA-3hjg-vc7r-rcrw
HIGHFix: podium-lib/layout@fe43e65GHSA-3hjg-vc7r-rcrw is a high-severity (CVSS 7.5) CWE-248 vulnerability in @podium/layout. A fix is available for @podium/layout — see the affected versions and patch details below.
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 GHSA-3hjg-vc7r-rcrw.
EPSS Exploitation Probability
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
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@podium/layoutnpm@podium/proxynpmDescription
Impact
An attacker using the Trailer header as part of the request against proxy endpoints has the ability to take down the server.
All Podium layouts that include podlets with proxy endpoints are affected.
Patches
@podium/layout which is the main way developers/users are vulnerable to this exploit, has been patched in version 4.6.110. All earlier versions are vulnerable.
@podium/proxy which is the source of the vulnerability and is used by @podium/layout has been patched in version 4.2.74. All earlier versions are vulnerable.
Workarounds
It is not easily possible to work around this issue without upgrading. We recommend upgrading @podium/layout and/or @podium/proxy as soon as possible.
For more information
If you have any questions or comments about this advisory:
- Open an issue in podium-lib/issues
Credits
The vulnerability was reported by krynos from Ercoli Consulting via FINN.no's private bug bounty program
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @podium/layout | all versions | 4.6.110npm install @podium/layout@4.6.110 |
| 📦npm | @podium/proxy | all versions | 4.2.74npm install @podium/proxy@4.2.74 |
Affected Products
podium layoutfinnpodium proxyfinnDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @podium/layout, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @podium/layout to 4.6.110 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3hjg-vc7r-rcrw 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-3hjg-vc7r-rcrw in your dependencies?
Find it across npm, including transitive dependencies.