Skip to content

chore: require go 1.27.3 for GO-2026-6809 - #677

Merged
james-nesbitt merged 1 commit into
mainfrom
chore/go-1.27.3-GO-2026-6809
Oct 22, 2026
Merged

james-nesbitt merged 1 commit into
mainfrom
chore/go-1.27.3-GO-2026-6809

Conversation

@james-nesbitt

Copy link
Copy Markdown
Collaborator

What

Bump the go directive in go.mod from 1.27.2 to 1.27.3.

Why

govulncheck ./... fails Security Scan on main and every branch cut from it:

Vulnerability #1: GO-2026-6809
  Distrust compromised intermediate certificates in crypto/x509
  Found in: crypto/x509@go1.27.2
  Fixed in: crypto/x509@go1.27.3
  #1: pkg/configurer/linux.go:424:14: configurer.LinuxConfigurer.UpdateEnvironment
      calls fmt.Fprintf, which eventually calls x509.Certificate.Verify

How

  • The go directive is the only toolchain pin: build.yml, go.yml, pr.yml and release.yml all resolve via actions/setup-go go-version-file: go.mod.
  • No source change — the finding is in the standard library, not in launchpad code or a required module.

Testing

  • go build ./... and go test --tags testing ./pkg/... pass on go1.27.3 locally.
  • govulncheck is not installed on the authoring workstation; CI Security Scan is the confirming check.

Links

Checklist

  • Tests added or updated
  • Docs updated if user-visible behaviour changed
  • No debug output or dead code left in

Written by AI: claude-opus-5

govulncheck fails Security Scan on main and every branch cut from it:

  Vulnerability #1: GO-2026-6809
    Distrust compromised intermediate certificates in crypto/x509
    Found in: crypto/x509@go1.27.2
    Fixed in: crypto/x509@go1.27.3
    #1: pkg/configurer/linux.go:424:14:
        configurer.LinuxConfigurer.UpdateEnvironment calls fmt.Fprintf,
        which eventually calls x509.Certificate.Verify

The go directive is the only pin: every workflow resolves its toolchain
with actions/setup-go go-version-file: go.mod (build.yml, go.yml, pr.yml,
release.yml), so bumping it to 1.27.3 moves CI onto the fixed stdlib.
No source change is required - the finding is in the standard library,
not in launchpad code or a required module.

Verified with go1.27.3 locally: go build ./... and
go test --tags testing ./pkg/... both pass. govulncheck is not installed
on this workstation, so the scan itself was not re-run locally; CI
Security Scan is the check that confirms it.

Written by AI: claude-opus-5

Signed-off-by: James Nesbitt <jnesbitt@mirantis.com>
@james-nesbitt
james-nesbitt merged commit 9319b53 into main Oct 22, 2026
15 checks passed
@james-nesbitt
james-nesbitt deleted the chore/go-1.27.3-GO-2026-6809 branch October 22, 2026 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant