Advisory record · GHSA-6h4p-m86h-hhgh

Hashicorp Vault has Privilege Escalation Vulnerability

CVSS 7.2 HighEPSS 0.0053 · 45th percentile

Published by the GitHub Advisory Database at 1 Aug 2025, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/hashicorp/vaultGo>=0.10.4, <1.20.01.20.0
Identifiers
GHSA-6h4p-m86h-hhgh · BIT-vault-2025-5999 · CVE-2025-5999 · GO-2025-3837
Weakness (CWE)
CWE-266
Published
1 Aug 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

HashiCorp Vault versions 0.10.4 up to but not including 1.20.0 are affected. A privileged operator with write access to the root namespace's identity endpoint can raise their own or another user's token to Vault's root policy. Upgrade to Vault 1.20.0, or to 1.19.6, 1.18.11 or 1.16.22 for Vault Enterprise.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H CNA (HashiCorp)
  • CISA KEV Not listed.
  • EPSS 0.0053, the 45th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.