LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3605: Vault KVv2 Metadata and Secret Deletion Policy Bypass Denial-of-Service

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.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-3605 lets an authenticated Vault user with certain glob-based KVv2 policy access delete secrets they should not be able to read or write. The issue is denial-of-service focused: sources state it does not expose secret values and does not cross namespaces. It is fixed in specified Vault releases.

Executive priority

Treat as high priority for Vault environments because it can disrupt applications by deleting secrets. Prioritize upgrades where KVv2 and broad glob policies are used. Business risk is service disruption, not direct credential disclosure, according to the supplied sources.

Technical view

The flaw is a Vault KVv2 metadata and secret deletion policy bypass involving glob policies. A low-privileged authenticated user may delete unauthorized secrets, affecting integrity and availability, with CVSS 3.1 score 8.1. Sources map it to CWE-288 and CWE-639. Fixed versions are Vault CE 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

Likely exposure

Exposure is most likely where HashiCorp Vault KVv2 is used with policies containing glob patterns and users have authenticated access to matching paths. The provided affected-version metadata is incomplete, so validate against the HashiCorp advisory and installed Vault version.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. Exploitation requires authenticated Vault access and a relevant KVv2 policy shape. The impact is unauthorized deletion, not secret disclosure, based on the provided advisory text.

Researcher notes

Do not assume broad compromise. The evidence supports an authenticated authorization bypass limited to KVv2 deletion behavior, with no namespace crossing and no secret read. Affected range details in the bundle are sparse; use vendor advisories to confirm exact product status.

Mitigation direction

  • Upgrade Vault CE to 2.0.0 or later if applicable.
  • Upgrade Vault Enterprise to 2.0.0, 1.21.5, 1.20.10, or 1.19.16.
  • Review KVv2 policies using glob patterns and narrow access where feasible.
  • Check HashiCorp guidance for any version-specific operational instructions.
  • Restore deleted secrets from approved backups if impact is found.

Validation and detection

  • Inventory Vault CE and Enterprise versions across all environments.
  • Identify KVv2 mounts and policies containing glob patterns.
  • Confirm users with KVv2 path access cannot delete unauthorized secrets after upgrade.
  • Review Vault audit logs for unexpected KVv2 metadata or secret deletion events.
  • Verify backups and recovery procedures for affected secret paths.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3605 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H2.85.2HashiCorp
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H2.85.2redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-3605Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPVault: Vault: Denial of Service due to unauthorized secret deletion via policy bypass
other:Red Hat severity ratingcvssV3_1
  • 2026-04-17T04:01:18.559Z: Reported to Red Hat.
  • 2026-04-17T02:44:42.032Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HashiCorpVault0.10.0unaffected
HashiCorpVault Enterprise0.10.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.