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

GHSA-8h84-8j4f-p97q

MEDIUMFix: diegohaz/bodymen@5d52e8c

GHSA-8h84-8j4f-p97q is a medium-severity (CVSS 6.3) CWE-74 vulnerability in bodymen. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-8h84-8j4f-p97q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Injection in bodymen

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

Real-World Exposure

1 pkg affected

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.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
bodymennpm
4Kdownloads / week

Description

bodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a proto payload.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmbodymenall versions1.1.1
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 bodymen. 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 bodymen to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8h84-8j4f-p97q 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-8h84-8j4f-p97q 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-8h84-8j4f-p97q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

bodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
O3 Security · Impact-Aware SCA

Is GHSA-8h84-8j4f-p97q in your dependencies?

O3 detects GHSA-8h84-8j4f-p97q 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-8h84-8j4f-p97q: Injection in bodymen… | O3 Security