Update google.golang.org/grpc (indirect) to v1.79.3 [SECURITY] (forgejo) #12794
No reviewers
forgejo/Reviewers
Labels
No labels
arch
riscv64
backport/v1.19
backport/v1.20
backport/v1.21/forgejo
backport/v10.0/forgejo
backport/v11.0/forgejo
backport/v12.0/forgejo
backport/v13.0/forgejo
backport/v14.0/forgejo
backport/v15.0/forgejo
backport/v7.0/forgejo
backport/v8.0/forgejo
backport/v9.0/forgejo
breaking
bug
bug
confirmed
bug
duplicate
bug
needs-more-info
bug
new-report
bug
reported-upstream
code/actions
code/api
code/auth
code/auth/faidp
code/auth/farp
code/email
code/federation
code/git
code/migrations
code/packages
code/wiki
database
MySQL
database
PostgreSQL
database
SQLite
dependency-upgrade
dependency
Chi
dependency
Chroma
dependency
F3
dependency
ForgeFed
dependency
garage
dependency
Gitea
dependency
Golang
Discussion
duplicate
enhancement/feature
forgejo/accessibility
forgejo/branding
forgejo/ci
forgejo/commit-graph
forgejo/documentation
forgejo/furnace cleanup
forgejo/i18n
forgejo/interop
forgejo/moderation
forgejo/privacy
forgejo/release
forgejo/scaling
forgejo/security
forgejo/ui
Gain
High
Gain
Nice to have
Gain
Undefined
Gain
Very High
good first issue
i18n/backport-stable
impact
large
impact
medium
impact
small
impact
unknown
Incompatible license
issue
closed
issue
do-not-exist-yet
issue
open
manual test
Manually tested during feature freeze
OS
FreeBSD
OS
Linux
OS
macOS
OS
Windows
problem
QA
regression
release blocker
Release Cycle
Feature Freeze
release-blocker
v7.0
release-blocker
v7.0.1
release-blocker
v7.0.2
release-blocker
v7.0.3
release-blocker
v7.0.4
release-blocker
v8.0.0
release-blocker/v9.0.0
run-all-playwright-tests
run-end-to-end-tests
stage
2-research
stage
3-design
stage
4-implementation
test
manual
test
needed
test
needs-help
test
not-needed
test
present
untested
User research - time-tracker
valuable code
worth a release-note
User research - Accessibility
User research - Blocked
User research - Community
User research - Config (instance)
User research - Errors
User research - Filters
User research - Future backlog
User research - Git workflow
User research - Labels
User research - Moderation
User research - Needs input
User research - Notifications/Dashboard
User research - Rendering
User research - Repo creation
User research - Repo units
User research - Security
User research - Settings (in-app)
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/forgejo!12794
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/forgejo-go-google.golang.org-grpc-vulnerability"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.75.0→v1.79.3gRPC-Go has an authorization bypass via missing leading slash in :path
CVE-2026-33186 / GHSA-p77j-4mvh-x3m3 / GO-2026-4762
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
:pathpseudo-header.The gRPC-Go server was too lenient in its routing logic, accepting requests where the
:pathomitted the mandatory leading slash (e.g.,Service/Methodinstead of/Service/Method). While the server successfully routed these requests to the correct handler, authorization interceptors (including the officialgrpc/authzpackage) 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:
google.golang.org/grpc/authzor custom interceptors relying oninfo.FullMethodorgrpc.Method(ctx).The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed
:pathheaders 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
:paththat does not start with a leading slash is immediately rejected with acodes.Unimplementederror, preventing it from reaching authorization interceptors or handlers with a non-canonical path string.Users should upgrade to the following versions (or newer):
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:
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
:pathheader 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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Authorization bypass in gRPC-Go via missing leading slash in :path in google.golang.org/grpc
CVE-2026-33186 / GHSA-p77j-4mvh-x3m3 / GO-2026-4762
More information
Details
Authorization bypass in gRPC-Go via missing leading slash in :path in google.golang.org/grpc
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Release Notes
grpc/grpc-go (google.golang.org/grpc)
v1.79.3: Release 1.79.3Compare Source
Security
grpc/authz. Any request with a non-canonical path is now immediately rejected with anUnimplementederror. (#8981)v1.79.2: Release 1.79.2Compare Source
Bug Fixes
v1.79.1: Release 1.79.1Compare Source
Bug Fixes
-devsuffix from the User-Agent header. (#8902)v1.79.0: Release 1.79.0Compare Source
API Changes
SetDefaultBufferPoolto change the default buffer pool. (#8806)MetricsRecorderto require embedding the newUnimplementedMetricsRecorder(a no-op struct) in all implementations for forward compatibility. (#8780)Behavior Changes
Addressesand only handleEndpointsin resolver updates. (#8841)New Features
AsyncMetricReporterandRegisterAsyncReporterAPIs. (#8780)GRPC_EXPERIMENTAL_PF_WEIGHTED_SHUFFLING. (#8864):authorityrewriting, as specified in gRFC A81. (#8779)random_subsettingLB policy, as specified in gRFC A68. (#8650)Bug Fixes
CONNECTINGstate. (#8813)WithDecompressororRPCDecompressor). (#8765)Performance Improvements
bufferobjects. (#8784)v1.78.0: Release 1.78.0Compare Source
Behavior Changes
Unknownon malformed grpc-status. (#8735)New Features
experimental.AcceptCompressorsso callers can restrict thegrpc-accept-encodingheader advertised for a call. (#8718)Bug Fixes
StringMatcherwhere regexes would match incorrectly when ignore_case is set to true. (#8723)OnFinishcall option not being invoked for RPCs where stream creation failed. (#8710)Performance Improvements
v1.77.0: Release 1.77.0Compare Source
API Changes
Readerinterface with a struct for better performance and maintainability. (#8669)Behavior Changes
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
resource-not-founderrors, causing the gRPC client channel to move toTransientFailure. (#8605)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)pick_firstbut don't set endpoints. (#8610)Performance Improvements
New Features
grpc.lb.backend_servicein per-call metrics (#8637)GRPC_EXPERIMENTAL_XDS_BOOTSTRAP_CALL_CREDS=trueto enable this feature. (#8536)v1.76.0: Release 1.76.0Compare Source
Dependencies
Bug Fixes
INTERNALwhen a server sends zero response messages for a unary or client-streaming RPC. (#8523)INTERNALinstead ofUNKNOWNupon receiving http headers with status 1xx andEND_STREAMflag set. (#8518)IDLEstate on backend address change. (#8615)New Features
credentials/jwtpackage providing file-based JWT PerRPCCredentials (A97). (#8431)Performance Improvements
v1.75.1: Release 1.75.1Compare Source
Bug Fixes
Configuration
📅 Schedule: (UTC)
* 0-3 * * *)🚦 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.
This PR has been generated by Mend Renovate.
ℹ️ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the
go getcommand, which resulted in the following additional change(s):Details:
cloud.google.com/go/compute/metadatav0.7.0->v0.9.0google.golang.org/genproto/googleapis/rpcv0.0.0-20250825161204-c5933d9347a5->v0.0.0-20251202230838-ff82c1b0f217No impact from the security defect, as the grpc library isn't used as a server in Forgejo (connectrpc, a different but similar library, is used for Runner->Forgejo comms). But, approving the upgrade for cleanliness and no reason not to.