# GRPC bump to 1.82.1

**URL:** <https://discuss.kubernetes.io/t/grpc-bump-to-1-82-1/35131>\
**Category:** General Discussions\
**Created:** [August 21, 2026, 3:29pm UTC](https://discuss.kubernetes.io/t/grpc-bump-to-1-82-1/35131 "2026-08-21T15:29:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zhe\_Yuan](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/zhe_yuan/32/18455_2.png) [@Zhe\_Yuan](https://discuss.kubernetes.io/u/Zhe_Yuan)\
**Post date:** [August 21, 2026, 3:29pm UTC](https://discuss.kubernetes.io/t/grpc-bump-to-1-82-1/35131/1 "2026-08-21T15:29:32Z")

</div>

### Cluster information:

Kubernetes version: 1.36  
Cloud being used: (put bare-metal if not on a public cloud)  
Installation method:  
Host OS:  
CNI and version:  
CRI and version:

[grpc package - google.golang.org/grpc - Go Packages](http://google.golang.org/grpc) has some high severity CVE in 1.36, and these are addressed by this bump, [Update google.golang.org/grpc to v1.82.1 by dims · Pull Request #140740 · kubernetes/kubernetes · GitHub](https://github.com/kubernetes/kubernetes/pull/140740), in 1.37 pre-release. I’d like to know is there a specific reason this is not backported to 1.36? Does this count as a breaking change? To me, the behavioral changes here are more on grpc side.