Quick answers
- Is CVE-2026-105626 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105626 being exploited in the wild.
- How severe is CVE-2026-105626?
- High severity, with a CVSS score of 7.5, published 26 October 2026.
- Which products and versions are affected?
- HashiCorp Consul up to 2.0.4; HashiCorp Consul Enterprise up to 2.0.4 (Enterprise track); 1.21.18 and earlier (1.21.x track).
- Is there a fix for CVE-2026-105626?
- Yes: fixed in Consul 2.1.0, Consul Enterprise 2.1.0 and 1.21.19. Until then: Restrict network access to the HTTP API using firewall rules or network segmentation to limit exposure to trusted clients only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105626 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-105626?
- Check whether you run HashiCorp Consul or HashiCorp Consul Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Consul 2.1.0, Consul Enterprise 2.1.0 and 1.21.19
Restrict network access to the HTTP API using firewall rules or network segmentation to limit exposure to trusted clients only.
Technical details
Several HTTP API endpoints read and decode the entire request body into memory without size limits before evaluating ACL permissions. An attacker can send arbitrarily large payloads to endpoints that do not require authentication, causing excessive memory consumption and potential out-of-memory conditions. The fix introduces a 512 KiB request body size limit on write endpoints.
Affected products
- HashiCorp Consul up to 2.0.4
- HashiCorp Consul Enterprise up to 2.0.4 (Enterprise track); 1.21.18 and earlier (1.21.x track)
Timeline
- 2026-10-26: disclosed