cve.bz

CVE-2026-105816 hashicorp: Path traversal

8.0 highEPSS 0.3%Fix available

High (8.0) in hashicorp. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Vault and Vault Enterprise did not consistently verify that stored plugin catalog entries reference binaries within the configured plugin directory. When Vault uses Shamir seals and has an external plugin directory configured, a privileged operator able to restore an Integrated Storage (Raft) snapshot may be able to execute arbitrary code on the Vault host. This vulnerability (CVE-2026-105816) is fixed in Vault Community Edition 2.1.2, and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23.

Severity

CVSS 3.1

8.0 high
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th 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: total, 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-105816 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105816?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105816?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-105816 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

Versions

From the CNA's record in the CVE List.

ProductAffected
HashiCorp Vaultfrom 0.0.1 before 2.1.2
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 Important.

Red Hat's statement

An Important severity arbitrary code execution flaw was found in HashiCorp Vault, affecting Red Hat OpenShift Data Foundation 4 containers that bundle the Vault component. Vault verifies that a plugin binary resolves within the configured plugin directory when the plugin is registered, but it did not consistently verify stored plugin catalog entries when they are later used to run a plugin. Consequently, when Vault uses Shamir seals and has an external plugin directory configured, a privileged operator able to restore an Integrated Storage (Raft) snapshot containing a modified catalog entry can cause Vault to execute a binary outside the plugin directory as the Vault service user, including during unseal for existing mounts. This gives the operator arbitrary code execution on the underlying host with high impact to confidentiality, integrity, and availability. Clusters using auto-unseal, or with no external plugin directory configured, are not affected. For Red Hat OpenShift Data Foundation 4, resolution of this issue is delegated: the affected containers bundling the Vault component have a fix being pursued, while the odf4/cephcsi-rhel9 container was determined not to include the affected component and is not affected. The Red Hat severity (CVSS 8.0, Important) matches the upstream assessment.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Openshift Data Foundation 4odf4/cephcsi-rhel9Not affected
Red Hat Openshift Data Foundation 4odf4/mcg-cli-rhel9Affected
Red Hat Openshift Data Foundation 4odf4/mcg-rhel9-operatorAffected

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-105816.

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