The Wire · Showcase
CONSUL PATCHES 8 CVE CHAINS, K8S FIXES FALSE FIPS WARNINGS
By RepoJournal · Filed · About HashiCorp
Consul upgraded Go 1.26.3 to close eight chained CVEs in the standard library overnight, while consul-k8s 1.8.x stops firing misleading FIPS compliance warnings on every pod startup.
Consul patched eight Go CVEs [1] by upgrading to toolchain 1.26.3 and golang.org/x/net 0.53.0, blocking chains in the standard library that could affect service mesh stability. Meanwhile, consul-k8s [2] fixed a three-bug cascade in the FIPS version check that was spamming logs with false warnings—the original code hit a non-existent API endpoint, passed nil context, and had a missing else guard that fired warnings unconditionally [3]. Both fixes ship quietly but matter: one secures the foundation, the other stops noise that masks real FIPS compliance issues. On the docs side, Nomad 2.0.1 release notes are live [4] with new scheduler parameters, and Vault's MSSQL EKM provider backfilled a missing v0.3.2 bug fix entry [5] documenting a version reporting issue that could confuse SQL Server integrations.
Action items
- → Pull Consul with Go 1.26.3 toolchain into your next deploy hashicorp/consul [immediate]
- → Upgrade consul-k8s to 1.8.9+ if running FIPS builds to stop false warning spam hashicorp/consul-k8s [plan]
- → Review Nomad 2.0.1 release notes for scheduler parameter changes hashicorp/web-unified-docs [plan]
References
- [1] updating golang.org/x/net and toolchain version ↗ hashicorp/consul
- [2] fix: correct FIPS Consul version check in connect-init (CSL-13179) (#5252) hashicorp/consul-k8s
- [3] fix: correct FIPS Consul version check in connect-init (CSL-13179) ↗ hashicorp/consul-k8s
- [4] [PUBLISH] nomad/2.0.1 ↗ hashicorp/web-unified-docs
- [5] docs(mssql): add missing v0.3.2 release note for version reporting fix (#2411) hashicorp/web-unified-docs
FAQ
- What changed in HashiCorp on May 13, 2026?
- Consul upgraded Go 1.26.3 to close eight chained CVEs in the standard library overnight, while consul-k8s 1.8.x stops firing misleading FIPS compliance warnings on every pod startup.
- What should HashiCorp teams do about it?
- Pull Consul with Go 1.26.3 toolchain into your next deploy • Upgrade consul-k8s to 1.8.9+ if running FIPS builds to stop false warning spam • Review Nomad 2.0.1 release notes for scheduler parameter changes
- Which HashiCorp repositories shipped on May 13, 2026?
- hashicorp/consul, hashicorp/consul-k8s, hashicorp/web-unified-docs