OpenBao EUVD-2026-108286

Exploitation requires a specific policy shape: a policy that grants access via a global explicit wildcard AND contains an explicit narrow deny rule built on an identity-metadata template that includes wildcard or path segments; under these conditions the deny rule is silently dropped. The exploiting principal's identity metadata must itself contain wildcard or path segments. Key LIMITING factors: the attacker must already be an authenticated OpenBao principal; identity metadata is normally set by a fully trusted IDP and not attacker-controlled, so an attacker must be able to influence that metadata or rely on a misconfigured IDP; and the vulnerable wildcard-plus-templated-denial policy must actually be deployed. Access gained is confined to paths already within the broader wildcard grant - it is not an unrestricted bypass. The non-restricted-templating variant is noted as less likely to occur.

All severity signals converge on LOW real-world risk. The vendor-supplied CVSS 4.0 base score is 2.1 and the vuln.today decision label is 'monitor' - not act_now or emergency. The vector (AV:N/AC:H/AT:P/PR:H/UI:N) describes a network-reachable but high-complexity flaw with an explicit attack requirement and high privileges, and impact is only Low across confidentiality, integrity and availability with no scope change. This is a high-complexity, authorization-only weakness (CWE-863), not a remote unauthenticated takeover. The GHSA advisory further constrains it: identity metadata is normally set by a fully trusted IDP and is not attacker-controlled, so the preconditions (a policy with a global explicit wildcard grant AND a templated narrow denial AND identity metadata containing wildcard/path segments) rarely align in practice. It is not in CISA KEV, so this is NOT confirmed active exploitation. No EPSS score was provided in the input, so exploitation probability cannot be quantified here. No public exploit code is identified - the two references are vendor/coordination advisories, not working exploit code. Net: this is a genuine but narrow, operator-/config-dependent ACL bypass, appropriately rated low priority; it is a patch-on-normal-cycle item, not an emergency.

An authenticated OpenBao principal whose identity metadata happens to contain wildcard or path segments operates under a policy that grants broad access via a global explicit wildcard but is supposed to be narrowed by a templated explicit deny rule. Because that templated denial is silently dropped during policy evaluation, the principal can read or act on paths inside the wildcard scope that the operator believed were denied. No public exploit code is identified at time of analysis - only vendor advisories (GHSA, VulnCheck) exist - and the GHSA notes metadata is normally controlled by a trusted IDP, making unintended access more likely than deliberate attacker abuse.