constructEvent does not verify headerGHSA-4g53-vp7q-gfjv
GHSA-4g53-vp7q-gfjv is a security vulnerability in @worker-tools/stripe-webhook. A fix is available for @worker-tools/stripe-webhook — see the affected versions and patch details below.
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.
@worker-tools/stripe-webhooknpmDescription
Impact
Anyone verifying a Stripe webhook request via this library's constructEvent function.
Patches
Upgrade to 1.1.4.
Workarounds
Use await verifyHeader(...) directly instead of constructEvent.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @worker-tools/stripe-webhook | all versions | 1.1.4npm install @worker-tools/stripe-webhook@1.1.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @worker-tools/stripe-webhook, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @worker-tools/stripe-webhook to 1.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4g53-vp7q-gfjv 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-4g53-vp7q-gfjv in your dependencies?
Find it across npm, including transitive dependencies.