CVE-2026-30121
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 an arbitrary file write 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 confidenceThe remotion-dev component in remotion v4.0.409 contains an arbitrary file write vulnerability that allows an attacker to write files to arbitrary locations on the filesystem. This could potentially lead to remote code execution if the attacker can overwrite critical system files, configuration files, or executable code.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 is installed in your projectExamine your package.json file for 'remotion' in the dependencies or devDependencies section, or run 'npm list remotion' to list the installed packageAffected if Remotion package is present in your project dependencies
-
Determine the installed Remotion versionRun 'npm list remotion' or check the version field in node_modules/remotion/package.jsonAffected if The installed version is exactly 4.0.409
-
Identify if the remotion-dev component is in useCheck your package.json scripts for any 'remotion dev' commands, or look for remotion-dev in node_modules. Also check if your application starts a Remotion development serverAffected if The remotion-dev development server component is being invoked or used
-
Verify file write access configurationReview your Remotion project configuration and any custom file handling code for unrestricted file write operations, particularly where user-controlled paths are usedAffected if The configuration allows arbitrary file path specification without validation or restriction
-
Check network exposure of the development serverDetermine if the remotion-dev server is exposed to network access by checking startup logs, configuration, or running 'netstat' or 'ss' to see binding addressesAffected if The remotion-dev server is accessible from network addresses rather than localhost only
You are affected only if Remotion is installed, the version is exactly 4.0.409, and the remotion-dev component is actively being used in your environment
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 to a patched version of remotion if available, or implement strict input validation and path sanitization on file write operations to restrict writing to safe, intended directories only.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30121 — 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-30121 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