CVE-2026-30120
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedremotion-dev remotion v4.0.409 was discovered to contain a remote code execution (RCE) vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceremotion-dev v4.0.409 contains a remote code execution (RCE) vulnerability. The vulnerability allows attackers to execute arbitrary code remotely, likely through improper input handling or insufficient validation in the remotion-dev server component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.0.409CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if remotion-dev is installedRun 'npm list remotion-dev' or 'yarn list remotion-dev' in your project directory to list installed packages, or check your package.json for remotion-dev in dependenciesAffected if remotion-dev appears in your installed packages
-
Verify the installed version of remotion-devCompare the installed version number (from npm list or package-lock.json) against the affected version: 4.0.409Affected if The installed version is exactly 4.0.409
-
Determine if the remotion-dev server is runningCheck for running processes that start remotion-dev server (often via 'npx remotion dev' or similar commands), or check for port 3000 (default) being used by remotionAffected if The remotion-dev server process is actively running
-
Check if the server is network accessibleReview your firewall rules, container networking config, or cloud security groups to see if the remotion-dev server port is exposed to the network or internetAffected if The remotion-dev server port is reachable from untrusted network sources
You are affected only if remotion-dev version 4.0.409 is installed AND the remotion-dev server component is running and accessible, since the RCE requires the vulnerable server component to be active.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade remotion-dev to the latest version beyond v4.0.409 where the vulnerability is patched. If immediate patching is not possible, restrict network access to remotion-dev servers and disable any exposed remote execution features.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30120 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30120 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data