Skip to content

[AV-142872] Fix critical issue in google.golang.org/grpc via minor version upgrade from 1.56.3 to 1.79.3 - #21

Closed
aikido-autofix[bot] wants to merge 1 commit into
mainfrom
fix/aikido-security-AV-142872-update-packages-106733879-mmkw
Closed

[AV-142872] Fix critical issue in google.golang.org/grpc via minor version upgrade from 1.56.3 to 1.79.3#21
aikido-autofix[bot] wants to merge 1 commit into
mainfrom
fix/aikido-security-AV-142872-update-packages-106733879-mmkw

Conversation

@aikido-autofix

@aikido-autofix aikido-autofix Bot commented Sep 6, 2026

Copy link
Copy Markdown

Jira

Pull Request Category

  • 🚀 New Functionality
  • 🐛 Bug Fix
  • 📚 Documentation
  • ♻️ Refactor
  • 🚄 Performance Improvements
  • ⏪ Revert
  • 🏛️ Infrastructure
  • 📦 Release
  • ⚙️ Build, Merge, CI or CD

Testing Approach

How was this change tested and do you have evidence?

  • Unit
  • Functional with cbclocal
  • E2E Tests
  • Sandbox
  • Una

Upgrade gRPC-Go to fix critical authorization bypass vulnerability caused by improper HTTP/2 :path validation allowing attackers to bypass path-based security policies.

✅ 1 CVE resolved by this upgrade, including 1 critical 🚨 CVE

This PR will resolve the following CVEs:

Issue Severity           Description
CVE-2026-33186
🚨 CRITICAL
[google.golang.org/grpc] Improper HTTP/2 :path validation allows requests without leading slashes to bypass path-based authorization interceptors, enabling attackers to circumvent "deny" rules and access restricted gRPC methods. This authorization bypass affects servers using path-based RBAC policies with fallback "allow" rules.
🔗 Related Tasks

@aikido-autofix aikido-autofix Bot added aikido Label created by Aikido AutoFix capella-scrum Label created by Aikido AutoFix control-plane Label created by Aikido AutoFix security Label created by Aikido AutoFix labels Sep 6, 2026
allabalakrishna9 added a commit that referenced this pull request Sep 6, 2026
Folds in the third Aikido AutoFix PR (#21, AV-142872), which proposed
grpc 1.56.3 -> 1.79.3 but was generated against main and so would have
downgraded what this branch already fixes:

  x/net    v0.58.0 -> v0.48.0   (0 advisories -> 9)
  x/crypto v0.55.0 -> v0.46.0   (3 advisories -> 30)
  go       1.25.0  -> 1.24.0

That is 36 advisories re-introduced to gain 4.

Taking grpc v1.83.2 rather than the v1.79.3 that PR proposed. v1.79.3
still carries 3 advisories, including GHSA-vp52-pcj8-j9qc (heap
exhaustion via HTTP/2 DATA frame fragmentation) and the xDS RBAC issues.
v1.83.2 has none, and it requires exactly what this branch already sets:
go 1.25.0, x/net v0.58.0, x/sys v0.47.0, x/text v0.41.0. No downgrade and
no extra toolchain change.

  google.golang.org/grpc     v1.56.3 -> v1.83.2   (5 advisories -> 0)
  google.golang.org/protobuf v1.30.0 -> v1.36.12  (2 advisories -> 0)
  github.com/golang/protobuf v1.5.3  -> v1.5.4
  github.com/google/uuid     v1.3.0  -> v1.6.0

Verified with go build ./... (clean).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@allabalakrishna9

Copy link
Copy Markdown

Superseded by #20, which now carries the grpc and protobuf bumps as well.

This PR was generated against main and could not see #20 (already open, x/net → v0.58.0 and x/crypto → v0.55.0). Both edit go.mod, so merging this one afterwards would have downgraded what #20 fixes:

Module #20 This PR Effect
golang.org/x/net v0.58.0 — 0 advisories v0.48.0 — 9 advisories +9 re-introduced
golang.org/x/crypto v0.55.0 — 3 advisories v0.46.0 — 30 advisories +27 re-introduced
go directive 1.25.0 1.24.0 downgrade

That is 36 advisories re-introduced to gain 4.

The grpc work itself was worth keeping and has been folded into #20, at a higher version than proposed here:

  • grpc v1.83.2 rather than v1.79.3. v1.79.3 still carries 3 advisories, including GHSA-vp52-pcj8-j9qc (heap exhaustion via HTTP/2 DATA frame fragmentation) and the xDS RBAC issues. v1.83.2 has none, and requires exactly what [AV-142878] Bump golang.org/x/*, grpc and protobuf to clear critical advisories #20 already sets — go 1.25.0, x/net v0.58.0, x/sys v0.47.0, x/text v0.41.0 — so it folds in with no downgrade and no extra toolchain change.
  • protobuf v1.36.12 (2 advisories → 0), plus golang/protobuf v1.5.4 and uuid v1.6.0 as proposed here.

Also worth noting: this PR moved the go directive to 1.24.0 but left the Dockerfile at FROM golang:1.21, which would have broken the image build — the same issue Copilot raised on #18 and #19. #20 carries the golang:1.25 fix.

Closing. AV-142872 stays open and is linked from #20.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aikido Label created by Aikido AutoFix capella-scrum Label created by Aikido AutoFix control-plane Label created by Aikido AutoFix security Label created by Aikido AutoFix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant