Mitigates CVE-2026-111943 (compromised eMudhra intermediate CAs).
- **Go 1.26.9 to 1.26.10** (`go.mod`, `mise.toml`, `mise.lock`). Go
1.26.10 no longer trusts certificates issued through the compromised
intermediates.
- **Bundled Terraform 1.16.6 to 1.16.7** (`install.go`, `install.sh`,
`scripts/Dockerfile.base`, `mise.toml`, `mise.lock`, `flake.nix`, airgap
docs, `testdata/generation.sha1`).
[1.16.7](https://github.com/hashicorp/terraform/releases/tag/v1.16.7) is
built with Go 1.26.10. Checksums come from the GPG-verified
`terraform_1.16.7_SHA256SUMS`. `maxTerraformVersion` stays at 1.16.9.
- **Base image `alpine:3.24.2` to `alpine:3.24.3`**. 3.24.2 ships
`ca-certificates-bundle-20260909-r0`; 3.24.3 ships `20261020-r0`.
Verification:
- Rebuilt `scripts/Dockerfile.base` for linux/amd64 and linux/arm64.
Both contain `ca-certificates-bundle-20261020-r0` and `Terraform
v1.16.7`.
- `go test ./provisioner/terraform/...` passes with Terraform 1.16.7.
- `scripts/check_go_versions.sh` passes.
- Local git hooks were skipped at the author's request because the
dogfood host was overloaded. CI is the gate.
Backports to `release/2.34` through `release/2.38` follow as separate
PRs. Older Terraform minor lines did not get the Go 1.26.10 rebuild
(1.15.9 is built with Go 1.25.10, 1.14.9 with Go 1.25.8), so
release/2.35 also moves to 1.16.7.
<details>
<summary>Decision log</summary>
- The request named Go 1.26.1. Main and every release branch were
already on 1.26.9, so @sreya confirmed the target is 1.26.10.
- release/2.34 stays on the Alpine 3.23 line (`alpine:3.23.7`, which
also ships `ca-certificates-bundle-20261020-r0`) instead of jumping to
3.24.
- release/2.35 had drifted: `install.go` pinned 1.14.5 (max 1.14.9)
while the image and `mise.toml` used 1.15.5. Its backport sets both to
1.16.7 and raises max to 1.16.9.
</details>
> Generated by Coder Agents on behalf of @sreya.