Skip to main content

OpenBao PKI EUVDEUVD-2026-108292

| CVE-2026-115369 LOW
Incorrect Authorization (CWE-863)
2026-10-22 disclosure@vulncheck.com GHSA-65vq-mjjr-475v
2.1
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with PKI sign permission
  2. Exploit
    Submit CSR with out-of-range IP SAN to pki/sign
  3. Impact
    Receive CA-signed cert for unauthorized IP

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires all of the following: the OpenBao PKI role must be configured with an allowed_ip_sans_cidr restriction; the use_csr_sans option must be enabled (this is the default); the caller must be authenticated and hold sign permission on that role; and the request must go through pki/sign/<role> with a CSR (the flaw does not affect the pki/issue path with ip_sans, which still enforces the CIDR). Limiting factors: the attacker must already be a trusted, authenticated principal with signing rights (PR:H), impact is confined to embedding an out-of-range IP SAN in an issued certificate (integrity only), and only versions 2.5.0 through 2.6.1 are affected - v2.6.2 is fixed.

Impact

This is a low-priority issue across every available signal, and the signals are mutually consistent rather than conflicting. The vendor CVSS 4.0 score is 2.1 (Low) with vector AV:N/AC:L/AT:P/PR:H/UI:N and only VI:L (limited integrity impact, no confidentiality or availability impact), reflecting that an already-privileged, authenticated caller can obtain a certificate for an IP outside the role's allowed CIDR - an authorization-restriction bypass (CWE-863), not a remote code or data-exposure flaw. The vuln.today Decision label is 'monitor', the lowest urgency tier, which aligns with the low score. No EPSS score was provided in the input, the CVE is not listed in CISA KEV, and no working exploit code is supplied (only vendor/VulnCheck advisories), so there is no evidence of exploitation probability or active abuse. The practical impact is scoped narrowly: the attacker must already hold sign permission on a CIDR-restricted PKI role, so the vulnerability lets a trusted-but-constrained caller exceed its intended IP-SAN boundary rather than granting any new foothold. Net assessment: a genuine authorization bug worth patching on a normal maintenance cycle, not an emergency.

Exploit ScenarioDerived

An authenticated operator who holds sign permission on an OpenBao PKI role that is CIDR-restricted via allowed_ip_sans_cidr crafts a CSR containing an IP SAN outside the permitted range and submits it to pki/sign/<role> with use_csr_sans enabled (the default). OpenBao fails to apply the CIDR check to CSR-sourced IP SANs and returns a CA-signed certificate embedding the unauthorized IP, even though the same IP would be rejected through pki/issue with ip_sans. No public working exploit code is identified; only vendor advisories exist.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 22, 2026

OpenBao 2.5.0 through 2.6.1 will issue a CA-signed certificate bearing an out-of-range IP SAN when a caller submits a CSR to pki/sign/<role> on a role that has allowed_ip_sans_cidr set and use_csr_sans enabled - the latter being the default - so the CIDR restriction that is correctly applied to explicit ip_sans on pki/issue is silently bypassed on the sign path. Only authenticated principals already holding sign permission on such a role can reach the endpoint, and the consequence is limited to integrity (an unauthorized IP embedded in a certificate), which is why the vendor and independent scoring both rate it low severity. The flaw is fixed in OpenBao 2.6.2; no public exploit has been identified at time of analysis and the issue is tracked at monitor priority. Affected deployments are those running PKI roles with CIDR-restricted IP SANs on 2.5.0-2.6.1.

RemediationAI

Upgrade to OpenBao 2.6.2, the version named in the vendor advisory as the fix (https://github.com/openbao/openbao/security/advisories/GHSA-g892-p242-8g86), on any deployment running 2.5.0 through 2.6.1 with PKI roles that set allowed_ip_sans_cidr. The advisory publishes no workaround beyond upgrading and does not otherwise document compensating configuration. Pending the upgrade, note that the exposure is confined to the CSR-based sign path: the pki/issue path with explicit ip_sans continues to enforce the CIDR restriction, so audits can focus on certificates issued via pki/sign/<role> on CIDR-restricted roles and on which principals hold sign permission on those roles. Reviewing issued certificates for IP SANs outside the intended ranges helps establish whether the gap was exercised.

Affected VersionsENISA

openbao 2.5.0 <2.6.2

Affected Packages

euvd openbao fix: 2.6.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

OpenBao's PKI secrets engine lets an operator constrain a role with allowed_ip_sans_cidr, so that IP SANs requested in a certificate are limited to approved network ranges. The corresponding feature flag use_csr_sans (default true) instructs the sign endpoint to carry SANs forward from the submitted CSR rather than requiring them to be passed as API parameters. The two paths diverge: pki/issue/<role> validates caller-supplied ip_sans against the CIDR list, while pki/sign/<role> with use_csr_sans copies IP SANs out of the CSR without applying the same check. Classified as CWE-863 (incorrect authorization), the defect is a missing enforcement branch on one code path rather than a flaw in the CIDR comparison itself - an authenticated caller with sign rights on a restricted role can therefore obtain a CA-backed certificate embedding an IP the role was meant to exclude. The precise trigger is documented in the vendor advisory: a CSR containing an out-of-range IP SAN submitted to the sign endpoint; the issue path with explicit ip_sans still enforces the CIDR correctly. Only CSR-derived IP SANs are affected; the advisory does not describe other SAN types or other PKI paths being impacted.

Know when Openbao gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 2.1 LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 2.7 LOW

Requires an authenticated caller with sign permission (PR:H) over the network with no user interaction; impact is limited to improperly issuing a certificate (I:L), with no confidentiality or availability effect.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Oct 22, 2026 - 20:18 EUVD

DescriptionCVE.org

OpenBao from 2.5.0 before 2.6.2 fails to enforce the PKI role allowed_ip_sans_cidr restriction on IP SANs taken from a CSR when use_csr_sans is enabled. Authenticated callers with sign permission can submit a CSR with an out-of-range IP SAN to pki/sign/<role> and obtain CA-signed certificates for unauthorized IPs.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
newer open-source Vault fork, limited production footprint relative to upstream
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

10
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2024-2048 CRITICAL
9.8 Mar 04

Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when con

CVE-2026-63132 CRITICAL
9.2 Sep 22

Timing-based leakage of the single recovery token in OpenBao lets a remote, unauthenticated attacker who can reach the i

CVE-2025-54997 CRITICAL
9.1 Aug 09

OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certifi

CVE-2024-7594 HIGH
8.8 Sep 26

Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default. Rated high severity

CVE-2025-59048 HIGH
8.1 Oct 23

Cross-account IAM role impersonation in OpenBao's auth-aws plugin (versions up to and including 0.1.0) lets an authentic

CVE-2026-71543 HIGH
7.5 Sep 21

OpenBao versions prior to 2.6.0 fail to reject syntax-significant characters when templated identity data is substituted

CVE-2025-59043 HIGH
7.5

Unauthenticated denial of service in OpenBao 2.4.0 and earlier allows remote attackers to crash the server or exhaust CP

CVE-2025-64761 HIGH
7.5 Nov 25

OpenBao is an open source identity-based secrets management system. Rated high severity (CVSS 7.5), this vulnerability i

CVE-2025-52894 HIGH
7.5 Jun 25

OpenBao versions before 2.3.0 contain an unauthenticated denial-of-service vulnerability in the root rekey and recovery

CVE-2026-115365 HIGH
7.5 Oct 22

Cross-namespace privilege escalation in OpenBao 2.3.0 through 2.6.2 allows an authenticated token holder to attach speci

CVE-2024-8185 HIGH
7.5 Oct 31

Vault Community and Vault Enterprise (“Vault”) clusters using Vault’s Integrated Storage backend are vulnerable to a den

CVE-2024-9180 HIGH
7.2 Oct 10

A privileged Vault operator with write permissions to the root namespace’s identity endpoint could escalate their own or

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy