Is CVE-2026-5807 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-5807 being exploited in the wild.

How severe is CVE-2026-5807?

High severity, with a CVSS score of 7.5, published 17 April 2026.

Which products and versions are affected?

github.com/hashicorp/vault (Go) <= 1.21.4, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.21.4; HashiCorp Vault Community Edition <= 1.21.4, up to 1.21.4, fixed in 2.0.0; HashiCorp Vault Enterprise <= 1.21.4, 1.20.9, 1.19.15, up to 1.21.4, 1.20.9, and 1.19.15; fixed in 2.0.0.

Is there a fix for CVE-2026-5807?

A patch was published on 2026-04-17: Fixed in version 2.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-5807 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-5807?

Check whether you run github.com/hashicorp/vault (Go), HashiCorp Vault Community Edition or HashiCorp Vault Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5807: HashiCorp Vault denial of service in root token generation and rekeying

Q: Is there a fix for CVE-2026-5807?

A patch was published on 2026-04-17: Fixed in version 2.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-5807 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-5807?

Check whether you run github.com/hashicorp/vault (Go), HashiCorp Vault Community Edition or HashiCorp Vault Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5807 · Severity: high · CVSS 7.5 · Published 2026-04-17

HashiCorp Vault, a tool used for managing sensitive secrets and encryption keys, is vulnerable to a denial-of-service attack. An unauthorized person can repeatedly start or cancel critical administrative tasks, such as generating root tokens or rotating security keys. This blocks legitimate administrators from performing these essential security operations, potentially preventing system recovery or emergency access during a crisis.

Technologies: github.com/hashicorp/vault (Go), HashiCorp Vault Community Edition, HashiCorp Vault Enterprise. Vendors: Go, HashiCorp.

Quick answers

Is CVE-2026-5807 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5807 being exploited in the wild.
How severe is CVE-2026-5807?: High severity, with a CVSS score of 7.5, published 17 April 2026.
Which products and versions are affected?: github.com/hashicorp/vault (Go) <= 1.21.4, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.21.4; HashiCorp Vault Community Edition <= 1.21.4, up to 1.21.4, fixed in 2.0.0; HashiCorp Vault Enterprise <= 1.21.4, 1.20.9, 1.19.15, up to 1.21.4, 1.20.9, and 1.19.15; fixed in 2.0.0.
Is there a fix for CVE-2026-5807?: A patch was published on 2026-04-17: Fixed in version 2.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-5807 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-5807?: Check whether you run github.com/hashicorp/vault (Go), HashiCorp Vault Community Edition or HashiCorp Vault Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

HashiCorp Vault is vulnerable to a Denial of Service (DoS) via resource exhaustion (CWE-770). The vulnerability exists in the 'sys/rekey', 'sys/generate-root', and 'sys/rekey-recovery-key' HTTP endpoints, which were previously unauthenticated. Because Vault only allows a single in-progress operation for these workflows, a remote, unauthenticated attacker can repeatedly initiate or cancel these processes to occupy the operation slot indefinitely. This prevents legitimate operators from completing root token generation or key rotation. The issue is resolved in Vault 2.0.0 by requiring authentication for these endpoints.

Affected products

HashiCorp Vault Community Edition <= 1.21.4
HashiCorp Vault Enterprise <= 1.21.4, 1.20.9, 1.19.15

Identifiers

CVE-2026-5807
GHSA-88v5-9hxc-f85r
GO-2026-5247

Timeline

2026-04-16: disclosed: Initial publication by HashiCorp
2026-04-17: advisory: GitHub and NVD advisories published
2026-04-17: patched: Fixed in version 2.0.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.