You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[SECURITY] Published release v0.12.778 is built with go1.25.3 and still trusts the compromised eMudhra intermediates; cut a Go 1.26.10 release #857
The eMudhra mitigation (CVE-2026-111943) is code in Go's own crypto/x509, shipped in Go 1.27.3 and 1.26.10 on 2026-10-19. A binary has it only if it was compiled with one of those versions or later. No library dependency can supply it, and no go directive in a library's go.mod delivers it.
#855 moved main to Go 1.26.10 (go.mod, build.yml, lint.yml, mcp-wringer.yml, Dockerfile). The binary users download today is still the one built before that: releases.stackql.io/stackql/latest serves v0.12.778, built 2026-10-11 with go1.25.3.
Evidence (2026-10-21, Linux amd64)
Client
Trust store
Compromised direct chain
Compromised AAA cross-signed chain
stackql v0.12.778 (go version -m = go1.25.3)
--tls.CABundle containing the root
TLS accepted, page fetched
TLS accepted, page fetched
Go 1.22.2 probe
same roots, explicit RootCAs
accepted
accepted
Go 1.27.3 probe
same roots, explicit RootCAs
rejected: x509: no valid chains built
rejected: x509: no valid chains built
Test hosts are the ones published at https://emudhra.we-have-a-problem.com/. With a patched OS store (Ubuntu ca-certificates 20260816ubuntu0.24.04.1) the direct chain fails for any Go, but the Sectigo AAA root behind the cross-signed chain is still shipped by Apple, Microsoft and several bundled stores, so the OS store is not a reliable backstop. The Go blocklist is, and it needs a rebuild to exist.
Ask
Cut and publish a release from the first successful main build after emudhra-incident-response #855 (run 39523752150 was in progress when this was filed): tag v0.12.<build>, follow docs/stackql_release_process.md, run mcp-packaging, push the tag to releases.stackql.io so latest serves a 1.26.10 build. Docker Hub and the MCPB bundles pick it up through that process.
mcp-packaging.yml, sdk job: the Go MCP launcher (packaging/mcpb/go, go.mod says go 1.25.0) is still built with go-version: '1.25'. Go 1.25 is out of support and never received the fix. Move it to 1.26.10 like the other jobs. Impact is small (the launcher verifies downloads against sha256 pins in its embedded manifest), but it is the last unpatched toolchain in the repo.
goreleaser.yml still pins actions/setup-go@v2 with go-version: 1.16 on release* tags. Retire it or bring it in line.
Optional: add toolchain go1.26.10 to go.mod so a developer with an older local Go gets exactly the fixed version instead of a build error.
Note on the SDK directives
stackql-labs/omnisdk v0.1.5-beta03 briefly set go 1.27.2, the last version without the fix; beta04 and beta05 moved to go 1.26.10. Either way, a library's go line is a floor for whoever compiles it, not a fix. Only the toolchain that compiles the stackql binary matters, which #855 now pins.
Status 2026-10-21: v0.12.813 will be cut from Build #813 (run 39543810085, commit 41ef83e, two commits after #855). At that commit go.mod is go 1.27.3, every setup-go in build.yml is 1.27.3 and the Dockerfile builds from golang:1.27.3-bookworm, so the released CLI, Docker image and MCPB bundles carry the crypto/x509 blocklist. That closes item 1. Item 4 is moot: with go 1.27.3 as the directive, GOTOOLCHAIN=auto already selects a fixed toolchain for older local installs.
Still open after the release: item 2 (the Go MCP launcher in mcp-packaging.ymlsdk job is still go-version: '1.25', sha256 pins limit this to availability) and item 3 (goreleaser.yml on Go 1.16). Fine to close this issue on publish and carry those two as housekeeping.
Done in v0.12.824 (go1.27.3): GitHub release, releases.stackql.io latest, Docker Hub latest/v0.12/v0.12.824 and the MCPB bundles all carry the crypto/x509 denylist. Verified the server rejects the live AAA cross-signed test host with x509: no valid chains built, and stackql-mcp-go v0.12.824 launches it from a fresh consumer module. Launcher workflow is on Go 1.27.3; goreleaser.yml retired under #860.
Activity
jeffreyaven commentedon Oct 21, 2026
Status 2026-10-21: v0.12.813 will be cut from Build #813 (run 39543810085, commit 41ef83e, two commits after #855). At that commit
go.modisgo 1.27.3, everysetup-goinbuild.ymlis1.27.3and the Dockerfile builds fromgolang:1.27.3-bookworm, so the released CLI, Docker image and MCPB bundles carry thecrypto/x509blocklist. That closes item 1. Item 4 is moot: withgo 1.27.3as the directive,GOTOOLCHAIN=autoalready selects a fixed toolchain for older local installs.Still open after the release: item 2 (the Go MCP launcher in
mcp-packaging.ymlsdkjob is stillgo-version: '1.25', sha256 pins limit this to availability) and item 3 (goreleaser.ymlon Go 1.16). Fine to close this issue on publish and carry those two as housekeeping.jeffreyaven commentedon Oct 21, 2026
Items 2 and 3 are now tracked separately in #860; this issue can close when v0.12.813 is published.
jeffreyaven commentedon Oct 22, 2026
Done in v0.12.824 (go1.27.3): GitHub release, releases.stackql.io latest, Docker Hub latest/v0.12/v0.12.824 and the MCPB bundles all carry the crypto/x509 denylist. Verified the server rejects the live AAA cross-signed test host with x509: no valid chains built, and stackql-mcp-go v0.12.824 launches it from a fresh consumer module. Launcher workflow is on Go 1.27.3; goreleaser.yml retired under #860.