NPM · JULY 2026 · EARLY WARNING

AVideo < 29.0: Critical CVE Under Investigation - Command Injection Risk

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
CVE-2026-45578CVE-2026-64625Severity: CRITICAL

AVideo versions prior to 29.0 are under investigation for a critical vulnerability (CVE-2026-64625) that may allow command injection through the Live plugin.

What happened

AVideo before 29.0 is reportedly affected by a critical vulnerability (CVE-2026-64625) with a CVSS score of 9.8. The issue appears to stem from an incomplete fix for CVE-2026-45578, where the execAsync() function re-wraps escaped commands, enabling command substitution. This could allow attackers to inject arbitrary OS commands via the on_publish.php endpoint in the Live plugin, despite escapeshellarg() protection.

Professional software engineers using AVideo should assess their exposure by checking if they are running a version prior to 29.0. It is recommended to upgrade to AVideo version 29.0 or later to mitigate the risk of command injection.

The primary sources indicate that this is an early warning and the details are under investigation. For the most accurate and up-to-date information, consult the NVD page for CVE-2026-64625.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If avideo is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats