# CVE-2026-5807: Vault Vulnerable to Denial-of-Service via Unauthenticated Root Token Generation/Rekey Operations

> Unauthenticated attackers can cause denial of service by repeatedly initiating root token generation or rekey operations, blocking legitimate administrative workflows.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** BIT-vault-2026-5807, GHSA-88v5-9hxc-f85r, GO-2026-5247, MINI-86jq-h5x3-vvgv, MINI-p83p-xp6j-6p9w

## What is CVE-2026-5807?

CVE-2026-5807 is a high-severity denial of service vulnerability in Hashicorp Vault, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-5807?

4 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/vault` | Go | All versions | None |
| `github.com/hashicorp/vault` | Go | All versions to 1.21.4 | None |
| `github.com/hashicorp/vault` | Go | All versions to 1.21.4 | None |
| `vault` | Bitnami | From 0.10.0 | 2.0.0 |

Products: Hashicorp Vault.

## How do I fix CVE-2026-5807?

Upgrade to a fixed version.

## Is CVE-2026-5807 being exploited?

There is no known exploitation of CVE-2026-5807 in the wild and no public exploit code.

## Other vulnerabilities in Hashicorp Vault

- [CVE-2020-35192](https://insights.sbomify.com/CVE-2020-35192/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-12757](https://insights.sbomify.com/CVE-2020-12757/): Improper Input Validation in HashiCorp Vault (critical 9.8)
- [CVE-2025-6000](https://insights.sbomify.com/CVE-2025-6000/): Arbitrary Remote Code Execution via Plugin Catalog Abuse (critical 9.1)
- [CVE-2022-40186](https://insights.sbomify.com/CVE-2022-40186/): HashiCorp Vault vulnerable to incorrect metadata access (critical 9.1)
- [CVE-2022-36129](https://insights.sbomify.com/CVE-2022-36129/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5807 and fix it if it is affected.

What it is: CVE-2026-5807 is a high-severity denial of service vulnerability in Hashicorp Vault, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5807 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/vault (Go): affected all versions; no fix listed
- github.com/hashicorp/vault (Go): affected all versions up to 1.21.4; no fix listed
- github.com/hashicorp/vault (Go): affected all versions up to 1.21.4; no fix listed
- vault (Bitnami): affected from 0.10.0; fixed in 2.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5807/ (Markdown: https://insights.sbomify.com/CVE-2026-5807/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5807
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5807
- OSV: https://osv.dev/vulnerability/CVE-2026-5807

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5807/
Summaries are generated and may contain mistakes; the official description above is the record.