---
id: "CVE-2026-126311"
page: "https://infrastack.ai/live/CVE-2026-126311"
kind: "vulnerability"
aliases: ["CVE-2026-126311"]
title: "OpenBao: unescaped wildcards in SSH certificate principals enable broad certificates"
severity: "medium"
cvss: 5.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["openbao", "package", "self-hosted", "ssh", "vault-compatible"]
not_affected_if: ["no-ssh-secrets-engine", "static-principals", "trusted-identity-provider"]
published_at: "2026-11-13T10:17:36+00:00"
first_seen_at: "2026-11-13T10:47:15+00:00"
updated_at: "2026-11-13T10:56:47+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126311", "first_seen_at": "2026-11-13T10:47:15+00:00"}]
exploit_sources: []
---

# OpenBao: unescaped wildcards in SSH certificate principals enable broad certificates

Link for people: https://infrastack.ai/live/CVE-2026-126311 (this .md is for agents)

OpenBao's SSH secrets engine builds certificate principals from external token metadata without neutralizing '*' wildcard characters. An attacker who controls that metadata, typically through a compromised identity provider, can obtain SSH certificates valid for multiple hosts or users.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the OpenBao server version with `bao version`; versions before `2.6.5` and `2.7.x` before `2.7.2` are affected.
- Look for SSH secrets engine roles that use identity templates to build principals from token metadata.
- Review which identity providers can set that token metadata.

## Fix

- OpenBao `2.6.5` and later in the 2.6 line
- OpenBao `2.7.2` and later in the 2.7 line

## Timeline

- 2026-11-13T10:47:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126311

## Documents

- [advisory] Vendor advisory: github.com https://github.com/openbao/openbao/security/advisories/GHSA-h76r-48x5-36hg
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/openbao-before-2.6.5-and-2.7.2-wildcard-principals-in-ssh-certificates-via-identity-templates

## From the sources

OpenBao before 2.6.5 and 2.7.x before 2.7.2 does not neutralize wildcard characters in SSH certificate principals rendered from unvalidated external token metadata via identity templates in the SSH secrets engine. Attackers controlling that metadata, typically through a compromised identity provider, can inject '*' to obtain SSH certificates valid for multiple hosts or users.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_