GHSA-g6pc-6676-c23j is a critical-severity (CVSS 9.1) CWE-123 vulnerability in remotion. A fix is available for remotion — see the affected versions and patch details below.
Remotion: arbitrary file write vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-g6pc-6676-c23j.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-g6pc-6676-c23j by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
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.
remotionnpmDescription
remotion-dev remotion v4.0.409 was discovered to contain an arbitrary file write vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | remotion | all versions | 4.0.410npm install remotion@4.0.410 |
Affected Products
remotionremotionDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for remotion, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update remotion to 4.0.410 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g6pc-6676-c23j is resolved across your whole dependency graph.
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.
Frequently Asked Questions
Is GHSA-g6pc-6676-c23j in your dependencies?
Find it across npm, including transitive dependencies.