openbao: Improper Handling of Case Sensitivity
CVE-2026-126312 is a high-severity improper handling of case sensitivity vulnerability in openbao, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 2.6.5, 2.7.2, 0.2.0 as the first without the flaw, so updating openbao to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.42% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update openbao to 2.6.5 or 2.7.2 or 0.2.0, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Openbao | openbao | before 2.6.5; 2.7.0 up to, but not including, 2.7.2; before 0.2.0 | 2.6.5, 2.7.2, 0.2.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.6 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 7.1 | High | CNA (vulncheck.com) |
Official description
OpenBao before 2.6.5 and 2.7.x before 2.7.2, and the openbao-plugins LDAP and RADIUS auth plugins before 0.2.0, contain an ACL bypass in the AppRole, Cert, LDAP, and RADIUS auth methods caused by implicit path canonicalization. Authenticated attackers can request non-canonical paths for AppRole Role IDs, Cert CRLs, LDAP groups and users, or RADIUS users to evade ACL deny rules.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Handling of Case Sensitivity
The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.
How developers prevent this class of flaw
- Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
More Improper Handling of Case Sensitivity vulnerabilities (CWE-178)
Timeline
- CVE record published.
References
Other references
Other vulnerabilities in openbao
- 8.7 High severity
- 7.1 High severity
- 9.2 Critical severity
- 7.5 High severity
- 7.1 High severity
- 7.5 High severity
Recent Improper Handling of Case Sensitivity vulnerabilities
- 9.4 Critical severity
- 9.4 Critical severity
- 8.6 High severity
- 7.1 High severity
- 8.1 High severity
- 8.8 High severity
Spotted an error? Tell us.