golang-google-grpc - Debian Package Tracker

general

source: golang-google-grpc (main)
version: 1.81.1-1
maintainer: Debian Go Packaging Team (DMD)
uploaders: Tim Potter [DMD] – Martina Ferrari [DMD] – Dmitry Smirnov [DMD]
arch: all any
std-ver: 4.7.4
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1.27.1-1
oldstable: 1.33.3-2
stable: 1.64.0-7
testing: 1.79.3-1
unstable: 1.81.1-1

versioned links

1.27.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.33.3-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.64.0-7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.79.3-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.81.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

golang-google-grpc-dev (1 bugs: 0, 1, 0, 0)
protoc-gen-go-grpc

action needed

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 2-day delay is over. Check why.

Created: 2026-05-29 Last update: 2026-05-31 17:32

1 new commit since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 48aacd744b6fbd809ccf63ad98ba2ec095a1c192
Merge: dacac260 8cc1171a
Author: Andrew Lee (李健秋) <ajqlee@debian.org>
Date:   Mon May 25 13:57:29 2026 +0200

    Merge branch 'debian/sid' into 'debian/sid'
    
    New upstream version 1.81.1
    
    See merge request go-team/packages/golang-google-grpc!6

Created: 2026-05-25 Last update: 2026-05-26 10:32

lintian reports 3 warnings normal

Lintian reports 3 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2026-04-10 Last update: 2026-05-26 00:01

1 low-priority security issue in trixie low

There is 1 open security issue in trixie.

1 issue left for the package maintainer to handle:

CVE-2026-33186: (needs triaging) gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have 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. This affects gRPC-Go servers that 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)`; AND that have a 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. The fix in version 1.79.3 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. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.

You can find information about how to handle this issue in the security team's documentation.

Created: 2026-03-29 Last update: 2026-05-25 16:00

1 low-priority security issue in bookworm low

There is 1 open security issue in bookworm.

1 issue left for the package maintainer to handle:

CVE-2026-33186: (needs triaging) gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have 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. This affects gRPC-Go servers that 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)`; AND that have a 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. The fix in version 1.79.3 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. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.

You can find information about how to handle this issue in the security team's documentation.

Created: 2026-03-29 Last update: 2026-05-25 16:00

testing migrations

excuses:
- Migration status: Blocked. Can't migrate due to a non-migratable dependency. Check status below.
- Blocked by: golang-opentelemetry-otel
- Migration status for golang-google-grpc (1.79.3-1 to 1.81.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- ∙ ∙ Built-Using: golang-google-grpc golang-opentelemetry-otel (not considered)
- ∙ ∙ Invalidated by built-using
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-google-grpc.html
- ∙ ∙ Autopkgtest for golang-google-grpc/1.81.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ Required age reduced by 3 days because of autopkgtest
- ∙ ∙ 6 days old (needed 2 days)
- Not considered

news

[rss feed]

[2026-05-25] Accepted golang-google-grpc 1.81.1-1 (source) into unstable (Juan Manuel Méndez Rey) (signed by: 李健秋 Andrew Lee)
[2026-04-16] golang-google-grpc 1.79.3-1 MIGRATED to testing (Debian testing watch)
[2026-04-10] Accepted golang-google-grpc 1.79.3-1 (source) into unstable (Andrew Lee (李健秋)) (signed by: 李健秋 Andrew Lee)
[2025-12-29] Accepted golang-google-grpc 1.75.1-1 (source) into experimental (Andrew Lee (李健秋)) (signed by: Sakirnth Nagarasa)
[2025-10-15] golang-google-grpc 1.66.3-2 MIGRATED to testing (Debian testing watch)
[2025-10-12] Accepted golang-google-grpc 1.66.3-2 (source) into unstable (Reinhard Tartler)
[2025-10-11] Accepted golang-google-grpc 1.66.3-1 (source) into experimental (Reinhard Tartler)
[2025-05-15] golang-google-grpc 1.64.0-7 MIGRATED to testing (Debian testing watch)
[2025-05-15] golang-google-grpc 1.64.0-7 MIGRATED to testing (Debian testing watch)
[2025-05-05] Accepted golang-google-grpc 1.64.0-7 (source) into unstable (Andrej Shadura) (signed by: Andrew Shadura)
[2024-08-07] golang-google-grpc 1.64.0-6 MIGRATED to testing (Debian testing watch)
[2024-08-04] Accepted golang-google-grpc 1.64.0-6 (source) into unstable (Mathias Gibbens)
[2024-07-30] Accepted golang-google-grpc 1.64.0-5 (source) into unstable (Mathias Gibbens)
[2024-07-29] Accepted golang-google-grpc 1.64.0-4 (source) into unstable (Mathias Gibbens)
[2024-07-27] Accepted golang-google-grpc 1.64.0-3 (source) into unstable (Mathias Gibbens)
[2024-07-25] Accepted golang-google-grpc 1.64.0-2 (source) into unstable (Mathias Gibbens)
[2024-06-22] Accepted golang-google-grpc 1.64.0-1 (source) into experimental (Reinhard Tartler)
[2024-01-22] Accepted golang-google-grpc 1.60.1-2 (source) into experimental (Simon Josefsson)
[2024-01-22] Accepted golang-google-grpc 1.60.1-1 (source) into experimental (Simon Josefsson)
[2024-01-18] Accepted golang-google-grpc 1.59.0-1 (source) into experimental (Simon Josefsson)
[2023-07-10] golang-google-grpc 1.38.0+really1.33.3-1 MIGRATED to testing (Debian testing watch)
[2023-07-05] Accepted golang-google-grpc 1.38.1-1 (source) into experimental (Anthony Fok)
[2023-07-05] Accepted golang-google-grpc 1.38.0+really1.33.3-1 (source) into unstable (Anthony Fok)
[2023-06-23] Accepted golang-google-grpc 1.38.0-5 (source) into unstable (Thomas Goirand)
[2023-01-17] golang-google-grpc 1.33.3-2 MIGRATED to testing (Debian testing watch)
[2023-01-10] Accepted golang-google-grpc 1.33.3-2 (source) into unstable (Shengjing Zhu)
[2023-01-02] golang-google-grpc 1.33.3-1 MIGRATED to testing (Debian testing watch)
[2022-12-31] Accepted golang-google-grpc 1.33.3-1 (source) into unstable (Shengjing Zhu)
[2022-12-31] golang-google-grpc 1.32.0-5 MIGRATED to testing (Debian testing watch)
[2022-12-31] golang-google-grpc 1.32.0-5 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 2
RC: 0
I&N: 1
M&W: 1
F&P: 0
patch: 0

links

homepage
lintian (0, 3)
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.66.3-2
1 bug (1 patch)