Vault KVv2 Metadata and Secret Deletion Policy Bypass Denial-of-Service
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: HashiCorp Vault 2.0.0; HashiCorp Vault Enterprise 1.19.16, 1.20.10, 1.21.5.
Low priority for now. Upgrade to HashiCorp Vault 2.0.0; HashiCorp Vault Enterprise 1.19.16, 1.20.10, 1.21.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 17, 2026
- Updated
- Jul 15, 2026
- EPSS
- 0.5% · 41th percentile
- CWE
- CWE-288
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · HashiCorp
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hashicorp | vault | cpe:2.3:a:hashicorp:vault |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hashicorp vault0.10.0 and later · before 1.19.16
- hashicorp vault0.10.0 and later · before 2.0.0
- hashicorp vault1.20.0 and later · before 1.20.10
- hashicorp vault1.21.0 and later · before 1.21.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.
HashiCorp Vault
- 0.10.0 and later · before 2.0.0affected · semver
HashiCorp Vault Enterprise
- 0.10.0 and later · before 2.0.0affected · semverfixed in 1.19.16, 1.20.10, 1.21.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/hashicorp/vault | from 0.10.0 · up to and including 1.21.4 | — |
| Go | github.com/hashicorp/vault | from 0.10.0 | — |
| openSUSE:Tumbleweed | openbao | before 2.5.3-1.1 | 2.5.3-1.1 |
Same product
hashicorp: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-35192The official vault docker images before 0.11.6 contain a blank password for a root user.40Plan
- CVE-2024-2048Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates39Monitor
- CVE-2020-12757HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials 39Monitor
- CVE-2025-6000Arbitrary Remote Code Execution via Plugin Catalog Abuse36Monitor
- CVE-2022-40186An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3.36Monitor
- CVE-2022-36129HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an unauthenticated API endpoint 36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| HashiCorp Vault | 2.0.0 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.19.16 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.20.10 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.21.5 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 2.0.0 | Vendor (CNA) |
| opensuse:openbao | 2.5.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- chungkn from OneMount Group, as well as Andy RUSSON et Gabriel DEPARTOUTalmond.eu , sponsored the ANSSI (French Cybersecurity Agency) open
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-11621176 days apartVault AWS auth method bypass due to AWS client cache32Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-105816173 days apartVault Vulnerable to Arbitrary Code Execution via Plugin Catalog Entries Restored From Raft Snapshots32Monitor
- CVE-2026-505175 days apartAudit Log Plugin Directory Guard Bypass via Legacy path Option17Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-288 · Authentication Bypass Using an Alternate Path or ChannelCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.