Fix 2 issues flagged across 2 files - #486
Closed
begininvoke wants to merge 2 commits into
Closed
Conversation
Member
|
Oh no, reprolang is compromised. What a tragedy. And the go indexer could maybe get stuck in an infinite loop? No way. |
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.
A scan flagged a few things in this repository. This changes 2 files — one item each, described below.
1.
go.mod, around line 1The
golang.org/x/textpackage contains a vulnerability in itsnorm.Iterimplementation that triggers an infinite loop when processing input containing invalid UTF-8 bytes. This results in a high-severity Denial of Service (DoS), causing application thread hangs and excessive CPU consumption. Immediate dependency upgrade to the patched version is required.Updates golang.org/x/text from v0.38.0 to v0.39.0 to address CVE‑2026‑56852, preserving the existing API and ensuring the go.mod file parses correctly.
For reference: rule
CVE-2026-56852. Rated high.2.
reprolang/go.mod, around line 1This HIGH severity vulnerability in golang.org/x/mod v0.33.0 allows a coordinated attack via GOPROXY and GOSUMDB to serve malicious module content that bypasses transparency log verification. Exploitation enables undetectable supply chain poisoning, potentially leading to arbitrary code execution or data compromise. Immediate update is required.
Update golang.org/x/mod from v0.33.0 to v0.40.0 to resolve CVE-2026-56864 and CVE-2026-56865.
For reference: rule
CVE-2026-56864. Rated high.I do not know the codebase, so please check the change fits how the rest of it works. Happy to adjust it or close this if the reasoning is off.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.