CVE-2024-8185 | Vault Vulnerable to Denial of Service When Processing Raft Join Requests

Vault Community and Vault Enterprise (“Vault”) clusters using Vault’s Integrated Storage backend are vulnerable to a denial-of-service (DoS) attack through memory exhaustion through a Raft cluster join API endpoint . An attacker may send a large volume of requests to the endpoint which may cause Vault to consume excessive system memory resources, potentially leading to a crash of the underlying system and the Vault process itself. This vulnerability, CVE-2024-8185, is fixed in Vault Community 1.18.1 and Vault Enterprise 1.18.1, 1.17.8, and 1.16.12.

Published: 2024-10-31 Last update: 2025-11-13 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-8185 is rated Moderate Risk (56.3/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.81%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-8185

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-10 0.65% 0.81% +0.17%
2 2026-06-09 0.81% 0.65% -0.17%
3 2026-05-24 — 0.81% —

Full EPSS history (33 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-8185

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2024-8185

GitHub Security Advisory for CVE-2024-8185

GHSA-g233-2p4r-3q7v · Severity: high · Ecosystem: go — Hashicorp Vault vulnerable to denial of service through memory exhaustion

OS Trackers for CVE-2024-8185

vendor priority summary link
alpine — CVE-2024-8185: 1 source package rows (vault); 11 state rows across 1 repos (edge-community); fixed 0, open 11. https://security.alpinelinux.org/vuln/CVE-2024-8185
redhat high — https://access.redhat.com/security/cve/CVE-2024-8185
suse high — https://www.suse.com/security/cve/CVE-2024-8185/

Affected software / configurations for CVE-2024-8185

Vendor Product Version Raw CPE
hashicorp vault >= 1.2.0, < 1.16.12 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault >= 1.2.0, < 1.18.1 cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
hashicorp vault >= 1.17.0, < 1.17.8 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault 1.18.0 cpe:2.3:a:hashicorp:vault:1.18.0:*:*:*:enterprise:*:*:*
openbao openbao < 2.0.3 cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*

References for CVE-2024-8185

cvelogic Threat Intelligence