CVE-2023-32731: Connection confusion in gRPC

Grpc.Core Updated 02 Oct 2025

Summary

05/07/2023
Yes i
High
7.4

CVE-2023-32731: Connection confusion in gRPC. Affects Grpc.Core versions < 2.52.0. Fixed in 2.52.0. How to fix ↓

Also tracked for

The same CVE-2023-32731 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gRPC package is a high-performance, open-source framework developed by Google for building distributed systems. It provides a powerful and efficient way to connect and communicate between services using remote procedure calls (RPCs). gRPC supports multiple programming languages and is widely used in various applications and platforms.

Vulnerability Detail

The vulnerability in gRPC arises from a connection confusion issue within the HTTP2 stack. When the stack encounters a header size exceeded error, it stops parsing the rest of the HPACK frame. This behavior leads to a desynchronization of HPACK tables between the sender and receiver, particularly when used between a proxy and a backend. An attacker can leverage this vulnerability to cause requests from the proxy to be interpreted as containing headers from different proxy clients. This can result in an information leak that may be exploited for privilege escalation or data exfiltration.

How To Fix

Latest published version: 2.46.6 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.52.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

The gRPC package is susceptible to a connection confusion vulnerability that can result in an information leak. It is crucial to upgrade to a fixed version of gRPC (2.52.0 or above) to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Grpc.Core →

Share this vulnerability

FAQ

gRPC is an open-source framework developed by Google for building distributed systems using remote procedure calls (RPCs). It provides high-performance and efficient communication between services.

The vulnerability can lead to an information leak, allowing an attacker to escalate privileges or exfiltrate data by manipulating headers in requests.

To fix this vulnerability, you should upgrade to a version of gRPC that includes the necessary fix. Specifically, versions 2.52.0 and above contain the fix.

No specific workarounds have been provided for this vulnerability.

You can find more information about this vulnerability in the GitHub advisory database: [link to the advisory]

Related vulnerabilities

Recent vulnerabilities recorded for Grpc.Core.

How To Fix

Latest published version: 2.46.6 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.52.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback