CVSS 3.1
6.8 mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NMedium (6.8) in hashicorp. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NExplain CVE-2026-5006 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-5006?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-5006?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-5006 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.11.0 before 2.0.4 |
| HashiCorp Vault Enterprise | from 0.11.0 before 2.0.4 |
| Product | Fixed in |
|---|---|
| HashiCorp Vault | 2.0.4 |
| HashiCorp Vault Enterprise | 1.19.20 |
| HashiCorp Vault Enterprise | 1.20.14 |
| HashiCorp Vault Enterprise | 1.21.9 |
| HashiCorp Vault Enterprise | 2.0.4 |
Red Hat rates this Important.
A privilege escalation vulnerability was found in HashiCorp Vault and Vault Enterprise. In versions 0.11.0 through 2.0.3 (and Enterprise versions through 1.21.8, 1.20.13, and 1.19.19), an authenticated attacker may manipulate an identity value referenced by a templated policy path to gain unintended access to Vault paths. The vulnerability allows attackers who can control a referenced identity value to include slash (/) characters that Vault interprets as additional path segments when rendering the policy, enabling path traversal to access secrets outside their authorized scope. This vulnerability affects the Vault server policy evaluation engine. Red Hat products that use the HashiCorp Vault Go client library (github.com/hashicorp/vault/api) to connect to external Vault servers are not directly vulnerable, as policy evaluation occurs server-side. However, customers running HashiCorp Vault servers should upgrade to fixed versions and enable the deny_slash_in_templated_paths configuration option.
For Red Hat products using the HashiCorp Vault Go client library (OpenShift Data Foundation, Ceph, and related components):
No action is required for Red Hat products. This vulnerability affects the Vault server policy evaluation engine, not client libraries. Red Hat products use the Vault Go API client to retrieve secrets from externally managed Vault servers but do not run Vault server components or evaluate policies. The vulnerable code path is not present or executed in these client library integrations.
For customers operating HashiCorp Vault servers (not Red Hat products):
1. Upgrade HashiCorp Vault to a fixed version:
- Vault Community Edition: upgrade to version 2.0.4 or later
- Vault Enterprise: upgrade to version 2.0.4, 1.21.9, 1.20.14, or 1.19.20 (depending on your current version stream)
2. After upgrading, set deny_slash_in_templated_paths = true in your Vault server configuration. This option defaults to false even after upgrade and must be explicitly enabled to prevent slash injection in templated policy paths.
3. Review templated policies that interpolate identity values (such as {{identity.entity.name}} or {{identity.entity.metadata.group}}) to ensure they follow least-privilege principles and do not grant excessive path access.
4. Audit Vault access logs for suspicious activity involving policy path evaluations with unexpected slash characters, particularly in identity metadata values.
5. Consider implementing additional access controls at the network level to limit who can authenticate to Vault servers.
Red Hat provides HashiCorp Vault containers certified for Red Hat OpenShift; these containers are maintained and patched by HashiCorp. Customers using these containers should follow HashiCorp's upgrade guidance to deploy fixed versions.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Openshift Data Foundation 4 | odf4/cephcsi-rhel9 | Affected | |
| Red Hat Openshift Data Foundation 4 | odf4/mcg-cli-rhel9 | Affected | |
| Red Hat Openshift Data Foundation 4 | odf4/mcg-rhel9-operator | Affected | |
| Red Hat Openshift Data Foundation 4 | rhceph-dev/odf4-cephcsi-rhel9 | Affected | |
| Red Hat Openshift Data Foundation 4 | rhceph-dev/odf4-mcg-cli-rhel9 | Affected | |
| Red Hat Openshift Data Foundation 4 | rhceph-dev/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-5006.
Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.