Skip to content

fix: upgrade Go to 1.25.11 (CVE-2026-27145, CVE-2026-42507)#26065

Merged
Shelnutt2 merged 1 commit into
release/2.33from
sshelnutt/ent-107-go-1.25.11
Jun 4, 2026
Merged

fix: upgrade Go to 1.25.11 (CVE-2026-27145, CVE-2026-42507)#26065
Shelnutt2 merged 1 commit into
release/2.33from
sshelnutt/ent-107-go-1.25.11

Conversation

@Shelnutt2
Copy link
Copy Markdown
Contributor

Summary

Upgrades the Go toolchain from 1.25.10 to 1.25.11 on the release/2.33 branch to address two low-severity CVEs:

  • CVE-2026-27145 (Low): crypto/x509 VerifyHostname quadratic cost with large DNS SAN list (DoS on untrusted certs)
  • CVE-2026-42507 (Low): net/textproto attacker-controlled input included in errors without escaping (log injection)

Changes

  • go.mod: bump go directive from 1.25.10 to 1.25.11
  • .github/actions/setup-go/action.yaml: update default Go version
  • dogfood/coder/ubuntu-26.04/Dockerfile: update GO_VERSION and GO_CHECKSUM
  • dogfood/coder/ubuntu-22.04/Dockerfile: update GO_VERSION and GO_CHECKSUM

Relates to: ENT-107

Generated by Coder Agents

@linear-code
Copy link
Copy Markdown

linear-code Bot commented Jun 4, 2026

ENT-107

@Shelnutt2 Shelnutt2 marked this pull request as ready for review June 4, 2026 13:39
@Shelnutt2 Shelnutt2 requested a review from f0ssel June 4, 2026 13:40
Copy link
Copy Markdown
Member

@Emyrk Emyrk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we are on 1.26 now

@Shelnutt2
Copy link
Copy Markdown
Contributor Author

we are on 1.26 now

This is the release-2.33 "stable" branch.

@Shelnutt2 Shelnutt2 merged commit 757e570 into release/2.33 Jun 4, 2026
39 of 41 checks passed
@Shelnutt2 Shelnutt2 deleted the sshelnutt/ent-107-go-1.25.11 branch June 4, 2026 15:28
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 4, 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