Skip to main content
VulnerabilityPublished Updated

CVE-2025-11374: github.com/hashicorp/consul · Consul key/value endpoint is vulnerable to denial of service

Affects github.com/hashicorp/consulSource GCVE Database

0
Compare
Authoritative record:CVE-2025-11374· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.22.0 when convenient.

Data as of 4 Nov 2026, 18:23 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.22.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 4 Nov 2026.

What to do

Upgrade github.com/hashicorp/consul to 1.22.0.

Affected software

ProductAffectedFixed in
Gogithub.com/hashicorp/consulAffected
  • <1.22.0
Fixed in
  • 1.22.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches provided by HashiCorp by upgrading to Consul Community Edition 1.22.0 or Consul Enterprise versions 1.22.0, 1.21.6, 1.20.8, or 1.18.12. Since a patch is available, remediation should be performed promptly to prevent potential denial of service.

Description

A denial of service (DoS) vulnerability exists in the key/value endpoint of Consul and Consul Enterprise due to improper validation of the Content Length header. This flaw, tracked as CVE-2025-11374, allows an attacker with low privileges to cause service disruption. The issue is resolved in Consul Community Edition 1.22.0 and Consul Enterprise versions 1.22.0, 1.21.6, 1.20.8, and 1.18.12.

References

Community reviews

Loading reviews…