cve.bz

CVE-2026-105820 hashicorp vault enterprise: Path traversal

5.4 mediumEPSS 0.2%Fix available

Medium (5.4) in hashicorp vault enterprise. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Vault's ACL policy cache allowed namespace traversal when policy names contained path traversal constructs. This may allow a token assigned specially crafted policy names to use the capabilities of policies defined in other namespaces, including the root namespace. This vulnerability (CVE-2026-105820) is fixed in Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23. Vault Community Edition does not support namespaces, and is not affected.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • HashiCorp Vault Enterprise: fixed in 1.21.12
  • HashiCorp Vault Enterprise: fixed in 1.20.17
  • HashiCorp Vault Enterprise: fixed in 1.19.23

Ask an AI about this CVE

Show the promptExplain CVE-2026-105820 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105820?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105820?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-105820 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.

Affected

  • hashicorp:vault enterprise

Versions

From the CNA's record in the CVE List.

ProductAffected
HashiCorp Vault Enterprisefrom 0.0.1 before 2.1.2

Fixed in

ProductFixed in
HashiCorp Vault Enterprise1.21.12
HashiCorp Vault Enterprise1.20.17
HashiCorp Vault Enterprise1.19.23

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat has evaluated this vulnerability as having a Moderate security impact because exploitation requires an authenticated attacker with permissions to create or associate manipulated policy definitions, and the affected namespace functionality is exclusive to proprietary enterprise deployments rather than open-source distributions. In typical Red Hat environments, integrating products act as Vault clients or interact with standard community editions where multi-tenant namespaces are not supported. Consequently, the flaw cannot be triggered in standard default configurations without an external enterprise deployment and delegated policy management.

ProductPackageStateAdvisory
Red Hat Openshift Data Foundation 4odf4/cephcsi-rhel9Under investigation
Red Hat Openshift Data Foundation 4odf4/mcg-cli-rhel9Under investigation
Red Hat Openshift Data Foundation 4odf4/mcg-rhel9-operatorUnder investigation

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105820.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic 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-126 Path Traversal Likelihood: High · Severity: Very High

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

References

Check your stackJSON