OPENBAO · CVE-2026-126310 · Infrastructure
NO FIX YET · SEE WHAT TO DO
OpenBao before 2.6.5 and 2.7.2 lets anyone who knows a public OIDC client's client_id request ID tokens from the identity/oidc/provider token endpoint without a secret. An attacker can impersonate that client and obtain identity tokens they are not entitled to.
first public Oct 26, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running OpenBao with the OIDC identity provider enabled and at least one public client configured with client_credentials. Deployments without the OIDC provider, or where every client is confidential, are less exposed. The sources do not detail further configuration conditions.
Not affected if no-public-clients, oidc-provider-unused
Who cares oidc, openbao, self-hosted
bao version; versions below 2.6.5 or 2.7.2 on their respective branches are affected.2.6.5 (2.6 branch) or 2.7.2 (2.7 branch).OpenBao before 2.6.5 and 2.7.2 contains an authentication bypass vulnerability that allows unauthenticated callers to obtain OIDC ID tokens by abusing public clients with client_credentials enabled. Attackers who know a public client's client_id can request tokens from the identity/oidc/provider/<name>/token endpoint to impersonate the client without any secret.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.