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

GHSA-f259-h6m8-hm8m

CRITICALFix: saeedseyfi/exec-local-bin@d425866

GHSA-f259-h6m8-hm8m is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in exec-local-bin. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-f259-h6m8-hm8m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

exec-local-bin vulnerable to Command Injection

Also known asCVE-2022-25923
Published
Jan 6, 2023
Updated
Apr 10, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Apr 10, 2025 · 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, a proxy for how much of the ecosystem is exposed.

exec-local-binnpm
24downloads / week

Description

Versions of the package exec-local-bin before 1.2.0 are vulnerable to Command Injection via the theProcess() functionality due to improper user-input sanitization.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmexec-local-binall versions1.2.0
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 exec-local-bin. 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 exec-local-bin to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f259-h6m8-hm8m 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-f259-h6m8-hm8m 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-f259-h6m8-hm8m. 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 the package exec-local-bin before 1.2.0 are vulnerable to Command Injection via the `theProcess()` functionality due to improper user-input sanitization.
O3 Security · Impact-Aware SCA

Is GHSA-f259-h6m8-hm8m in your dependencies?

O3 detects GHSA-f259-h6m8-hm8m 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-f259-h6m8-hm8m: exec-local-bin… | O3 Security