fix(deps): Update module google.golang.org/grpc to v1.79.3 [SECURITY]

[renovate-sh-app]

This PR contains the following updates:

Package	Change	Age	Confidence
google.golang.org/grpc	v1.78.0 → v1.79.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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:

1. They use path-based authorization interceptors, such as the official RBAC implementation in google.golang.org/grpc/authz or custom interceptors relying on info.FullMethod or grpc.Method(ctx).
2. 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.

---

gRPC-Go has an authorization bypass via missing leading slash in :path

CVE-2026-33186 / GHSA-p77j-4mvh-x3m3

More information

Details

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:

1. They use path-based authorization interceptors, such as the official RBAC implementation in google.golang.org/grpc/authz or custom interceptors relying on info.FullMethod or grpc.Method(ctx).
2. 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.

Severity

• CVSS Score: 9.1 / 10 (Critical)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

References

• https://github.com/grpc/grpc-go/security/advisories/GHSA-p77j-4mvh-x3m3
• https://github.com/grpc/grpc-go

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

grpc/grpc-go (google.golang.org/grpc)

v1.79.3: Release 1.79.3

Compare Source

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 an Unimplemented error. (#​8981)

v1.79.2: Release 1.79.2

Compare Source

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

Compare Source

Bug Fixes

• grpc: Remove the -dev suffix from the User-Agent header. (#​8902)

v1.79.0: Release 1.79.0

Compare Source

API Changes

• mem: Add experimental API SetDefaultBufferPool to change the default buffer pool. (#​8806)
  • Special Thanks: @​vanja-p
• experimental/stats: Update MetricsRecorder to require embedding the new UnimplementedMetricsRecorder (a no-op struct) in all implementations for forward compatibility. (#​8780)

Behavior Changes

• balancer/weightedtarget: Remove handling of Addresses and only handle Endpoints in resolver updates. (#​8841)

New Features

• experimental/stats: Add support for asynchronous gauge metrics through the new AsyncMetricReporter and RegisterAsyncReporter APIs. (#​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)
• xds: Implement :authority rewriting, as specified in gRFC A81. (#​8779)
• balancer/randomsubsetting: Implement the random_subsetting LB 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 CONNECTING state. (#​8813)
• health: Fix a bug where health checks failed for clients using legacy compression options (WithDecompressor or RPCDecompressor). (#​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 buffer objects. (#​8784)
• transport: Reduce slice re-allocations by reserving slice capacity. (#​8797)

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

[renovate-sh-app]

ℹ️ Artifact update notice

File name: collector/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 3 additional dependencies were updated

Details:

Package	Change
cel.dev/expr	v0.24.0 -> v0.25.1
github.com/cncf/xds/go	v0.0.0-20251022180443-0feb69152e9f -> v0.0.0-20251210132809-ee656c7534f5
go.opentelemetry.io/contrib/detectors/gcp	v1.38.0 -> v1.39.0

File name: extension/alloyengine/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 3 additional dependencies were updated

Details:

Package	Change
cel.dev/expr	v0.24.0 -> v0.25.1
github.com/cncf/xds/go	v0.0.0-20251022180443-0feb69152e9f -> v0.0.0-20251210132809-ee656c7534f5
go.opentelemetry.io/contrib/detectors/gcp	v1.38.0 -> v1.39.0

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 3 additional dependencies were updated

Details:

Package	Change
github.com/cncf/xds/go	v0.0.0-20251022180443-0feb69152e9f -> v0.0.0-20251210132809-ee656c7534f5
go.opentelemetry.io/contrib/detectors/gcp	v1.38.0 -> v1.39.0
cel.dev/expr	v0.24.0 -> v0.25.1

[github-actions]

🔍 Dependency Review

Below is an assessment of the dependency updates shown in the go.mod diffs. Each section summarizes any required code changes (if any), with references and suggested diffs where appropriate.

cel.dev/expr v0.24.0 -> v0.25.1 — ✅ Safe

• Scope: Indirect dependency only in this repo (no direct imports found in the provided go.mod files).
• Upstream impact: cel.dev/expr (CEL-Go) v0.x uses semantic versioning with potential changes across minor versions, but the 0.25.0–0.25.1 range contains bug fixes and internal improvements. No breaking surface-area changes are called out in the 0.25.1 patch.
• Repository impact: Since this module is not directly imported by your code, there are no repository code changes required. Any impact would be in transitive libraries that embed CEL evaluation, which typically keep compatibility across such bumps.

Evidence

• Releases: https://github.com/google/cel-go/releases (module path cel.dev/expr)
• Tags to review: v0.25.0, v0.25.1

No code changes required.

github.com/cncf/xds/go v0.0.0-20251022180443-0feb69152e9f -> v0.0.0-20251210132809-ee656c7534f5 — ✅ Safe

• Scope: Indirect dependency; this module primarily contains protobuf-generated types for xDS APIs.
• Upstream impact: Updates to the xDS protobufs; no Go logic. These are typically consumed by gRPC xDS/control-plane stacks.
• Repository impact: No direct usage in your go.mod; no code changes required in this repository. Compatibility is handled by gRPC and control-plane libraries.

Evidence

• Source: https://github.com/cncf/xds (go package github.com/cncf/xds/go)
• Nature of changes: Proto definitions only

No code changes required.

go.opentelemetry.io/contrib/detectors/gcp v1.38.0 -> v1.39.0 — ✅ Safe

• Scope: Indirect dependency.
• Upstream impact (1.39.0): Routine feature/bugfix release for resource detectors. These releases typically:
  • Add or refine detection logic for resource attributes.
  • Track upstream semconv changes.
  • Maintain API stability across minor bumps.
• Repository impact: No repository code changes required. Behavior changes are limited to what attributes are auto-detected at runtime.

Evidence

• Releases: https://github.com/open-telemetry/opentelemetry-go-contrib/releases
• Module: go.opentelemetry.io/contrib/detectors/gcp

No code changes required.

google.golang.org/grpc v1.78.0 -> v1.79.3 — ✅ Safe

• Scope: Direct dependency in root module (indirect in submodules).
• Upstream impact:
  • 1.79.x is a minor/patch series focusing on bug fixes, performance/stability improvements, and incremental xDS and resolver/balancer changes.
  • No breaking API removals were announced for this jump.
• Repository impact: No code changes are typically required. Below are sanity checks that help avoid subtle behavior issues that occasionally surface with transport or metadata validation hardening.

Things to quickly verify

• Metadata keys must be lowercase ASCII; keys ending with “-bin” must carry binary values. If you have any uppercase or non-conformant metadata keys, normalize them.

Example normalization (if needed)

- md := metadata.Pairs("Authorization", token)
+ md := metadata.Pairs("authorization", token)
  ctx := metadata.NewOutgoingContext(ctx, md)
  _, err := client.SomeCall(ctx, req)

• If you maintain any custom name resolvers or balancers (most repos don’t), ensure they still compile and behave as expected under 1.79.x. No changes are expected for standard usage.

Evidence

• Releases: https://github.com/grpc/grpc-go/releases
• Tags to review: v1.79.0, v1.79.1, v1.79.2, v1.79.3

No code changes required.

Notes

• A transitive change to github.com/envoyproxy/go-control-plane is visible in go.sum (to v0.14.0), but since it is not declared in any go.mod diff, it is outside the scope of this review per the rules. This aligns with the xDS/grpc ecosystem updates above and does not require changes in this repository.

[blewis12]

approved but waiting to merge pipeline fixes from main

[renovate-sh-app]

Rebase requested. Renovate is processing this repository now.