cve.bz

CVE-2025-5999 (Vault Fault) hashicorp vault: Incorrect Privilege Assignment

7.2 highEPSS 0.5%Fix available

Known as Vault Fault

High (7.2) in hashicorp vault. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/hashicorp/vault 1.20.0.

On this page
A privileged Vault operator with write permissions to the root namespace’s identity endpoint could escalate their own or another user’s token privileges to Vault’s root policy. Fixed in Vault Community Edition 1.20.0 and Vault Enterprise 1.20.0, 1.19.6, 1.18.11 and 1.16.22.

Severity

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-21. 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 2025-08-01. 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-266 Incorrect Privilege Assignment
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-5999 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-5999?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-5999?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-2025-5999 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.10.4 before 1.20.0
HashiCorp Vault Enterprisefrom 0.10.4 before 1.20.0

Fixed in

ProductFixed in
HashiCorp Vault Enterprise1.19.6
HashiCorp Vault Enterprise1.18.11
HashiCorp Vault Enterprise1.16.22

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6h4p-m86h-hhghGogithub.com/hashicorp/vault>=0.10.4 <1.20.01.20.0
GO-2025-3837Gogithub.com/hashicorp/vault>=0.10.4 <1.20.01.20.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20250814T182633-150000.1.98.1SUSE-SU-2025:02912-1
openSUSELeap 15.6govulncheck-vulndb0.0.20250814T182633-150000.1.98.1SUSE-SU-2025:02912-1
openSUSETumbleweedgovulncheck-vulndb0.0.20250811T192933-1.1openSUSE-SU-2025:15434-1
openSUSETumbleweedopenbao2.3.2-1.1openSUSE-SU-2025:15460-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is Important rather than Moderate because it enables direct privilege escalation to the Vault root policy, granting unrestricted administrative control over the entire Vault environment. While the attacker must already have write access to the root namespace’s identity endpoint, that permission alone does not normally confer root-level authority—this flaw breaks the intended privilege separation model. By exploiting it, an attacker can craft malicious writes to the identity endpoint to bind their own or another user’s token to the root policy, bypassing all policy restrictions. With root access, the attacker can exfiltrate every stored secret, modify or delete sensitive data, disable audit logs to cover tracks, and introduce persistent backdoors.

Red Hat's mitigation

Until you can upgrade to a fixed release, mitigation options include applying Sentinel EGP policies to prevent assignment of the root policy via the identity API, and closely monitoring Vault audit logs for tokens with "identity_policies": ["root"].

ProductPackageStateAdvisory
cert-manager Operator for Red Hat OpenShiftcert-manager/cert-manager-operator-rhel9Affected
cert-manager Operator for Red Hat OpenShiftcert-manager/jetstack-cert-manager-acmesolver-rhel9Affected
cert-manager Operator for Red Hat OpenShiftcert-manager/jetstack-cert-manager-rhel9Affected
external secrets operator for Red Hat OpenShift - Tech Previewexternal-secrets-operator/external-secrets-operator-rhel9Not affected
Red Hat Openshift Data Foundation 4odf4/cephcsi-rhel9Not affected
Red Hat Openshift Data Foundation 4odf4/mcg-cli-rhel9Not affected
Red Hat Openshift Data Foundation 4odf4/mcg-rhel9-operatorNot affected
Red Hat Openshift Data Foundation 4odf4/odf-cli-rhel9Not affected
Red Hat Trusted Artifact Signerrhtas/client-server-rhel9Not affected
Red Hat Trusted Artifact Signerrhtas/fulcio-rhel9Not 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-2025-5999.

References

Check your stackJSON