security(deps): bump grpc to v1.82.1 and x/text to v0.39.0 - #111
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
grpc v1.82.1 clears GHSA-hrxh-6v49-42gf (HIGH) — the only fixable finding in ghcr.io/nudgebee/forager:0.1.2 reported by the nudgebee-oss deployed-image Trivy scan. It is an indirect dependency and the Dockerfile already builds on golang 1.26.5, so no other change is needed there. x/text v0.39.0 clears GO-2026-5970 (infinite loop on invalid input), which the repo's own govulncheck gate flags as reachable from mcp.Proxy.HealthCheck, db.Proxy.CollectMetadata/Configure and kafka.scramClient.Begin. This one is pre-existing on main — v0.38.0 is identical there — but the gate blocks any PR until it is bumped, and it is the same class of fix. Takes the image to 0 fixable CRITICAL/HIGH/MEDIUM (the remaining 5C/17H/57M are Debian base-OS packages with no published upstream fix).
mayankpande88
force-pushed
the
security/grpc-1.82.1
branch
from
July 27, 2026 12:47
2e0fde0 to
6e6b045
Compare
mayankpande88
changed the title
RamanKharchee
approved these changes
Jul 27, 2026
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.
Description
Two indirect dependency bumps, both security fixes.
google.golang.org/grpcv1.81.1 → v1.82.1 clears GHSA-hrxh-6v49-42gf (HIGH) — the only fixable finding inghcr.io/nudgebee/forager:0.1.2, surfaced by the nudgebee-oss deployed-image Trivy scan. The Dockerfile already builds ongolang:1.26.5-bookworm, so thego.mod/go.sumbump is the whole change.golang.org/x/textv0.38.0 → v0.39.0 clears GO-2026-5970 (infinite loop on invalid input). This repo's owngovulncheckgate flags it as reachable frommcp.Proxy.HealthCheck,db.Proxy.CollectMetadata,db.Proxy.Configureandkafka.scramClient.Begin.Note: the x/text issue is pre-existing on
main— v0.38.0 is identical there, so it was not introduced by the grpc bump. It is included here because thevulngate blocks any PR until it is bumped, and it is the same class of fix.Together these take the image to 0 fixable CRITICAL/HIGH/MEDIUM. The remaining
5C / 17H / 57Mare Debian base-OS packages (perl-base, zlib1g, libxml2) with no published upstream fix — those need a base migration, not a dependency bump.Type of change
How Has This Been Tested?
make validate(fmt + lint + test) passes:golangci-lintreports 0 issues, all 10 test packages pass with 0 failures,go build ./...andgo vet ./...clean.Checklist
make validatepasses (fmt + lint + test)