Skip to content

security: bump golang.org/x/mod to fix CVE-2026-56864/56865 - #538

Merged
scttfrdmn merged 2 commits into
mainfrom
chore/bump-x-mod-cve-56864
Aug 19, 2026
Merged

security: bump golang.org/x/mod to fix CVE-2026-56864/56865#538
scttfrdmn merged 2 commits into
mainfrom
chore/bump-x-mod-cve-56864

Conversation

@scttfrdmn

Copy link
Copy Markdown
Contributor

Trivy's vulnerability DB started flagging the transitive golang.org/x/mod v0.37.0 dependency (pulled in via pkg/plugin -> sigstore-go's module-verification code) as HIGH severity for CVE-2026-56864/CVE-2026-56865 — a malicious GOSUMDB/GOPROXY could forge module checksums. This started failing the Security Scan check on every open PR in this repo regardless of what the PR actually changed, since it's a scan of the dependency graph on main, not a diff.

Bumped to v0.40.0 (the fixed version) via go get golang.org/x/mod@v0.40.0 && go mod tidy. No other dependency changed. go build ./..., go vet ./..., and go test -short ./... all clean.

Trivy's vulnerability DB started flagging the transitive x/mod v0.37.0
dependency (pulled in via pkg/plugin -> sigstore-go) as HIGH, failing the
Security Scan check on every open PR regardless of what changed. Bump to
v0.40.0, the fixed version.
Same CVE-2026-56864/56865 fix as the root module, missed on the first
pass because lambda/ttl-reaper pins its own go.mod (a separate Go
module with a replace directive to ../.., per this repo's structure) and
isn't touched by `go mod tidy` at the repo root. This is exactly the
"nested module pins its own deps" trap noted for lagotto#43 — a stale
go.mod in a nested lambda module fails CI without naming which module.
@codecov

codecov Bot commented Aug 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@scttfrdmn
scttfrdmn merged commit 0d5683c into main Aug 19, 2026
7 checks passed
@scttfrdmn
scttfrdmn deleted the chore/bump-x-mod-cve-56864 branch August 19, 2026 21:39
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