CVSS 3.1
8.0 highCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HHigh (8.0) in hashicorp. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| HashiCorp Vault | from 0.0.1 before 2.1.2 |
| HashiCorp Vault Enterprise | from 0.0.1 before 2.1.2 |
| Product | Fixed in |
|---|---|
| HashiCorp Vault Enterprise | 1.21.12 |
| HashiCorp Vault Enterprise | 1.20.17 |
| HashiCorp Vault Enterprise | 1.19.23 |
Red Hat rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Openshift Data Foundation 4 | odf4/cephcsi-rhel9 | Not affected | |
| Red Hat Openshift Data Foundation 4 | odf4/mcg-cli-rhel9 | Affected | |
| Red Hat Openshift Data Foundation 4 | odf4/mcg-rhel9-operator | Affected |
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.