chore: bump Go to 1.26.4 on release/2.34 by sreya · Pull Request #26265 · coder/coder · GitHub
Skip to content

chore: bump Go to 1.26.4 on release/2.34#26265

Merged
sreya merged 1 commit into
release/2.34from
backport-go-1.26.4-release-2.34
Jun 11, 2026
Merged

chore: bump Go to 1.26.4 on release/2.34#26265
sreya merged 1 commit into
release/2.34from
backport-go-1.26.4-release-2.34

Conversation

@sreya

@sreya sreya commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Backports the Go toolchain security update to release/2.34.

release/2.34 is already on Go 1.26.4 in go.mod/mise.toml, but the setup-go composite action still defaulted to 1.26.2. This updates the action default to 1.26.4 so CI uses the patched toolchain, addressing:

  • CVE-2026-27145 (Low): crypto/x509 VerifyHostname quadratic cost with large DNS SAN lists.
  • CVE-2026-42507 (Low): net/textproto unescaped attacker-controlled input in errors (log injection).

Related to the upstream upgrade in #26066 (61a35185cf).

Why this differs from a direct cherry-pick of 61a3518

Commit 61a35185cf bumps go.mod/mise.toml/mise.lock from 1.26.2 to 1.26.4. On release/2.34 those files are already at 1.26.4, so a cherry-pick is a no-op there. The only remaining 1.26.2 reference was the setup-go action default, which this PR updates directly.

Generated by Coder Agents on behalf of @sreya

@sreya sreya requested a review from jdomeracki-coder as a code owner June 11, 2026 15:03
@sreya sreya self-assigned this Jun 11, 2026
@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown

@sreya sreya changed the title chore(.github/actions/setup-go): bump Go to 1.26.4 on release/2.34 chore: bump Go to 1.26.4 on release/2.34 Jun 11, 2026
@sreya sreya merged commit fad8efd into release/2.34 Jun 11, 2026
55 of 56 checks passed
@sreya sreya deleted the backport-go-1.26.4-release-2.34 branch June 11, 2026 15:14
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants