Fix possible fix(deps): 2 vulnerable dependencies in go.mod - #78
Merged
Autumn-27 merged 1 commit intoAug 31, 2026
Merged
Conversation
|
@begininvoke is attempting to deploy a commit to the Autumn's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
2 participants
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.
This changes
go.modto address something a scan flagged. It is around line 1.The project depends on golang.org/x/mod v0.37.0, which is vulnerable to CVE-2026-56864. A compromised GOSUMDB can serve arbitrary module code that bypasses the module checksum database and transparency log, allowing an attacker to inject malicious code into the build process. Because this can lead to execution of arbitrary code in downstream applications, the risk is classified as HIGH.
Update golang.org/x/mod from v0.37.0 to v0.40.0 to resolve two high‑severity CVEs.
For reference: rule
CVE-2026-56864. Rated high.I may well be missing context here — if the current code is deliberate, feel free to close this.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.