Skip to content

fix(security): require patched Go toolchain for eMudhra incident - #28

Merged
zzwong merged 1 commit into
mainfrom
security/emudhra-2026-10-21
Oct 21, 2026
Merged

zzwong merged 1 commit into
mainfrom
security/emudhra-2026-10-21

Conversation

@zzwong

@zzwong zzwong commented Oct 21, 2026

Copy link
Copy Markdown
Owner

Scope

Require Go 1.26.10 for the eMudhra incident in go.mod. Based on freshly cloned main at 332a063127d9afc0e20d0377384f73329db8fe8c; no dependency version, source, archive, or release-artifact changes. Existing toolchain directives were absent.

Existing CI/build selectors follow go.mod or the selected Go compiler; no old literal active compiler selector found. Historical plans and source examples are unchanged.

Verification

Bounded commands with an allowlisted environment, scratch HOME, no ambient credentials/Go configuration, and task-local patched public CA bundle (empty system cert directory); no TLS bypass. Default verification uses Go 1.27.3.

  • go version: exit 0.
  • go mod tidy -diff: exit 0.
  • go test -mod=readonly -count=1 -timeout=90s ./...: exit 0.
  • go vet -mod=readonly ./...: exit 0.
  • go version (exact Go 1.26.10): exit 0.
  • go test -mod=readonly -run=^$ -timeout=60s ./... (exact Go 1.26.10): exit 0.

git diff --check passed; complete diff directly reviewed as security-only. Independent review/parent gates and live required CI/review policy remain pending. No release, deployment, running-binary replacement, or deployed runtime proof is claimed. Previously distributed artifacts still require reviewed patched-compiler rebuild/release. Do not merge until parent review gates. No merge, policy/Actions changes, admin bypass, or force push.

@zzwong
zzwong merged commit 3eabd3d into main Oct 21, 2026
4 checks passed
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