CVE-2026-115366 openbao CVE debrief

Who should care

Defenders and administrators of OpenBao instances, particularly those using versions 2.3.0 to 2.6.2, should assess exposure and prioritize verification and remediation. This includes reviewing and restricting access to plugin registration APIs, monitoring for suspicious activity, and planning for upgrades or mitigations. Security teams should track exceptions, retest remediated assets, and verify evidence of remediation.

Why it matters

Defenders should care about CVE-2026-115366 as it allows unauthorized modifications to plugin registrations in OpenBao, potentially causing denial of service. Affected versions require verification, and upgrading to 2.6.3 or later is recommended.

• Potential denial of service due to unauthorized plugin registration modifications
• Need to verify and restrict access to /v1/sys/plugins/catalog/*
• Possible impact on plugin registration integrity

Technical summary

The vulnerability allows privileged child-namespace tokens to modify plugin registrations due to /v1/sys/plugins/catalog/* not being restricted to the root namespace, potentially causing denial of service. This improper authorization vulnerability can lead to unauthorized modifications to plugin registrations. Affected OpenBao versions require verification and potential remediation through upgrades or access control adjustments. Defenders should prioritize verifying and upgrading to OpenBao 2.6.3 or later, and restrict access to /v1/sys/plugins/catalog/* to root namespaces only.

Defensive priority

Defenders should prioritize verifying and upgrading to OpenBao 2.6.3 or later, and restrict access to /v1/sys/plugins/catalog/* to root namespaces only.

Recommended defensive actions

• Verify OpenBao version and upgrade to 2.6.3 or later if necessary
• Restrict access to /v1/sys/plugins/catalog/* to root namespaces only
• Monitor plugin registrations and modifications
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, but additional verification is needed to confirm affected versions and potential impacts. OpenBao instances using versions 2.3.0 to 2.6.2 may be vulnerable. Verification should include reviewing plugin registrations and access controls. Defensive measures include restricting access to /v1/sys/plugins/catalog/* to root namespaces only and monitoring plugin registration modifications.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.