Blinko EUVD-2026-97145

Requires an authenticated session able to invoke the plugin.installPlugin tRPC procedure, which is open to any authenticated user; the description notes self-registration may be enabled, potentially granting that access to otherwise unauthorized attackers. The RCE-as-root outcome specifically depends on running the official Docker image, which executes as root, allowing overwrite of a root-owned startup file - a non-root or hardened container deployment would limit impact to file overwrite within the process's privileges rather than root code execution. Affects Blinko through version 1.8.8. Limiting factors: valid (or self-registered) account required, and the full root-RCE severity is contingent on the default root Docker configuration.

This is a genuine high-priority issue, not a CVSS-inflated paper risk. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity flaw requiring only low privileges - and the description notes self-registration may be enabled, which can effectively collapse the PR:L barrier toward anonymous access on many deployments. A path-traversal write primitive (CWE-24) that lands files outside the plugins directory, combined with the official Docker image running as root, yields a clean authenticated-to-root RCE chain with full C/I/A impact. Publicly available exploit code exists (a dedicated POC repository, kashishtopi/blinko-plugin-path-traversal-rce, is referenced), which raises real-world likelihood above a theoretical finding. No EPSS score was provided in the input, so exploitation probability cannot be quantified here, and the CVE is NOT on CISA KEV - there is no confirmation of active in-the-wild exploitation, only working POC code. The CVSS vector and the description are mutually consistent (network tRPC procedure, authenticated-but-low privilege, root container), so no signal conflict is present. Net: treat as a priority patch for any exposed Blinko instance, especially those allowing self-registration, while recognizing real-world urgency is tempered by the product's niche footprint and the absence of confirmed mass exploitation.

An attacker registers or uses a low-privilege account on an internet-exposed Blinko instance and invokes the plugin.installPlugin tRPC procedure with a plugin name containing ../ sequences, causing downloaded plugin files to be written outside the plugins directory. By overwriting a root-owned startup file inside the root-running Docker container, the attacker achieves remote code execution as root. Working POC exploit code is publicly available, lowering the skill required.