CVE-2026-19113

Unauthenticated denial of service via unbounded request body processing

Published Aug 7, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Consul Community Edition and Consul Enterprise 1.3.0 through 2.0.2 are vulnerable to an unauthenticated denial of service in several agent HTTP API endpoints. A remote caller could cause the agent to consume substantial memory before the request was rejected. This vulnerability, CVE-2026-19113, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

Analysis

AI-generated

Technical impact

Consul Community Edition and Consul Enterprise versions 1.3.0 through 2.0.2 contain an unauthenticated denial‑of‑service vulnerability that manifests when certain agent HTTP API endpoints process request bodies without enforcing size limits. By sending a request with an unbounded body, a remote attacker can cause the agent to allocate a large amount of memory before the request is rejected, leading to resource exhaustion and potential service disruption. The weakness is a memory‑management failure (CWE‑400) that also demonstrates improper resource allocation limits (CWE‑770).

Affected Systems

The vulnerability affects HashiCorp Consul Community Edition and Consul Enterprise. All releases from 1.3.0 to 2.0.2 are vulnerable; the bug is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

Risk and Exploitability

The CVSS score of 5.3 reflects a moderate severity due to the lack of authentication requirement, but the impact is limited to service availability rather than data compromise. The EPSS score indicates a very low likelihood of exploitation, approximately 0.3% (less than 1%). The vulnerability is not listed in CISA KEV. The likely attack vector is remote unauthenticated traffic targeting the agent HTTP API, with the attacker provoking memory consumption via specially crafted request bodies. Successful exploitation would result in denial of service on the target node, potentially cascading to cluster disruption if multiple agents are affected.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Consul 2.0.3 or Consul Enterprise 1.21.17, 1.22.11, or 2.0.3, where the request‑size limits have been restored.
  • If an upgrade is not immediately possible, restrict access to the agent HTTP API endpoints so that only trusted hosts can send requests, preventing unauthenticated actors from abusing the flaw.
  • Continuously monitor agent memory usage and enforce operational limits; implement rate‑limiting or hard‑timeout controls on request processing to mitigate accidental overload.

Generated by OpenCVE AI on August 14, 2026 at 02:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Hashicorp
Hashicorp consul
Hashicorp consul Enterprise
Vendors & Products Hashicorp
Hashicorp consul
Hashicorp consul Enterprise
Type Values Removed Values Added
Description Consul Community Edition and Consul Enterprise 1.3.0 through 2.0.2 are vulnerable to an unauthenticated denial of service in several agent HTTP API endpoints. A remote caller could cause the agent to consume substantial memory before the request was rejected. This vulnerability, CVE-2026-19113, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.
Title Unauthenticated denial of service via unbounded request body processing
Weaknesses CWE-400
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
HashiCorp
Published
Updated
Aug 10, 2026, 6:24 PM
Reserved
Aug 6, 2026, 2:10 PM
Status
Awaiting Analysis
Published
Aug 7, 2026, 8:16 PM
Modified
Aug 28, 2026, 3:47 PM
Severity
Important
Public date
Aug 7, 2026, 7:20 PM