Repository navigation
Update Go to 1.27.3 - #161
Merged
Merged
Conversation
Fixes GO-2026-6809 (crypto/x509), reported by govulncheck.
There was a problem hiding this comment.
🟢 Approved
The isolated patch-version bump is consistent with CI’s toolchain selection, and no blocking issues were identified.
No open issues 🎉
What changed in this PR
Updates the project’s Go version to pick up the crypto/x509 security fix described in the PR.
Changes:
- Raises the Go directive from
1.27.2to1.27.3; no application code changes.
[!TIP]
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or rungh pr ready --undo.
Click "Ready for review" or rungh pr readyto reengage.
| File | Description |
|---|---|
| go.mod | Updates the Go patch version to 1.27.3. |
Review effort: Balanced
dschmura
added a commit
to dschmura/modelrails_base
that referenced
this pull request
Oct 23, 2026
…s fix ships (#1442) The image scan is red on #1438 and will be on every pull request that touches `Gemfile.lock`: one HIGH finding in the Go baked into Thruster 0.1.27's precompiled binary, CVE-2026-111943 (GO-2026-6809, `crypto/x509` trusting a compromised intermediate), fixed in Go 1.27.3. Thruster 0.1.27 is still the newest release and its binary reports `go1.27.1`. This time the fix is visible upstream: basecamp/thruster#161 moved `main` to Go 1.27.3 and `x/net` 0.61.0 on 2026-10-23, which covers this finding and the three the block already holds. It is merged, not released, and the gem's binary comes from a release, so there is still no action available here. The entry says exactly that, and its revisit trigger names the release that carries #161. When Dependabot opens that bump, the whole Thruster block comes out, as #1410 did for the previous batch. Exposure, for the record and not as the rationale: Thruster terminates TLS only when `TLS_DOMAIN` is set, and `git grep TLS_DOMAIN` over tracked files finds nothing. | Check | Result | | --- | --- | | `template_invariants_spec` (rationale + `Revisit:` per entry) | 1 example, 0 failures | | Pre-push suite | green | | Image Scan on this pull request | the proof; it is the one job the local suite cannot run | After this merges, #1438 and #1441 go green on a rebase.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps Go from 1.27.2 to 1.27.3 to fix GO-2026-6809 (distrust compromised intermediate certificates in
crypto/x509). govulncheck reported it as reachable throughio.Copy.With 1.27.3, tests pass and govulncheck no longer reports any reachable vulnerabilities. The only remaining finding is GO-2026-5932 (
x/crypto/openpgp), which isn't imported and has no fix.