Ignore go1.26.4 stdlib vulns in govulncheck until toolchain bump#5425
Merged
Conversation
The daily Security Scan and every open PR started failing on 2026-06-03 after three Go standard-library advisories were published on 2026-06-02: GO-2026-5037 (CVE-2026-27145, crypto/x509 VerifyHostname) GO-2026-5038 (CVE-2026-42504, mime WordDecoder.DecodeHeader) GO-2026-5039 (CVE-2026-42507, net/textproto error messages) All three are stdlib DoS / log-injection issues (no RCE) fixed in go1.26.4 / go1.25.11. CI builds with `setup-go: stable`, which still resolves to go1.26.3 because the actions/go-versions manifest lags the release, so govulncheck flags them on code we do not control. Add the three OSV IDs to the documented IGNORED_VULNS exclusion list to unblock CI. This is temporary and should be removed once CI builds on go1.26.4 or later. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2 tasks
JAORMX
approved these changes
Jun 3, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5425 +/- ##
==========================================
+ Coverage 68.84% 68.85% +0.01%
==========================================
Files 634 634
Lines 64433 64433
==========================================
+ Hits 44358 44367 +9
+ Misses 16795 16785 -10
- Partials 3280 3281 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Summary
The daily Security Scan and every open PR have been failing the
Go Vulnerability Checksince 2026-06-03 03:03 UTC. On 2026-06-02 three Go standard-library advisories were published, and govulncheck flags them because CI builds withsetup-go: stable, which still resolves to go1.26.3 (theactions/go-versionsmanifest lags the release):GO-2026-5037(CVE-2026-27145) —crypto/x509VerifyHostnamequadratic-cost perfGO-2026-5038(CVE-2026-42504) —mimeWordDecoder.DecodeHeaderexcessive CPUGO-2026-5039(CVE-2026-42507) —net/textprotouser input in error messagesAll three are stdlib DoS / log-injection issues (no RCE) fixed in go1.26.4 / go1.25.11 — code we do not own. This PR adds the three OSV IDs to the existing, documented
IGNORED_VULNSexclusion list to unblock CI. It is explicitly temporary: the comment instructs removing the exclusion once CI builds on go1.26.4 or later (at which pointstablewill resolve to a patched toolchain and the findings disappear on their own).Type of change
Test plan
Manual testing (describe below)
Confirmed each OSV maps to a Go stdlib advisory fixed in go1.26.4 / go1.25.11 via
pkg.go.dev/vuln.Verified the failing job lists exactly these three IDs:
❌ Vulnerabilities need attention: GO-2026-5037 GO-2026-5038 GO-2026-5039.Validated
security-scan.ymlstill parses as YAML.Authoritative check is this PR's own
Go Vulnerability Checkrun going green.API Compatibility
v1beta1API.Does this introduce a user-facing change?
No.
Special notes for reviewers
This is a stop-gap. The clean fix is to get CI onto go1.26.4 (e.g. pin the version or wait for the
actions/go-versionsstablemanifest to catch up). Once that lands, delete the three IDs fromIGNORED_VULNSand restore the comment to "none currently."Generated with Claude Code