stigmem-node version 0.9.0a1 permits disabling plugin signature enforcement through a single configuration flag without the required second acknowledgment. This flaw allows a user who can write to the plugin directory to place unsigned, potentially malicious plugins into that directory. When the application loads these plugins, arbitrary code execution is achieved within the context of the running service. The weakness is a form of insecure or missing code verification, corresponding to CWE‑494.

The vulnerability affects the stigmem-node product from eidetic-labs, specifically version 0.9.0a1. Versions prior to 0.9.0a2, which has been released with a stricter disabling mechanism requiring a second explicit acknowledgment, are not vulnerable. Administrators should verify installation versions against the vendor’s released patches.

The vulnerability carries a CVSS score of 7.3, indicating a moderate to high potential impact. The EPSS score of < 1% suggests that exploitation remains unlikely, but the requirement for write access to the plugin directory means that an attacker with local or remote write permissions could trigger the bypass. The flaw is not listed in CISA’s KEV catalog. Based on the description, the likely attack vector is a local or remotely compromised user who can write to the plugin directory, which is inferred from the need for write access. Once exploited, it results in arbitrary code execution, providing an attacker with complete control over the affected system.