VulnerabilityPublished 28 Aug 2025Updated 23 Oct 2025

CVE-2025-6203: HashiCorp Vault · Unthrottled Resource Allocation

Affects HashiCorp VaultSource CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 1.20.3 : patch HashiCorp Vault soon.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.20.3

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Aug 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
HashiCorp Vault	Affected =1.15.0	Fixed in–

AI-suggested

Immediate patching: Upgrade all affected Vault instances to the fixed versions—Community Edition 1.20.3 or Enterprise Editions 1.20.3, 1.19.9, 1.18.14, or 1.16.25.
Implement resource monitoring: Deploy monitoring tools to track CPU and memory usage of Vault servers in real time to detect abnormal spikes indicative of exploitation attempts.
Configure request throttling: Where possible, apply rate limiting or throttling on incoming Vault requests to prevent resource exhaustion from complex payloads.
Network segmentation: Restrict Vault access to trusted networks and clients to reduce exposure to unauthenticated remote attacks.
Audit logging and alerting: Enhance audit log monitoring to detect unusual request patterns or timeouts in Vault’s auditing subroutine.
Incident response readiness: Prepare response plans for potential Vault unavailability, including fallback secrets management or manual overrides.
Vendor communication: Stay updated with HashiCorp advisories for any additional patches or mitigations.
Test patches in staging environments before production deployment to ensure stability.

Description

A malicious user may submit a specially-crafted complex payload that otherwise meets the default request size limit which results in excessive memory and CPU consumption of Vault. This may lead to a timeout in Vault’s auditing subroutine, potentially resulting in the Vault server to become unresponsive. This vulnerability, CVE-2025-6203, is fixed in Vault Community Edition 1.20.3 and Vault Enterprise 1.20.3, 1.19.9, 1.18.14, and 1.16.25.

Impact

For European organizations, the primary impact of CVE-2025-6203 is the potential denial of service of HashiCorp Vault servers, which can disrupt access to critical secrets and credentials necessary for secure operations. This can halt automated deployment pipelines, cloud infrastructure provisioning, and application authentication processes that depend on Vault, leading to operational downtime and increased risk exposure. Since Vault is integral to many DevOps and cloud-native environments, unavailability can cascade into broader service outages or security lapses. The vulnerability does not compromise data confidentiality or integrity but severely affects availability, which is critical for business continuity. Organizations in sectors such as finance, healthcare, and critical infrastructure that rely heavily on Vault for secrets management may face significant operational and reputational risks. Additionally, the lack of authentication requirement for exploitation increases the risk of opportunistic attacks from external threat actors. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as exploit techniques may emerge. European entities with automated security compliance and auditing processes dependent on Vault’s availability are particularly vulnerable to disruptions caused by this flaw.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

discuss.hashicorp.com/t/hcsec-2025-24-vault-denial-of-service-though-complex-json-payloads/76393 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Oct 2025, 18:44 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats