OpenBao EUVD-2026-108289

Exploitation requires that the OpenBao Agent or Proxy is configured with require_request_header = true - the specific SSRF-hardening setting whose header enforcement this bug omits on the quit endpoints. The attacker must also be able to deliver a request to the /agent/v1/quit or /proxy/v1/quit listener, which per the CVSS PR:H and AT:P metrics presupposes a high-privilege position or a server-side request forgery primitive reaching that interface. Limiting factors: the flaw is irrelevant on deployments that do not enable require_request_header; impact is confined to availability (shutting down Agent/Proxy), with no access to secrets, no confidentiality or integrity impact; and the companion cache-clear endpoints carry no material security impact per the vendor.

This is a genuinely low-severity, low-priority issue and all available signals agree. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:H/UI:N) yields a 2.1 base score, with impact limited to availability of the vulnerable system (VA:L) and no confidentiality or integrity impact - consistent with a denial-of-service of the Agent/Proxy processes via their quit endpoints. The vuln.today Decision label is 'monitor', the lowest urgency tier, and the GHSA advisory itself notes the parallel cache-clear endpoints have 'no material security impact'. No EPSS score was provided, the CVE is not in CISA KEV, and no public exploit or PoC reference was supplied (only the GHSA and VulnCheck advisory pages) - so exploitation status is: no public exploit identified at time of analysis. The AT:P (attack requirements present) metric and PR:H reflect the two real preconditions: the require_request_header protection must be enabled, and the attacker needs a high-privilege/SSRF foothold to reach the endpoint. One nuance worth flagging: this is effectively a weakness in the SSRF hardening feature itself - the bug only matters for operators who turned on require_request_header specifically to block SSRF, so the population it affects is the security-conscious subset. The signals are internally consistent; nothing here suggests hidden severity.

An attacker who can coerce a server-side request (SSRF) through an application co-located with an OpenBao Agent or Proxy that has require_request_header enabled sends a request to http://<agent>/agent/v1/quit without the X-Vault-Header, which previously should have been rejected. The Agent or Proxy process shuts down, breaking secret delivery to dependent applications until it is restarted. No public exploit code was provided in the sources.