What hashicorp/consul shipped
Written by FoxPlug from the repository's own releases; not affiliated with Consul. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/hashicorp/consul; Consul did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 26, 2026
What shipped
- Fixed an XSS issue where an invalid
max_stalevalue was echoed back in a 400 error and could be rendered by the browser when a Content-Type header was set throughhttp_config.response_headers. Pull request #24071 - Backported the XSS fix for the
max_staleerror response into the 2.1.x release branch. Pull request #24088 - Updated security-related dependencies including follow-redirects, markdown-it, body-parser, fast-uri and qs. Pull request #24080
- Backported the security dependency updates into the 2.1.x release branch. Pull request #24087
- Updated the security scan workflow to fail when CVEs are detected, honor suppressed vulnerabilities via the security-scan.hcl config, and list CVEs in a readable format. Pull request #23972
- Backported the security scan workflow update into the 2.1.x release branch. Pull request #24079
- Opened the post release pull request for 2.1. Pull request #24072
- Opened the post release pull request for 2.1.x. Pull request #24073
Why it matters
This week brought a fix for an XSS issue in the max_stale error response, along with updated security-related dependencies. It also tightened the security scan workflow so detected CVEs cause a failure and suppressed vulnerabilities are honored through config. These changes were backported to 2.1.x, so users on that branch get the same fixes.
Changelog entry
- Fixed an XSS issue where an invalid
max_stalevalue was echoed in a 400 error without an explicit Content-Type. Pull request #24071 - Backported the
max_staleXSS fix to release/2.1.x. Pull request #24088 - Updated security-related dependencies: follow-redirects, markdown-it, body-parser, fast-uri and qs. Pull request #24080
- Backported the security dependency updates to release/2.1.x. Pull request #24087
- Security scan workflow now fails on detected CVEs, uses security-scan.hcl for suppressed vulnerabilities, and lists CVEs readably. Pull request #23972
- Backported the security scan workflow update to release/2.1.x. Pull request #24079
- Post release pull request for 2.1. Pull request #24072
- Post release pull request for 2.1.x. Pull request #24073
This week: fixed an XSS issue in the max_stale error response, updated security-related dependencies, and made the security scan workflow fail on detected CVEs while honoring suppressed vulnerabilities in config. The fixes were backported to 2.1.x.
This week in Consul: an XSS issue was fixed where an invalid max_stale value was echoed back in a 400 error and could be rendered by the browser when a Content-Type was set through http_config.response_headers. Security-related dependencies including follow-redirects, markdown-it, body-parser, fast-uri and qs were updated. The security scan workflow now fails when CVEs are detected, honors suppressed vulnerabilities from security-scan.hcl, and lists CVEs in a readable format. The XSS fix, dependency updates and workflow change were all backported to the 2.1.x release branch.
Week of October 19, 2026
What shipped
- Catalog writes on the leader are now serialized with node write locks so authorization and Raft apply happen atomically. Pull request #24062
- Every leaf certificate request is now authorized, preventing unauthenticated cached requests. Pull request #24063
- Version 2.1.0 was released, including an Enterprise-only 512 KiB default limit on agent HTTP API request bodies that returns HTTP 413 for oversized requests. Release
- The maximum supported Envoy version was reverted from 1.39.4 to 1.39.1 to match the build that consul-dataplane 2.1.0 ships. Pull request #24057
- The envoyextensions submodule moved to v0.11.1 and troubleshoot moved to v0.10.1. Pull request #24060
- Pull request merges are now gated on at least 90 percent patch coverage for new or changed Go code. Pull request #23692
- The leaf certificate authorization change was backported to release/2.1.x. Pull request #24066
- The node write lock change for serialized catalog writes was backported to release/2.1.x. Pull request #24065
- The root hashicorp/consul module dependency was removed from test modules on release/2.1.x to address CVE-2026-15972. Pull request #24045
- A changelog entry was added for Consul Enterprise 1.21.19. Pull request #24059
Why it matters
This week brings the 2.1.0 release together with changes to how catalog writes and leaf certificate requests are authorized, and Envoy support is adjusted to match what consul-dataplane 2.1.0 ships. Test modules also drop the root module dependency for a security fix, and merges now require at least 90 percent patch coverage.
Changelog entry
- Release 2.1.0, with Enterprise agent HTTP API request bodies limited to 512 KiB by default and HTTP 413 returned for oversized requests. Release
- Serialize ACL-vetted catalog writes on the leader with node write locks. Pull request #24062
- Authorize every leaf certificate request to prevent unauthenticated cached requests. Pull request #24063
- Revert the maximum supported Envoy version from 1.39.4 to 1.39.1. Pull request #24057
- Update envoyextensions to v0.11.1 and troubleshoot to v0.10.1. Pull request #24060
- Gate pull request merges on at least 90 percent patch coverage for new or changed Go code. Pull request #23692
- Remove the root module dependency from test modules to address CVE-2026-15972. Pull request #24045
- Add Consul Enterprise 1.21.19 changelog. Pull request #24059
- Update version and changelog. Pull request #24067
- Release api/v1.35.0. Release
- Release sdk/v0.19.0. Release
- Release proto-public/v0.9.0. Release
Consul 2.1.0 is out. Catalog writes are serialized with node write locks, every leaf cert request is authorized, and patch coverage of 90 percent is now required to merge PRs. Max supported Envoy is back to 1.39.1.
Consul 2.1.0 shipped this week. Catalog writes on the leader are now serialized with node write locks so authorization and Raft apply stay atomic, and every leaf certificate request is authorized to block unauthenticated cached requests. Pull request merges are now gated on at least 90 percent patch coverage for new or changed Go code. The maximum supported Envoy version was reverted to 1.39.1 to match consul-dataplane 2.1.0, and the envoyextensions and troubleshoot submodules were updated. Test modules no longer depend on the root module, addressing CVE-2026-15972.
Week of October 12, 2026
What shipped
- Released Consul 2.1.0-rc2, which upgrades Go to 1.26.9 for security fixes and upgrades raft-wal to v0.5.0, removing the dependency on github.com/coreos/etcd. Release
- Removed the root hashicorp/consul dependency from test modules to address CVE-2026-15972, an unauthenticated denial of service on external gRPC listeners. Pull request #24043
- Upgraded Go from 1.26.7 to 1.26.9 to address Go standard library vulnerabilities reported by the binary and container scanning workflow. Pull request #24010
- Upgraded go-discover from v1.2.0 to v1.5.0 so go.mod no longer pulls in the archived github.com/hashicorp/vic module. Pull request #24021
- Added shared OIDC RP-Initiated logout plumbing so logging out of Consul can also end the user's identity provider session. Pull request #23739
- Fixed a WatchSet concurrency issue in the API gateway reconciler where AddTrigger updated the WatchSet while ReadDiscoveryChainConfigEntries was iterating over it. Pull request #24018
- Updated the compatibility test matrix for Nomad CE, Vault CE and Envoy versions. Pull request #24019
- Changed the UI to render tab content inside the tab panels and keep focus on activated tabs. Pull request #24013
- Added the 2.1.0-rc2 section to the changelog. Pull request #24030
- Prepared the 2.1.0-rc2 release branch by bumping the version file and prepending the changelog entry. Pull request #24014
Why it matters
This week's release candidate brings security fixes to the Go toolchain and a raft-wal upgrade that drops the etcd dependency, and it also closes an unauthenticated denial of service on external gRPC listeners. Alongside that, dependency and OIDC logout work make the project easier to scan and give logouts a cleaner path to ending identity provider sessions.
Changelog entry
- Release 2.1.0-rc2 (October 12, 2026): upgrade Go to 1.26.9 to address security vulnerabilities, and upgrade raft-wal to v0.5.0, removing the dependency on github.com/coreos/etcd. Release
- Security: remove root hashicorp/consul dependency from test modules to address CVE-2026-15972. Pull request #24043
- Deps: upgrade Go from 1.26.7 to 1.26.9 for Go standard library vulnerabilities. Pull request #24010
- Deps: upgrade go-discover to v1.5.0 to drop the archived hashicorp/vic module. Pull request #24021
- Oidc: add shared RP-Initiated IdP logout plumbing. Pull request #23739
- Fix WatchSet concurrency issue in apiGatewayReconciler reconcileRoute. Pull request #24018
- Update compatibility test matrix for Nomad, Vault and Envoy versions. Pull request #24019
- Ui: render tab content inside tab panels and keep focus on activated tabs. Pull request #24013
- Add 2.1.0-rc2 section to the changelog. Pull request #24030
- Prepare release 2.1.0-rc2. Pull request #24014
Consul 2.1.0-rc2 is out: Go 1.26.9 for security fixes, raft-wal v0.5.0 drops the etcd dependency. Also this week: CVE-2026-15972 fixed by removing the root module from test modules, go-discover v1.5.0, and OIDC RP-Initiated logout plumbing.
Consul 2.1.0-rc2 is available. It upgrades Go to 1.26.9 to address standard library vulnerabilities and moves raft-wal to v0.5.0 with raft, serf, memberlist and go-metrics updates, removing the dependency on github.com/coreos/etcd. Other work this week: test modules no longer depend on the root hashicorp/consul module, closing CVE-2026-15972, an unauthenticated denial of service on external gRPC listeners; go-discover moves to v1.5.0 so go.mod no longer requires the archived hashicorp/vic; and OIDC RP-Initiated logout plumbing lets logging out of Consul also end the identity provider session. A WatchSet concurrency issue in the API gateway reconciler was also fixed, and the UI now renders tab content inside tab panels.
Week of October 5, 2026
What shipped
- Fixed two independent watch leaks in agent/proxycfg that left goroutines and blocking queries running with nothing consuming their updates, causing server goroutine count and memory to keep growing. Pull request #23990
- Fixed four correctness bugs in API Gateway found during end-to-end testing of DNS auto-registration, covering DNS lookups, routing, and upstream limits on both agentless and agentful deployments. Pull request #23936
- Added feature gate retrieval and modification through RPCs and enhanced authorization checks to allow node-specific access based on ACL identities. Pull request #23975
- Clarified that agentful API gateways always enable upstream routing regardless of feature gate status, with the feature gate applying only to agentless gateways. Pull request #23976
- Added a Content-Security-Policy header to Consul UI responses to mitigate XSS and data injection attacks. Pull request #23971
- Restored dependency metrics in release artifacts so official release binaries send Raft, Serf, and Memberlist metrics to the intended sink. Pull request #23813
- Added 2.1 and dropped 1.22 in the active versions manifest so the backport assistant can backport to release/2.1.x. Pull request #23965
- Fixed a shell-quote security vulnerability. Pull request #23973
- Addressed a security vulnerability in the postcss-modules-local-by-default dependency. Pull request #23966
- Fixed a security vulnerability as part of ongoing remediation work. Pull request #23970
Why it matters
This week focused on reliability and security for people running Consul. Watch leaks in proxycfg that grew server goroutine count and memory over time were fixed, four API Gateway correctness bugs affecting DNS, routing, and upstream limits were corrected, and several security vulnerabilities in dependencies were addressed. The UI also gained a Content-Security-Policy header and the active versions manifest was updated so 2.1 backports work.
Changelog entry
- Proxycfg: stop leaking peered upstream health watches and watches of stopped proxy states that left goroutines and blocking queries running Pull request #23990
- Api-gateway: fix four correctness bugs in DNS, routing, and upstream limits affecting agentless and agentful deployments Pull request #23936
- Operator: add feature gate retrieval and modification through RPCs and enhance authorization checks for node-specific access Pull request #23975
- Api-gateway: clarify and enforce that agentful gateways always enable upstream routing regardless of feature gate status Pull request #23976
- Ui: add a Content-Security-Policy header to Consul UI responses to mitigate XSS and data injection attacks Pull request #23971
- Ci: restore dependency metrics in release artifacts so official binaries send Raft, Serf, and Memberlist metrics to the intended sink Pull request #23813
- Release: add 2.1 and drop 1.22 in the active versions manifest so backports to release/2.1.x are recognized Pull request #23965
- Security: fix a shell-quote vulnerability Pull request #23973
- Security: fix a vulnerability in the postcss-modules-local-by-default dependency Pull request #23966
- Security: fix a vulnerability Pull request #23970
- Test: stop envoy peering integration tests from flaking due to CI runner CPU contention and RPC connection pool timeouts Pull request #23983
- Deps: upgrade raft-wal to v0.5.0 so Consul no longer depends on coreos/etcd Pull request #23991
This week: fixed proxycfg watch leaks that grew memory, four API Gateway correctness bugs in DNS and routing, added a CSP header to UI responses, and addressed dependency security vulnerabilities.
This week in Consul: we fixed two independent watch leaks in agent/proxycfg that left goroutines and blocking queries running with nothing consuming their updates, which caused server goroutine count and memory to grow over time. Four API Gateway correctness bugs found during end-to-end DNS auto-registration testing were fixed, covering DNS lookups, routing, and upstream limits on both agentless and agentful deployments. Consul UI responses now include a Content-Security-Policy header to mitigate XSS and data injection attacks. Several dependency security vulnerabilities were addressed, feature gate RPCs were added, and the active versions manifest now includes 2.1 so backports to release/2.1.x can proceed.
Week of September 28, 2026
What shipped
- V2.1.0-rc1 released with breaking change: consul connect redirect-traffic command migrated from iptables/ip6tables to nftables for atomic rule application. Release
- Connect leaf certificates now served over SDS for hitless rotation on sidecar proxies and terminating gateways, eliminating connection termination during certificate rotation. Pull request #23938
- Security vulnerability GHSA-9f6g-j8ch-79g4 in morgan fixed to properly escape double quotes in access-log fields. Pull request #23952
- Security vulnerabilities fixed in morgan and js-yaml dependencies. Pull request #23946
- Envoy peering integration tests stabilized by increasing retry timeouts, wrapping metrics checks in retries, and removing RPC deadline from pooled connections. Pull request #23940
Why it matters
V2.1.0-rc1 is ready for testing with significant improvements to certificate rotation handling that eliminate connection disruption. Security fixes address vulnerabilities in key dependencies. Test stability improvements reduce flakiness in CI.
Changelog entry
- BREAKING: cli: consul connect redirect-traffic migrated from iptables/ip6tables to nftables Release
- Connect: leaf certificates served over SDS for hitless rotation in sidecar proxies and terminating gateways Pull request #23938
- Security: fixed GHSA-9f6g-j8ch-79g4 in morgan dependency Pull request #23952
- Security: fixed vulnerabilities in morgan and js-yaml dependencies Pull request #23946
- Test: improved envoy peering integration test stability with retry timeouts and RPC connection handling Pull request #23940
Consul v2.1.0-rc1 is available. Connect certificates now rotate without dropping connections, and the redirect-traffic command uses nftables for better atomic rule application.
Consul v2.1.0-rc1 brings hitless Connect certificate rotation for sidecar proxies and terminating gateways, so your services stay connected during certificate updates. The consul connect redirect-traffic command now uses nftables for atomic IPv4/IPv6 rule application. Test the RC and share feedback.
Week of September 21, 2026
What shipped
- Migration from iptables to nftables: the sdk/iptables package is replaced with sdk/nftables and all consul core callers are migrated to use the new implementation. Pull request #23785
- SDK v0.19.0-rc1 released with backported inference gateway type surface for consul-k8s compatibility. Release
- Terminating gateway credential injection structs backported to CE so consul-k8s can build against the type surface. Pull request #23939
- Inference gateway type surface backported from Enterprise to CE, including ServiceKindInferenceGateway service kind and config entry kinds. Pull request #23925
- API v1.35.0-rc1 released with updated SDK version. Release
- Envoyextensions v0.11.0-rc1 released with updated api and sdk. Release
- Troubleshoot v0.10.0-rc1 released with updated api, sdk, and envoyextensions. Release
- Peering refactor adds multiport enterprise extension points with shared data shapes and xDS extension points. Pull request #23877
- Feature gating for localized DNS added. Pull request #23934
- Non-consul generated VIP removed from inline table. Pull request #23928
Why it matters
This week includes a significant infrastructure change migrating from iptables to nftables for modern Linux distributions, alongside multiple RC releases of core components. Type surface backports enable consul-k8s to build against Enterprise features while maintaining Community Edition compatibility.
Changelog entry
- Sdk/iptables package replaced with sdk/nftables; all callers migrated to nftables implementation Pull request #23785
- Sdk/v0.19.0-rc1: inference gateway and terminating gateway credential injection type surface added Release
- Api/v1.35.0-rc1: SDK version updated Release
- Envoyextensions/v0.11.0-rc1: api and sdk updated Release
- Troubleshoot/v0.10.0-rc1: api, sdk, and envoyextensions updated Release
- Peering: added multiport enterprise extension points with CE no-op implementations Pull request #23877
- Feature gate added for localized DNS Pull request #23934
- Removed non-consul generated VIP from inline table Pull request #23928
Consul updates: nftables migration, SDK v0.19.0-rc1, API v1.35.0-rc1, and inference gateway type backports for CE.
This week's Consul updates include a major infrastructure shift from iptables to nftables, RC releases for SDK, API, and troubleshoot components, and backports of inference gateway and terminating gateway credential injection type surfaces to Community Edition for consul-k8s compatibility.
Week of September 14, 2026
What shipped
- Consul UI migrated to Helios Design System (HDS) as a combined 16-PR stack rebased onto main. Pull request #23911
- Post-Quantum Cryptography hybrid key exchange support added to Consul Connect Envoy service mesh sidecars and Consul Agent TLS communication. Pull request #23884
- HDS migration regressions fixed in filter bars, health indicators, navigation, service views, and intentions list. Pull request #23924
- HDS design system migration backported to release/2.0.x branch. Pull request #23927
- Release hygiene workflow added to scan PR descriptions and source files for internal Jira ticket IDs. Pull request #23829
- Client-side check implemented to prevent internal Jira issue IDs from entering the community-edition repository. Pull request #23870
Why it matters
The UI migration to HDS modernizes the user interface across the project, while post-quantum cryptography support addresses emerging security requirements for service mesh communication. Infrastructure improvements around release hygiene help maintain code quality and prevent accidental internal metadata leakage.
Changelog entry
- Ui: Migrated Consul UI to Helios Design System (HDS) Pull request #23911
- Connect: Added Post-Quantum Cryptography hybrid key exchange support (X25519MLKEM768 / NIST FIPS 203) for Envoy service mesh sidecars and Agent TLS Pull request #23884
- Ui: Fixed HDS migration regressions in filter bars, health indicators, navigation, and service views Pull request #23924
- Build: Added release hygiene workflow to scan for internal Jira ticket IDs in PR descriptions and source files Pull request #23829
- Build: Added client-side check to prevent internal Jira issue IDs from entering community-edition repository Pull request #23870
Consul now features a modernized UI with Helios Design System, post-quantum cryptography support for Connect sidecars, and improved release hygiene workflows.
This week's Consul updates bring significant improvements: the UI migrates to Helios Design System for a modernized interface, post-quantum cryptography hybrid key exchange is enabled across Connect Envoy sidecars and TLS communication, and new release hygiene workflows prevent internal metadata from entering the community repository.