Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-4g53-vp7q-gfjv

GHSA-4g53-vp7q-gfjv is a security vulnerability in @worker-tools/stripe-webhook. O3 Security confirms whether GHSA-4g53-vp7q-gfjv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

constructEvent does not verify header

Published
May 28, 2021
Updated
May 27, 2021
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of May 27, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦@worker-tools/stripe-webhook

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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

https://github.com/worker-tools/stripe-webhook/issues/1

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@worker-tools/stripe-webhookall versions1.1.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @worker-tools/stripe-webhook. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-4g53-vp7q-gfjv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4g53-vp7q-gfjv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 https://github.com/worker-tools/stripe-webhook/issues/1
O3 Security · Impact-Aware SCA

Is GHSA-4g53-vp7q-gfjv in your dependencies?

O3 detects GHSA-4g53-vp7q-gfjv across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-4g53-vp7q-gfjv: constructEvent does… | O3 Security