cve.bz

CVE-2026-126309 OpenBao before 2.6.5 and 2.7.2 Path Traversal in Transit Key Import

7.6 highEPSS 0.4%

High (7.6) in openbao openbao. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
OpenBao before 2.6.5 and 2.7.2 contains a path traversal vulnerability in Transit key import that allows authenticated attackers to bypass name restrictions in ACL policies. Attackers limited by a required_parameters name constraint can craft traversal sequences during import to write key material under arbitrary Transit key names.

Severity

CVSS 4.0

7.6 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-73 External Control of File Name or Path
OWASP Top 10
A06:2025 Insecure Design
Published
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126309 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126309?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126309?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126309 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126309

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126309](https://cve.bz/cve/badge/CVE-2026-126309.svg)](https://cve.bz/cve/CVE-2026-126309)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126309"><img src="https://cve.bz/cve/badge/CVE-2026-126309.svg" alt="CVE-2026-126309"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
openbaobefore 2.6.5
openbaofrom 2.7.0 before 2.7.2

Attack patterns (CAPEC)

  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-72 URL Encoding Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON