NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2020-28435 — ffmpeg-sdk

CRITICAL

CVE-2020-28435 is a critical-severity (CVSS 9.8) CWE-77 vulnerability in ffmpeg-sdk. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

ffmpeg-sdk vulnerable to OS Command Injection

Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
1 known
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk+0.08%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.01%0.63%1.25%1.87%0.5%1.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
ffmpeg-sdknpm
9downloads / week

Description

A command injection vulnerability affects all versions of package ffmpeg-sdk. The injection point is located in line 9 in index.js.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmffmpeg-sdkall versionsNo fix

Affected Products

1 product · 1 configurations
Application
ffmpeg-sdkffmpeg-sdk_project
all
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.

This affects all versions of package ffmpeg-sdk. The injection point is …

security.snyk.ioNVDJul 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ffmpeg-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of ffmpeg-sdk for CVE-2020-28435. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

A command injection vulnerability affects all versions of package ffmpeg-sdk. The injection point is located in line 9 in index.js.
O3 Security · Impact-Aware SCA

Is CVE-2020-28435 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-28435: ffmpeg-sdk (Critical 9.8)