CVE-2025-11374
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedConsul and Consul Enterprise’s (“Consul”) key/value endpoint is vulnerable to denial of service (DoS) due to incorrect Content Length header validation. This vulnerability, CVE-2025-11374, is fixed in Consul Community Edition 1.22.0 and Consul Enterprise 1.22.0, 1.21.6, 1.20.8 and 1.18.12.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceConsul and Consul Enterprise's key/value endpoint is vulnerable to denial of service due to incorrect Content-Length header validation. Attackers can send specially crafted requests with malformed Content-Length headers to cause service disruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.18.12< 1.22.0>= 1.19.0, < 1.20.8>= 1.21.0, < 1.21.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Consul versionRun 'consul version' on the Consul server or agentAffected if Version is < 1.18.12 OR >= 1.19.0 AND < 1.20.8 OR >= 1.21.0 AND < 1.21.6 OR >= 1.22.0 AND < 1.22.0 (in other words, not 1.18.12+, 1.20.8+, 1.21.6+, or 1.22.0+)
-
Identify if key/value endpoint is in useCheck if Consul KV is enabled by running 'consul kv -http-addr=<addr> _' or reviewing agent configuration for 'disable_update_check' or similar KV-related settingsAffected if KV endpoint is accessible (most default Consul installations have KV enabled)
-
Verify HTTP API exposureReview network exposure of Consul API ports (default 8500) using 'netstat -tlnp | grep 8500' or checking firewall rulesAffected if KV endpoint HTTP API is reachable over network
You are affected if your Consul version falls within the vulnerable ranges AND the KV endpoint is accessible via HTTP API.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.18.121.20.81.21.6
Upgrade Consul to version 1.22.0 (Community) or one of the fixed Enterprise versions (1.22.0, 1.21.6, 1.20.8, or 1.18.12).
Consul 1.22.0 (latest stable) or 1.21.6/1.20.8/1.18.12 based on current major version
- 1. Identify your current Consul version using `consul version`
- 2. Determine which patch version branch you should upgrade to based on your current major version
- 3. For Consul >= 1.22.0: already fixed
- 4. For Consul 1.21.x: upgrade to 1.21.6 or later
- 5. For Consul 1.20.x: upgrade to 1.20.8 or later
- 6. For Consul 1.18.x: upgrade to 1.18.12 or later
- 7. Download the appropriate version from https://www.consul.io/downloads
- 8. Follow standard Consul upgrade procedures: https://developer.hashicorp.com/consul/docs/upgrading
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11374 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data