CVE-2026-3605: An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secr

Routine

HIGH 8.1UPGRADE

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

An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secrets they were not authorized to read or write, resulting in denial-of-service. This vulnerability did not allow a malicious user to delete secrets across namespaces, nor read any secret data. Fxed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 69%)
CISA exploited list	No
Weakness	CWE-288, CWE-639
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 04:16 UTCPublished CVE record published
2026-10-26 22:10 UTCUpdated Record last modified

hashicorp vault UPGRADE

Affected: >= 0.10.0 and < 1.19.16 · >= 0.10.0 and < 2.0.0 · >= 1.20.0 and < 1.20.10 · >= 1.21.0 and < 1.21.5

Fixed in: 1.19.16, 1.20.10, 1.21.5, 2.0.0

Safe to downgrade to: a release before 0.10.0

1. Check installed version

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

2. UPGRADE to 1.19.16 (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.

3. If no update is available yet, DOWNGRADE to a release before 0.10.0 (Debian / Ubuntu)

apt-cache madison vault sudo apt install vault=<VERSION_BEFORE_0.10.0> sudo apt-mark hold vault

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vault sudo dnf downgrade vault-<VERSION_BEFORE_0.10.0> sudo dnf versionlock add vault

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-3605?

vault: upgrade to 1.19.16, 1.20.10, 1.21.5, 2.0.0. Exact commands for each OS are on this page.

Is CVE-2026-3605 being exploited?

CVE-2026-3605 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-3605 affect?

CVE-2026-3605 affects vault. Severity is high (CVSS 8.1). An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secrets they were not authorized to read or write, resulting in denial-of-service. This vulnerability did not allow a malicious user t

How urgent is CVE-2026-3605?

Priority 36/100. High severity

Software pages

HashiCorp Vault vulnerabilities

Related CVEs

CVE-2026-5807 HIGH 7.5 UPGRADE Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate
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