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

GHSA-3fw4-4h3m-892h

CRITICAL

GHSA-3fw4-4h3m-892h is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in serial-number. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-3fw4-4h3m-892h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OS Command Injection in serial-number

Also known asCVE-2019-10804SNYK-JS-SERIALNUMBER-559010
Published
Apr 13, 2021
Updated
Jul 8, 2026
Affected
1 pkg
Patched
None yet
Exploits
1 known
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦serial-number

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

serial-number through 1.3.0 allows execution of arbritary commands. The "cmdPrefix" argument in serialNumber function is used by the "exec" function without any validation.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmserial-numberall versionsNo fix
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 serial-number. 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. Remediation status

    No patched version of serial-number has shipped for GHSA-3fw4-4h3m-892h yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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-3fw4-4h3m-892h 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-3fw4-4h3m-892h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

serial-number through 1.3.0 allows execution of arbritary commands. The "cmdPrefix" argument in serialNumber function is used by the "exec" function without any validation.
O3 Security · Impact-Aware SCA

Is GHSA-3fw4-4h3m-892h in your dependencies?

O3 detects GHSA-3fw4-4h3m-892h across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.