fix(deps): Update module google.golang.org/grpc to v1.79.3 [SECURITY] - abandoned by cq-bot · Pull Request #124 · cloudquery/distribution
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| google.golang.org/grpc | v1.74.3 → v1.79.3 |
GitHub Vulnerability Alerts
CVE-2026-33186
Impact
What kind of vulnerability is it? Who is impacted?
It is an Authorization Bypass resulting from Improper Input Validation of the HTTP/2 :path pseudo-header.
The gRPC-Go server was too lenient in its routing logic, accepting requests where the :path omitted the mandatory leading slash (e.g., Service/Method instead of /Service/Method). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official grpc/authz package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with /) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present.
Who is impacted?
This affects gRPC-Go servers that meet both of the following criteria:
- They use path-based authorization interceptors, such as the official RBAC implementation in
google.golang.org/grpc/authzor custom interceptors relying oninfo.FullMethodorgrpc.Method(ctx). - Their security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule).
The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed :path headers directly to the gRPC server.
Patches
Has the problem been patched? What versions should users upgrade to?
Yes, the issue has been patched. The fix ensures that any request with a :path that does not start with a leading slash is immediately rejected with a codes.Unimplemented error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string.
Users should upgrade to the following versions (or newer):
- v1.79.3
- The latest master branch.
It is recommended that all users employing path-based authorization (especially grpc/authz) upgrade as soon as the patch is available in a tagged release.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods:
1. Use a Validating Interceptor (Recommended Mitigation)
Add an "outermost" interceptor to your server that validates the path before any other authorization logic runs:
func pathValidationInterceptor(ctx context.Context, req any, info *grpc.UnaryServerInfo, handler grpc.UnaryHandler) (any, error) { if info.FullMethod == "" || info.FullMethod[0] != '/' { return nil, status.Errorf(codes.Unimplemented, "malformed method name") } return handler(ctx, req) } // Ensure this is the FIRST interceptor in your chain s := grpc.NewServer( grpc.ChainUnaryInterceptor(pathValidationInterceptor, authzInterceptor), )
2. Infrastructure-Level Normalization
If your gRPC server is behind a reverse proxy or load balancer (such as Envoy, NGINX, or an L7 Cloud Load Balancer), ensure it is configured to enforce strict HTTP/2 compliance for pseudo-headers and reject or normalize requests where the :path header does not start with a leading slash.
3. Policy Hardening
Switch to a "default deny" posture in your authorization policies (explicitly listing all allowed paths and denying everything else) to reduce the risk of bypasses via malformed inputs.
Release Notes
grpc/grpc-go (google.golang.org/grpc)
v1.79.3: Release 1.79.3
Security
- server: fix an authorization bypass where malformed :path headers (missing the leading slash) could bypass path-based restricted "deny" rules in interceptors like
grpc/authz. Any request with a non-canonical path is now immediately rejected with anUnimplementederror. (#8981)
v1.79.2: Release 1.79.2
Bug Fixes
- stats: Prevent redundant error logging in health/ORCA producers by skipping stats/tracing processing when no stats handler is configured. (#8874)
v1.79.1: Release 1.79.1
Bug Fixes
- grpc: Remove the
-devsuffix from the User-Agent header. (#8902)
v1.79.0: Release 1.79.0
API Changes
- mem: Add experimental API
SetDefaultBufferPoolto change the default buffer pool. (#8806)- Special Thanks: @vanja-p
- experimental/stats: Update
MetricsRecorderto require embedding the newUnimplementedMetricsRecorder(a no-op struct) in all implementations for forward compatibility. (#8780)
Behavior Changes
- balancer/weightedtarget: Remove handling of
Addressesand only handleEndpointsin resolver updates. (#8841)
New Features
- experimental/stats: Add support for asynchronous gauge metrics through the new
AsyncMetricReporterandRegisterAsyncReporterAPIs. (#8780) - pickfirst: Add support for weighted random shuffling of endpoints, as described in gRFC A113.
- This is enabled by default, and can be turned off using the environment variable
GRPC_EXPERIMENTAL_PF_WEIGHTED_SHUFFLING. (#8864)
- This is enabled by default, and can be turned off using the environment variable
- xds: Implement
:authorityrewriting, as specified in gRFC A81. (#8779) - balancer/randomsubsetting: Implement the
random_subsettingLB policy, as specified in gRFC A68. (#8650)- Special Thanks: @marek-szews
Bug Fixes
- credentials/tls: Fix a bug where the port was not stripped from the authority override before validation. (#8726)
- Special Thanks: @Atul1710
- xds/priority: Fix a bug causing delayed failover to lower-priority clusters when a higher-priority cluster is stuck in
CONNECTINGstate. (#8813) - health: Fix a bug where health checks failed for clients using legacy compression options (
WithDecompressororRPCDecompressor). (#8765)- Special Thanks: @sanki92
- transport: Fix an issue where the HTTP/2 server could skip header size checks when terminating a stream early. (#8769)
- Special Thanks: @joybestourous
- server: Propagate status detail headers, if available, when terminating a stream during request header processing. (#8754)
- Special Thanks: @joybestourous
Performance Improvements
- credentials/alts: Optimize read buffer alignment to reduce copies. (#8791)
- mem: Optimize pooling and creation of
bufferobjects. (#8784) - transport: Reduce slice re-allocations by reserving slice capacity. (#8797)
v1.78.0: Release 1.78.0
Behavior Changes
- client: Align URL validation with Go 1.26+ to now reject target URLs with unbracketed colons in the hostname. (#8716)
- Special Thanks: @neild
- transport/client : Return status code
Unknownon malformed grpc-status. (#8735) -
- xds/resolver:
- Drop previous route resources and report an error when no matching virtual host is found.
- Only log LDS/RDS configuration errors following a successful update and retain the last valid resource to prevent transient failures. (#8711)
New Features
- stats/otel: Add backend service label to weighted round robin metrics as part of A89. (#8737)
- stats/otel: Add subchannel metrics (without the disconnection reason) to eventually replace the pickfirst metrics. (#8738)
- client: Wait for all pending goroutines to complete when closing a graceful switch balancer. (#8746)
- Special Thanks: @twz123
- client: Add
experimental.AcceptCompressorsso callers can restrict thegrpc-accept-encodingheader advertised for a call. (#8718)- Special Thanks: @iblancasa
Bug Fixes
- xds: Fix a bug in
StringMatcherwhere regexes would match incorrectly when ignore_case is set to true. (#8723) - client:
- Change connectivity state to CONNECTING when creating the name resolver (as part of exiting IDLE).
- Change connectivity state to TRANSIENT_FAILURE if name resolver creation fails (as part of exiting IDLE).
- Change connectivity state to IDLE after idle timeout expires even when current state is TRANSIENT_FAILURE.
- Fix a bug that resulted in
OnFinishcall option not being invoked for RPCs where stream creation failed. (#8710)
- xdsclient: Fix a race in the xdsClient that could lead to resource-not-found errors. (#8627)
Performance Improvements
- mem: Round up to nearest 4KiB for pool allocations larger than 1MiB. (#8705)
- Special Thanks: @cjc25
v1.77.0: Release 1.77.0
API Changes
- mem: Replace the
Readerinterface with a struct for better performance and maintainability. (#8669)
Behavior Changes
- balancer/pickfirst: Remove support for the old
pick_firstLB policy via the environment variableGRPC_EXPERIMENTAL_ENABLE_NEW_PICK_FIRST=false. The newpick_firsthas been the default sincev1.71.0. (#8672)
Bug Fixes
- xdsclient: Fix a race condition in the ADS stream implementation that could result in
resource-not-founderrors, causing the gRPC client channel to move toTransientFailure. (#8605) - client: Ignore HTTP status header for gRPC streams. (#8548)
- client: Set a read deadline when closing a transport to prevent it from blocking indefinitely on a broken connection. (#8534)
- Special Thanks: @jgold2-stripe
- client: Fix a bug where default port 443 was not automatically added to addresses without a specified port when sent to a proxy.
- Setting environment variable
GRPC_EXPERIMENTAL_ENABLE_DEFAULT_PORT_FOR_PROXY_TARGET=falsedisables this change; please file a bug if any problems are encountered as we will remove this option soon. (#8613)
- Setting environment variable
- balancer/pickfirst: Fix a bug where duplicate addresses were not being ignored as intended. (#8611)
- server: Fix a bug that caused overcounting of channelz metrics for successful and failed streams. (#8573)
- Special Thanks: @hugehoo
- balancer/pickfirst: When configured, shuffle addresses in resolver updates that lack endpoints. Since gRPC automatically adds endpoints to resolver updates, this bug only affects custom LB policies that delegate to
pick_firstbut don't set endpoints. (#8610) - mem: Clear large buffers before re-using. (#8670)
Performance Improvements
- transport: Reduce heap allocations to reduce time spent in garbage collection. (#8624, #8630, #8639, #8668)
- transport: Avoid copies when reading and writing Data frames. (#8657, #8667)
- mem: Avoid clearing newly allocated buffers. (#8670)
New Features
- outlierdetection: Add metrics specified in gRFC A91. (#8644)
- Special Thanks: @davinci26, @PardhuKonakanchi
- stats/opentelemetry: Add support for optional label
grpc.lb.backend_servicein per-call metrics (#8637) - xds: Add support for JWT Call Credentials as specified in gRFC A97. Set environment variable
GRPC_EXPERIMENTAL_XDS_BOOTSTRAP_CALL_CREDS=trueto enable this feature. (#8536)- Special Thanks: @dimpavloff
- experimental/stats: Add support for up/down counters. (#8581)
v1.76.0: Release 1.76.0
Dependencies
Bug Fixes
- client: Return status
INTERNALwhen a server sends zero response messages for a unary or client-streaming RPC. (#8523) - client: Fail RPCs with status
INTERNALinstead ofUNKNOWNupon receiving http headers with status 1xx andEND_STREAMflag set. (#8518)- Special Thanks: @vinothkumarr227
- pick_first: Fix race condition that could cause pick_first to get stuck in
IDLEstate on backend address change. (#8615)
New Features
- credentials: Add
credentials/jwtpackage providing file-based JWT PerRPCCredentials (A97). (#8431)- Special Thanks: @dimpavloff
Performance Improvements
- client: Improve HTTP/2 header size estimate to reduce re-allocations. (#8547)
- encoding/proto: Avoid redundant message size calculation when marshaling. (#8569)
- Special Thanks: @rs-unity
v1.75.1: Release 1.75.1
Bug Fixes
- transport: Fix a data race while copying headers for stats handlers in the std lib http2 server transport. (#8519)
- xdsclient:
- server: Fix a regression preventing streams from being cancelled or timed out when blocked on flow control. (#8528)
v1.75.0: Release 1.75.0
Behavior Changes
- xds: Remove support for GRPC_EXPERIMENTAL_XDS_FALLBACK environment variable. Fallback support can no longer be disabled. (#8482)
- stats: Introduce
DelayedPickCompleteevent, a type alias ofPickerUpdated. (#8465)- This (combined) event will now be emitted only once per call, when a transport is successfully selected for the attempt.
- OpenTelemetry metrics will no longer have multiple "Delayed LB pick complete" events in Go, matching other gRPC languages.
- A future release will delete the
PickerUpdatedsymbol.
- credentials: Properly apply
grpc.WithAuthorityas the highest-priority option for setting authority, above the setting in the credentials themselves. (#8488)- Now that this
WithAuthorityis available, the credentials should not be used to override the authority.
- Now that this
- round_robin: Randomize the order in which addresses are connected to in order to spread out initial RPC load between clients. (#8438)
- server: Return status code INTERNAL when a client sends more than one request in unary and server streaming RPC. (#8385)
- This is a behavior change but also a bug fix to bring gRPC-Go in line with the gRPC spec.
New Features
- dns: Add an environment variable (
GRPC_ENABLE_TXT_SERVICE_CONFIG) to provide a way to disable TXT lookups in the DNS resolver (by setting it tofalse). By default, TXT lookups are enabled, as they were previously. (#8377)
Bug Fixes
- xds: Fix regression preventing empty node IDs in xDS bootstrap configuration. (#8476)
- Special Thanks: @davinci26
- xds: Fix possible panic when certain invalid resources are encountered. (#8412)
- Special Thanks: @wooffie
- xdsclient: Fix a rare panic caused by processing a response from a closed server. (#8389)
- stats: Fix metric unit formatting by enclosing non-standard units like
callandendpointin curly braces to comply with UCUM and gRPC OpenTelemetry guidelines. (#8481) - xds: Fix possible panic when clusters are removed from the xds configuration. (#8428)
- xdsclient: Fix a race causing "resource doesn not exist" when rapidly subscribing and unsubscribing to the same resource. (#8369)
- client: When determining the authority, properly percent-encode (if needed, which is unlikely) when the target string omits the hostname and only specifies a port (
grpc.NewClient(":<port-number-or-name>")). (#8488)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.