Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.28% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-5006High confidence
Vault Vulnerable to Privilege Escalation via Slash Injection in Templated Policy Paths
HashiCorp · Vault
6.8MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 6 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs HashiCorp Vault and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 6 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 6 affected or under-investigation product states without a fixed product state in the same current advisory
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-5006 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityVault: Vault Enterprise: Vault: Privilege Escalation via Slash Injection in Templated Policy Paths
The vendor explicitly identifies these products as affected by this CVE.
- odf4/cephcsi-rhel9 as a component of Red Hat Openshift Data Foundation 4
- odf4/mcg-cli-rhel9 as a component of Red Hat Openshift Data Foundation 4
- odf4/mcg-rhel9-operator as a component of Red Hat Openshift Data Foundation 4
- rhceph-dev/odf4-cephcsi-rhel9 as a component of Red Hat Openshift Data Foundation 4
- rhceph-dev/odf4-mcg-cli-rhel9 as a component of Red Hat Openshift Data Foundation 4
- rhceph-dev/odf4-mcg-rhel9-operator as a component of Red Hat Openshift Data Foundation 4
- Summary
- A flaw was found in HashiCorp Vault. An authenticated attacker can manipulate identity values in templated policy paths by injecting slash characters. This manipulation allows Vault to misinterpret policy paths, leading to unintended access to Vault resources and potential privilege escalation.
- Remediation
- 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.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 6 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
A vulnerability was identified in HashiCorp Vault and Vault Enterprise (“Vault”) such that an authenticated attacker may manipulate an identity value referenced by a templated policy path to gain unintended access to Vault paths. An attacker who can control the referenced identity value may include slash ({{/}}) characters that Vault interprets as additional path segments when rendering the policy. This vulnerability, CVE-2026-5006, was fixed in Vault Community Edition 2.0.4 and Vault Enterprise 2.0.4, 1.21.9, 1.20.14, and 1.19.20.
What
A vulnerability was identified in HashiCorp Vault and Vault Enterprise (“Vault”) such that an authenticated attacker may manipulate an identity value referenced by a templated policy path to gain unintended access to Vault paths. An attacker who can control the referenced identity value may include slash ({{/}}) characters that Vault interprets as additional path segments when rendering the policy. This vulnerability, CVE-2026-5006, was fixed in Vault Community Edition 2.0.4 and Vault Enterprise 2.0.4, 1.21.9, 1.20.14, and 1.19.20.
Why
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
A vulnerability was identified in HashiCorp Vault and Vault Enterprise (“Vault”) such that an authenticated attacker may manipulate an identity value referenced by a templated policy path to gain unintended access to Vault paths. An attacker who can control the referenced identity value may include slash ({{/}}) characters that Vault interprets as additional path segments when rendering the policy. This vulnerability, CVE-2026-5006, was fixed in Vault Community Edition 2.0.4 and Vault Enterprise 2.0.4, 1.21.9, 1.20.14, and 1.19.20.
Why
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Authorization Bypass Through User-Controlled Key → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-639 ↗
CWE-639: Authorization Bypass Through User-Controlled Key. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- odf4/cephcsi-rhel9 as a component of Red Hat Openshift Data Foundation 4
- odf4/mcg-cli-rhel9 as a component of Red Hat Openshift Data Foundation 4
- odf4/mcg-rhel9-operator as a component of Red Hat Openshift Data Foundation 4
- rhceph-dev/odf4-cephcsi-rhel9 as a component of Red Hat Openshift Data Foundation 4
- rhceph-dev/odf4-mcg-cli-rhel9 as a component of Red Hat Openshift Data Foundation 4
- rhceph-dev/odf4-mcg-rhel9-operator as a component of Red Hat Openshift Data Foundation 4
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- 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.
04
Evidence and provenance
Published 24 Aug 2026 · Last source change 26 Aug 2026, 03:56 UTC · CWE-639 · Authorization Bypass Through User-Controlled Key
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-25
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-65122
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-5006 to remediation: access.redhat.com/CVE-2026-5006.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-5006
- After
- remediation: access.redhat.com/CVE-2026-5006
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- odf4/cephcsi-rhel9 as a component of Red Hat Openshift Data Foundation 4; odf4/mcg-cli-rhel9 as a component of Red Hat Openshift Data Foundation 4; odf4/mcg-rhel9-operator as a component of Red Hat Openshift Data Foundation 4
- After
- odf4/cephcsi-rhel9 as a component of Red Hat Openshift Data Foundation 4; odf4/mcg-cli-rhel9 as a component of Red Hat Openshift Data Foundation 4; odf4/mcg-rhel9-operator as a component of Red Hat Openshift Data Foundation 4; rhceph-dev/odf4-cephcsi-rhel9 as a component of Red Hat Openshift Data Foundation 4; rhceph-dev/odf4-mcg-cli-rhel9 as a component of Red Hat Openshift Data Foundation 4; rhceph-dev/odf4-mcg-rhel9-operator as a component of Red Hat Openshift Data Foundation 4
- ENISA EUVD mappingEUVD-2026-65122 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-65122"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.