The vulnerability exists because a single configuration setting, plugin_signing_required, defaulted to False, which disabled signature verification for plugins. This allowed a user with access to the plugin directory to load and execute unsigned code. The core of the vulnerability lies in the stigmem_node.plugins.lifecycle.register_discovered_plugins function, which contains the conditional logic that bypasses signature checks based on this flag.
The patch addresses this in two main ways. First, it changes the default value of plugin_signing_required to True in node/src/stigmem_node/settings.py, making the secure configuration the default. Second, it introduces a new middleware, stigmem_node.main.unsigned_plugin_override_warning, which logs a prominent warning on every single HTTP request if the insecure setting is active. This ensures that running in the vulnerable configuration is an explicit and noisy choice, rather than an insecure default.
Therefore, register_discovered_plugins is the function containing the vulnerable logic, and unsigned_plugin_override_warning is a key runtime indicator that would appear in logs and profiles if the system is in its vulnerable, insecurely configured state.