🛡️ CVE-2026-30121 — remotion

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: None — an unauthenticated stranger can try it.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: None.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-30121 is classified as CWE-123: Write-what-where Condition. Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.

Affected software

CVE-2026-30121 is recorded against 1 package.

• remotion

Timeline and source

Published on 15 June 2026 and last revised on 19 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Package)
github.com (Web)

Other advisories for this package

remotion has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2026-30120 (9.5 Critical, published 15 Jun 2026)

Same weakness in other software

These advisories are the same class of weakness (CWE-123: Write-what-where Condition) in other software:

• CVE-2026-20469 (6.0 Medium, published 3 Aug 2026)
• CVE-2026-47473 (7.4 High, published 14 Jul 2026)
• CVE-2026-45257 (7.8 High, published 26 Jun 2026)
• CVE-2026-43284 (8.8 High, published 8 May 2026)
• CVE-2026-41952 (7.8 High, published 29 Apr 2026)
• CVE-2025-14857 (published 7 Apr 2026)
• CVE-2025-69809 (9.8 Critical, published 16 Mar 2026)
• CVE-2025-29943 (published 16 Jan 2026)

Details

Affected Packages

References