Missing Authentication for Critical Function Affecting github.com/openbao/openbao/v2/internal/vault/identity package, versions <2.6.5>=2.7.0-beta20260909 <2.7.2


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.43% (39th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Missing Authentication for Critical Function vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-GOLANG-GITHUBCOMOPENBAOOPENBAOV2INTERNALVAULTIDENTITY-22566197
  • published16 Nov 2026
  • disclosed13 Nov 2026
  • creditdatosh

Introduced: 13 Nov 2026

NewCVE-2026-126310  (opens in a new tab)
CWE-287  (opens in a new tab)
CWE-306  (opens in a new tab)

How to fix?

Upgrade github.com/openbao/openbao/v2/internal/vault/identity to version 2.6.5, 2.7.2 or higher.

Overview

github.com/openbao/openbao/v2/internal/vault/identity is an OpenBao is a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys.

Affected versions of this package are vulnerable to Missing Authentication for Critical Function via the isFlowAllowed function in the identity OIDC provider. An unauthenticated caller who knows a public client’s client_id can request a client-credentials token from the provider’s token endpoint when that grant is enabled for the client; OpenBao issues an OIDC ID token without requiring a secret, allowing the caller to impersonate the client.

Workarounds

  • For clients with client_type=public, set client_credentials=false and do not enable client_credentials=true; this prevents unauthenticated callers from obtaining tokens through the client-credentials grant.

CVSS Base Scores

version 4.0
version 3.1