The Wire · Showcase
CONSUL AND DATAPLANE 2.0 SHIP WITH CRITICAL CRYPTO PATCHES
By RepoJournal · Filed · About HashiCorp
HashiCorp shipped major versions across Consul, Consul-K8s, and Consul Dataplane overnight, all patching the same cryptographic vulnerabilities that hit the Go ecosystem this spring.
Consul v2.0.0 [2] and Consul Dataplane v2.0.0 [1] both land with mandatory upgrades to golang.org/x/crypto and golang.org/x/net, closing the CVEs that forced every Go shop to scramble weeks ago. Consul-K8s follows suit [3] with the same dependency chain remediation across all modules, replacing go-jose/v3 with v4 to fix GHSA-c5q2-7r4c-mv6g. The dataplane release also bumps the UBI base image to 9.8 [1] and suppresses spurious OSV scanner false positives in RHEL RPM paths [4], which matters if you're running supply chain scanning in production. On the breaking changes front: Consul 2.0 increases default HTTP timeouts from 30 seconds to 15 minutes [2], a significant shift for long-polling blocking queries that could affect your connection pooling assumptions. Envoy gets pinned to 1.37.2 and Go to 1.26 [2], so you're looking at a coordinated upgrade across your entire service mesh.
Action items
- → Upgrade Consul to 2.0.0 before next deploy - blocking query timeouts changed hashicorp/consul [immediate]
- → Patch Consul Dataplane to 2.0.0 in all environments hashicorp/consul-dataplane [immediate]
- → Update Consul-K8s controllers to pick up crypto patches hashicorp/consul-k8s [immediate]
- → Verify Envoy sidecar compatibility with 1.37.2 in staging hashicorp/consul [plan]
References
- [1] v2.0.0 ↗ hashicorp/consul-dataplane
- [2] v2.0.0 ↗ hashicorp/consul
- [3] deps: upgrade dependencies to address CVEs in golang.org/x/crypto and golang.org/x/net ↗ hashicorp/consul-k8s
- [4] chore: suppress OSV scanner false positives for UBI base RPM paths ↗ hashicorp/consul-dataplane
FAQ
- What changed in HashiCorp on May 24, 2026?
- HashiCorp shipped major versions across Consul, Consul-K8s, and Consul Dataplane overnight, all patching the same cryptographic vulnerabilities that hit the Go ecosystem this spring.
- What should HashiCorp teams do about it?
- Upgrade Consul to 2.0.0 before next deploy - blocking query timeouts changed • Patch Consul Dataplane to 2.0.0 in all environments • Update Consul-K8s controllers to pick up crypto patches
- Which HashiCorp repositories shipped on May 24, 2026?
- hashicorp/consul-dataplane, hashicorp/consul, hashicorp/consul-k8s