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

CVE-2020-7628

CRITICAL

CVE-2020-7628 is a critical-severity (CVSS 9.8) remote code execution vulnerability in umount. O3 Security confirms whether CVE-2020-7628 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Command Injection in umount

Published
Jun 10, 2020
Updated
Mar 13, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Mar 13, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦umount

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

All versions of umount are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an exec call on the umount function . This may allow attackers to execute arbitrary code in the system if the device value passed to the function is user-controlled.

Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmumountall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for umount. 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 umount has shipped for CVE-2020-7628 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 CVE-2020-7628 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 CVE-2020-7628. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

All versions of `umount ` are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `umount` function . This may allow attackers to execute arbitrary code in the system if the `device` value passed to the function is user-controlled. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.
O3 Security · Impact-Aware SCA

Is CVE-2020-7628 in your dependencies?

O3 detects CVE-2020-7628 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2020-7628: Command Injection in… | O3 Security