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

GHSA-29xr-v42j-r956

CRITICAL

thenify before 3.3.1 made use of unsafe calls to `eval`.

Also known asCVE-2020-7677
Published
Jul 18, 2022
Updated
May 5, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
2 known

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk73th percentile+0.55%
0.00%0.70%1.40%2.10%0.2%1.6%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected
org.webjars.npm:thenify📦thenify

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

Description

Versions of thenify prior to 3.3.1 made use of unsafe calls to eval. Untrusted user input could thus lead to arbitrary code execution on the host. The patch in version 3.3.1 removes calls to eval.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.webjars.npm:thenifyall versions3.3.1
📦npmthenifyall versions3.3.1
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:thenify. 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 org.webjars.npm:thenify to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-29xr-v42j-r956 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-29xr-v42j-r956 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-29xr-v42j-r956. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of thenify prior to 3.3.1 made use of unsafe calls to `eval`. Untrusted user input could thus lead to arbitrary code execution on the host. The patch in version 3.3.1 removes calls to `eval`.
O3 Security · Impact-Aware SCA

Is GHSA-29xr-v42j-r956 in your dependencies?

O3 detects GHSA-29xr-v42j-r956 across Maven, npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.