Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-19014

consul: Consul: Denial of Service via uncontrolled resource consumption in Connect authorization endpoint

Overview

Published
7 Aug 2026
Modified
28 Aug 2026
Medium CVE
1 Registry packages
5 OS packages
3 Linux distributions
Yes Fix available

Description

Consul Community Edition and Consul Enterprise 1.17.0 through 2.0.2 are vulnerable to an uncontrolled resource consumption issue in the Connect authorization endpoint that may allow a caller to grow the agent's intention-match cache without bound, defeating the operator's cache-disable configuration. This vulnerability, CVE-2026-190124, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

Source: OX vulnerability database

Severity

4.3 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

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

Weakness: CWE-770

Affected packages · 1

Packages affected by CVE-2026-19014
EcosystemPackageVulnerableFixed in
Bitnami consul >=1.17.0, <2.0.3 2.0.3

Open a package to see all its vulnerabilities.

Operating systems · 4 fixes

chainguard 1 release · 2 packages

fixed 2
consul-fips-2-0 consul-2-0
chainguard fixes for CVE-2026-19014
ReleasePackageFixed in
consul-fips-2-0 2.0.3-r0
consul-2-0 2.0.4-r0

debian 1 release · 1 package

affected 1
consul
debian fixes for CVE-2026-19014
ReleasePackageFixed in
11 consul affected

minimos 1 release · 1 package

fixed 1
consul-2
minimos fixes for CVE-2026-19014
ReleasePackageFixed in
consul-2 +1 2.0.3-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.