Skip to main content
CVE-2026-126311VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-126311· Medium 4.6

Not known to be exploited · CVSS 4.6 Medium : upgrade to 2.7.2 or 2.6.5 when convenient.

Data as of 13 Nov 2026, 13:04 UTC

CVSS 4.0 base score
4.6Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.04.6
CNA (VulnCheck)CVSS 3.15.8
Patch
Available – fixed in 2.7.2, 2.6.5
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade openbao to 2.7.2 or 2.6.5.

Affected software

ProductAffectedFixed in
openbaoopenbaoAffected
  • >=2.7.0 <2.7.2
Fixed in
  • 2.7.2
openbaoopenbaoAffected
  • <2.6.5
Fixed in
  • 2.6.5
Goopenbaopkg:golang/openbaoOther threatsAffected
  • <2.6.5
  • >=2.7.0 <2.7.2
Fixed in
  • 2.6.5
  • 2.7.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…