CVE-2025-12044: HashiCorp Vault · Unthrottled Resource Allocation
Affects HashiCorp VaultSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 1.21.0 : patch HashiCorp Vault soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.21.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HashiCorp Vault | Affected
| Fixed in– |
AI-suggested
- Immediately upgrade all affected Vault instances to the patched versions: Vault Community Edition 1.21.0 or Enterprise versions 1.16.27, 1.19.11, 1.20.5, or 1.21.0.
- Implement network-level access controls to restrict unauthenticated access to Vault endpoints, such as IP whitelisting, VPNs, or zero trust network segmentation.
- Deploy Web Application Firewalls (WAFs) or API gateways capable of detecting and rate-limiting suspicious JSON payloads to prevent abuse before reaching Vault.
- Monitor Vault server resource utilization and logs for unusual spikes in JSON processing or request rates indicative of exploitation attempts.
- Conduct regular security assessments and penetration testing focused on API abuse and resource exhaustion scenarios.
- Educate DevOps and security teams about this vulnerability and ensure incident response plans include steps for Vault service disruptions.
- Consider implementing additional rate limiting or request throttling mechanisms at the application or infrastructure level to complement Vault’s internal controls.
Description
Vault and Vault Enterprise (“Vault”) are vulnerable to an unauthenticated denial of service when processing JSON payloads. This occurs due to a regression from a previous fix for [+HCSEC-2025-24+|https://discuss.hashicorp.com/t/hcsec-2025-24-vault-denial-of-service-though-complex-json-payloads/76393] which allowed for processing JSON payloads before applying rate limits. This vulnerability, CVE-2025-12044, is fixed in Vault Community Edition 1.21.0 and Vault Enterprise 1.16.27, 1.19.11, 1.20.5, and 1.21.0.