CVE-2026-115366: 
Wolfi vulnerability analysis and mitigation

CVE-2026-115366 is an improper authorization vulnerability in OpenBao affecting versions 2.3.0 through 2.6.2, where the plugin registration API endpoint /v1/sys/plugins/catalog/* is not restricted to the root namespace. This allows sufficiently privileged child-namespace tokens to modify plugin registrations, potentially causing denial of service. The vulnerability was published on October 22, 2026, and carries a CVSS v3.1 base score of 2.6 (Low) and a CVSS v4.0 base score of 2.0 (Low) (GitHub Advisory, Feedly).

The root cause is classified as CWE-863 (Incorrect Authorization): OpenBao's plugin registration APIs (/v1/sys/plugins/catalog/*) fail to enforce that write and delete operations can only originate from the root namespace, allowing child-namespace tokens with sufficient privileges to interact with the global plugin catalog via the sys/ mount of their namespace. An attacker must possess a privileged token within a child namespace and requires user interaction (active) to exploit the flaw over the network. Exploitation is constrained by the requirement that plugin execution only occurs if the command parameter matches a valid file in the host's configured plugin directory and the sha256sum matches the file on disk, limiting realistic impact to denial-of-service scenarios (GitHub Advisory).

Successful exploitation allows a privileged child-namespace attacker to remove existing plugin registrations, create invalid registrations, or register installed plugins through their namespace's sys/ mount, resulting in denial of service for OpenBao's plugin subsystem. There is no confidentiality or integrity impact on data, and lateral movement or data exfiltration is not a realistic outcome given the constraints on plugin execution. The impact is limited to availability of the affected OpenBao instance's plugin functionality (GitHub Advisory, Feedly).

No public proof-of-concept exploit code or in-the-wild exploitation has been reported for CVE-2026-115366. The EPSS score is 0.0, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation requires a low-privilege token within a child namespace and active user interaction, significantly limiting the attack surface (Feedly, GitHub Advisory).

1. Obtain a privileged child-namespace token: Acquire a token within a child namespace that has write or delete capabilities on sys/plugins/catalog/* within that namespace.
2. Identify the target endpoint: Locate the OpenBao instance's API endpoint at /v1/sys/plugins/catalog/ accessible via the child namespace's sys/ mount.
3. Manipulate plugin registrations: Use the privileged token to send HTTP requests (PUT/DELETE) to /v1/sys/plugins/catalog/<type>/<name> to remove existing plugin registrations, create invalid ones, or register installed plugins with arbitrary parameters.
4. Cause denial of service: By removing or corrupting critical plugin registrations, disrupt OpenBao's ability to load or execute plugins, degrading service availability for the affected instance (GitHub Advisory).

• Network: Unexpected API calls to /v1/sys/plugins/catalog/* originating from child-namespace tokens rather than root-namespace administrative tokens.
• Logs: OpenBao audit logs showing PUT or DELETE requests to sys/plugins/catalog/ endpoints authenticated with child-namespace tokens; repeated or unusual plugin registration modifications in audit trails.
• Application Behavior: Plugin load failures or missing plugin registrations that were previously configured; OpenBao error logs indicating plugins cannot be found or are misconfigured after unexpected catalog changes.

Upgrade OpenBao to version 2.6.3 or 2.7.0, which patch this vulnerability. As a workaround, ensure that tenants who should not control the plugin catalog are not granted write or delete capabilities on sys/plugins/catalog/* within their namespaces via policy configuration. Alternatively, disable external plugins entirely by not configuring a plugin_directory in the OpenBao server configuration (GitHub Advisory).

The vulnerability was independently reported by three researchers — @satoqz, @MarcIlunga, and @opensec-intelligence — before the initial report was published, indicating some level of community awareness. No significant media coverage or notable public commentary beyond the official advisory has been identified at this time (GitHub Advisory).