CVE-2026-5807: Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate

Q: How do I fix CVE-2026-5807?

vault: upgrade to 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-5807 being exploited?

CVE-2026-5807 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-5807 affect?

CVE-2026-5807 affects vault. Severity is high (CVSS 7.5). Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate or cancel root token generation or rekey operations, occupying the single in-progress operation slot. This prevents legitimate op

Q: How urgent is CVE-2026-5807?

Priority 45/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2026-5807 is a high-severity flaw (CVSS 7.5) affecting vault. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate or cancel root token generation or rekey operations, occupying the single in-progress operation slot. This prevents legitimate operators from completing these workflows. This vulnerability, CVE-2026-5807, is fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-770
Published	2026-04-17
Last modified	2026-10-26

Publisher (CNA): HashiCorp Inc. · Vendor: hashicorp

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-17 05:16 UTCPublished CVE record published
2026-10-26 22:10 UTCUpdated Record last modified

hashicorp vault UPGRADE

Affected: < 2.0.0

Fixed in: 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vault || rpm -q vault || vault --version

2. UPGRADE to 2.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vault

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vault

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-5807?

vault: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2026-5807 being exploited?

CVE-2026-5807 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-5807 affect?

CVE-2026-5807 affects vault. Severity is high (CVSS 7.5). Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate or cancel root token generation or rekey operations, occupying the single in-progress operation slot. This prevents legitimate op

How urgent is CVE-2026-5807?

Priority 45/100. High severity; Remotely exploitable, no login, no user action

Software pages

HashiCorp Vault vulnerabilities

Related CVEs

CVE-2026-3605 HIGH 8.1 UPGRADE An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secr
CVE-2026-5052 MEDIUM 5.3 UPGRADE Vault’s PKI engine’s ACME validation did not reject local targets when issuing http-01 and tls-alpn-01 challen
CVE-2026-4525 HIGH 7.5 UPGRADE If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header

References

← Back to latest CVEs