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

GHSA-5pxj-mhwj-x5gv

CRITICALFix: victornpb/asciitable.js#1

GHSA-5pxj-mhwj-x5gv is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in asciitable.js. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-5pxj-mhwj-x5gv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in asciitable.js

Also known asCVE-2020-7771
Published
Apr 13, 2021
Updated
Mar 16, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Mar 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦asciitable.js

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

The package asciitable.js before 1.0.3 is vulnerable to Prototype Pollution via the main function.

PoC

var a = require("asciitable.js"); 
var b = JSON.parse('{"__proto__":{"test":123}}'); 
a({},b); 
console.log({}.test)

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmasciitable.jsall versions1.0.3
Exploits & PoCs
1

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 asciitable.js. 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 asciitable.js to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5pxj-mhwj-x5gv 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-5pxj-mhwj-x5gv 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-5pxj-mhwj-x5gv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package asciitable.js before 1.0.3 is vulnerable to Prototype Pollution via the main function. ### PoC ```js var a = require("asciitable.js"); var b = JSON.parse('{"__proto__":{"test":123}}'); a({},b); console.log({}.test) ```
O3 Security · Impact-Aware SCA

Is GHSA-5pxj-mhwj-x5gv in your dependencies?

O3 detects GHSA-5pxj-mhwj-x5gv across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.