chore(deps): update module google.golang.org/grpc to v1.82.1 [security] (release-v1.40) - autoclosed - #5092
Closed
marvin-tigera wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
marvin-tigera
deleted the
renovate/release-v1.40-go-google.golang.org-grpc-vulnerability
branch
July 24, 2026 01:03
pasanw
added a commit
to pasanw/operator
that referenced
this pull request
Aug 7, 2026
Mirrors the master/release-v1.43 fix (tigera#5100 / tigera#5101) for the release-v1.40 line. All three deps are indirect; no operator code changes. - helm.sh/helm/v3 v3.20.2 -> v3.21.3: the operator never imports github.com/containerd/containerd itself; it only pulled it in transitively through helm. Helm v3.21.3 drops that dependency, so the vulnerable containerd code stops shipping in the operator binary -- clearing CVE-2026-50195 (crit 9.9), CVE-2026-53492 (crit 9.6) and CVE-2026-53489 (high), none of which has a fix in the containerd 1.7.x line. This bump pulls k8s.io/* v0.35 -> v0.36 with it (same shape as a prior k8s bump on this branch). - sigs.k8s.io/controller-runtime v0.23.3 -> v0.24.1: required for k8s v0.36 compatibility (matches release-v1.43); no operator code changes. - oras.land/oras-go/v2 v2.6.0 -> v2.6.2: clears CVE-2026-50151 and CVE-2026-50163 (both confirmed fixed in v2.6.2 by OSV / the GitHub Advisory DB). An earlier attempt stopped at v2.6.1, which cleared only CVE-2026-50151. - google.golang.org/grpc -> v1.82.1: clears GHSA-hrxh-6v49-42gf / GO-2026-6061. The oras and grpc requires carry advisory-naming comments so a future re-tidy cannot silently revert the pins. Supersedes the autoclosed Renovate security PRs tigera#5092 (grpc) and tigera#5011 (oras v2.6.1). Note: Renovate keys vulnerability alerts off the default branch, so release-branch security PRs autoclose when master is fixed -- this branch's containerd exposure would otherwise be invisible to automation post-merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
pasanw
added a commit
to pasanw/operator
that referenced
this pull request
Aug 7, 2026
Indirect dependency bumps only; no operator code changes, no k8s change. - oras.land/oras-go/v2 v2.6.0 -> v2.6.2: clears CVE-2026-50151 and CVE-2026-50163 (oras hardlink path traversal, high 7.1). Both are recorded as fixed = 2.6.2 by OSV and the GitHub Advisory DB, and by the master / release-v1.43 fixes (tigera#5100 / tigera#5101). (An earlier version of this PR stopped at v2.6.1 and wrongly stated v2.6.2 was not the fix.) - google.golang.org/grpc -> v1.82.1: clears GHSA-hrxh-6v49-42gf / GO-2026-6061. Both requires carry advisory-naming comments so a future go mod tidy cannot silently revert the pins. NOT fixed here, deliberately: the containerd advisories CVE-2026-50195 (crit 9.9), CVE-2026-53492 (crit 9.6) and CVE-2026-53489 (high). containerd 1.7.33 has no fixed version; the only remediation is dropping the (purely transitive, via Helm) dependency by bumping Helm to v3.21.3 -- but every containerd-free Helm is already on k8s v0.36, and this branch is kept on k8s v0.35 to stay aligned with the calico-private core (also on k8s 1.35), avoiding an operator/core minor-version divergence. These three are VEXed on this line; master and release-v1.43, already on k8s 1.36, take the Helm route (tigera#5100 / tigera#5101). Supersedes the autoclosed Renovate security PRs tigera#5092 (grpc) and tigera#5011 (oras v2.6.1). Renovate keys vulnerability alerts off the default branch, so release-branch security PRs autoclose when master is fixed -- this branch's exposure would otherwise be invisible to automation post-merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
This PR contains the following updates:
v1.80.0→v1.82.1gRPC-Go: xDS RBAC and HTTP/2 Vulnerabilities
GHSA-hrxh-6v49-42gf
More information
Details
Multiple security vulnerabilities have been identified and addressed in grpc-go affecting the xDS RBAC authorization engine (internal/xds/rbac) and the HTTP/2 transport server implementation (internal/transport). These vulnerabilities could result in:
MetadataorRequestedServerNamefields.NOTrules around unsupported fields.Impact
What kind of vulnerability is it? Who is impacted?
xDS RBAC Authorization Bypass via
Metadata&RequestedServerNamematcherspermissionandprincipalrules (specificallyMetadataandRequestedServerName) were silently ignored and treated as no-ops.NOTrules (Permission_NotRule/Principal_NotId) or multi-conditionOR/ANDrules, silently dropping them changed the boolean logic flow of the authorization engine.As a result, policy evaluation decisions could fail open, allowing unauthorized clients to access protected gRPC services or resources.
HTTP/2 Rapid Reset Mitigation Bypass / Denial of Service via Stream Aborts
SETTINGSACKs or server-initiatedRST_STREAMs.When a client initiated a rapid flood of stream creation (
HEADERS) immediately followed by stream terminationRST_STREAM, items queued up in the control buffer without counting against the transport response frame threshold. An attacker can repeatedly trigger this flood sequence to bypass reader blocking, resulting in high CPU usage, and Denial of Service (DoS).Denial of Service (Panic) in xDS RBAC Engine via Unsupported Fields inside NOT Rules
NOTrule wrapped an unsupported or unhandled field (such asSourcedMetadata), the recursive step returned an empty matcher. This could result in a runtime panic when the RBAC engine attempts to authorize an incoming request.An attacker or misconfigured/malicious xDS management server delivering an LDS/RDS update containing a
NOTrule around an unhandled field causes the gRPC server process to crash immediately (CWE-248 / Denial of Service).Patches
Has the problem been patched? What versions should users upgrade to?
All three issues have been fixed in
masterand will be released in 1.82.1 shortly.Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
If upgrading grpc-go immediately is not possible, apply the following workarounds based on your deployment architecture:
Metadata,RequestedServerName, orNOTrules wrapping unsupported fields (such asSourcedMetadata) to grpc-go servers.max_concurrent_streamslimits and active rate limiting onRST_STREAMfrequency per connection.Severity
8.27.55.9Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
grpc/grpc-go (google.golang.org/grpc)
v1.82.1: Release 1.82.1Compare Source
Security
GRPC_GO_EXPERIMENTAL_CONTROL_BUFFER_THROTTLE_LIMIT.MetadataandRequestedServerNamepermissions matcher fields. If present in a DENY rule, previously these would be ignored and fail-open.NotRule/NotIdpermissions.source_ipprincipal identifier by treating it as equivalent todirect_remote_ip.v1.82.0: Release 1.82.0Compare Source
Behavior Changes
GRPC_GO_EXPERIMENTAL_DISABLE_STRICT_PATH_CHECKINGenvironment varibale. Strict incoming RPC path validation (which has been the default sincev1.79.3) can no longer be disabled. (#9112)16MBto8KB. This may be enabled by settingGRPC_GO_EXPERIMENTAL_ENABLE_8KB_DEFAULT_HEADER_LIST_SIZE=true. This will be enabled by default in a subsequent release. (#9019)GRPC_GO_EXPERIMENTAL_CASE_SENSITIVE_BALANCER_REGISTRIES=false(and file an issue) to revert to case-insensitive behavior. (#9017)New Features
NewContextWithLabelCallback, to register a callback that is invoked when telemetry labels are added. (#8877)GRPC_GO_SERVER_GOROUTINE_LABELSthat controls settingruntime/pprof.Labelson goroutines spawned by the server. SetGRPC_GO_SERVER_GOROUTINE_LABELS=grpc.method=trueto add thegrpc.methodlabel on goroutines spawned to handle incoming requests. (#9082)Bug Fixes
gzipCompressor (used via the deprecatedWithCompressordial option), enforce theMaxRecvMsgSizelimit on the decompressed message buffer, preventing excessive memory allocation from highly compressed payloads. (#9114)grpc.previous-rpc-attempts, at the call level and not the attempt level. (#8923)Close()is always called on readers returned fromCompressor.Decompressif possible. (#9135)LastMessageSentTimestampandLastMessageReceivedTimestampfields inSocketMetricsto ensure they contain correct timestamp values. (#9109)v1.81.1: Release 1.81.1Compare Source
Security
Bug Fixes
v1.81.0: Release 1.81.0Compare Source
Behavior Changes
Dependencies
Bug Fixes
RST_STREAMwhen receiving anEND_STREAMwhen the stream is not already half-closed. (#8832)New Features
GRPC_EXPERIMENTAL_XDS_SNI=trueenvironment variable. (#9016)GRPC_EXPERIMENTAL_XDS_ORCA_LRS_PROPAGATION=true. (#9005)grpc.subchannel.disconnectionsmetric by adding disconnection reason to thegrpc.disconnect_errorlabel (gRFC A94). This provides granular insights into why subchannels are closing. (#8973)mem.Buffer.Slice()API to slice the buffer like a slice. (#8977)Performance Improvements
GRPC_GO_EXPERIMENTAL_HTTP_FRAMER_READ_BUFFER_POOLING=falseand report any issues. (#9032)