Skip to content

Bump docs/remotion deps to clear OSV CVEs (fast-uri, ws) #10

Description

@soydachi

Problem

OSV-Scanner flags 3 vulnerabilities in docs/remotion/package-lock.json (transitive deps). The Security workflow fails on main because of them (google/osv-scanner-action, --exit-code 1).

CVE Severity Package Installed Fixed in
CVE-2026-6322 (GHSA-v39h-62p7-jpjc) High fast-uri 3.1.0 ≥ 3.1.2
CVE-2026-6321 (GHSA-q3j6-qgpj-74h6) High fast-uri 3.1.0 ≥ 3.1.1
CVE-2026-45736 (GHSA-58qx-3vcg-4xpx) Medium ws 8.17.1 ≥ 8.20.1
  • fast-uri < 3.1.2 — percent-encoded authority/path-segment decoding enables URI authority confusion and path-normalization allowlist bypass.
  • ws < 8.20.1 — uninitialized memory disclosure when a TypedArray is passed as the close() reason.

All three are pulled in transitively by remotion under docs/remotion/; the app's own runtime deps are unaffected (zero-dependency core).

Fix

Update docs/remotion/ so the lockfile resolves fast-uri ≥ 3.1.2 and ws ≥ 8.20.1. Likely covered by the open Dependabot remotion bumps (e.g. remotion 4.0.468); otherwise add explicit overrides in docs/remotion/package.json and regenerate the lockfile.

Acceptance

  • docs/remotion/package-lock.json resolves fast-uri ≥ 3.1.2 and ws ≥ 8.20.1
  • OSV-Scanner reports 0 findings → Security workflow green on main

Filed via /ai-issue. CVE data from the repo code-scanning alerts (OSV-Scanner).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesDependency updatessecuritySecurity vulnerability or hardening

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions