Advisory record · GHSA-mwgr-84fv-3jh9

Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users

CVSS 3.7 LowEPSS 0.0038 · 32nd 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<1.20.11.20.1
Identifiers
GHSA-mwgr-84fv-3jh9 · BIT-vault-2025-6011 · CVE-2025-6011 · GO-2025-3839
Weakness (CWE)
CWE-203
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.

A timing side channel in the userpass auth method of github.com/hashicorp/vault before 1.20.1 lets an attacker tell whether a username exists, which can enable username enumeration. The source does not describe the required network position or access level. Upgrade to version 1.20.1 or later; the source also lists fixed versions for Vault Enterprise 1.19.7, 1.18.12, and 1.16.23.

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
3.7 Low 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (HashiCorp)
  • CISA KEV Not listed.
  • EPSS 0.0038, the 32nd percentile, on 17 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.