CVE-2023-32731: PYSEC-2026-1427 - Connection confusion in gRPC

Quick answers

Is CVE-2023-32731 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2023-32731 being exploited in the wild.

How severe is CVE-2023-32731?

Low severity, with a CVSS score of 3.1, published 7 July 2026.

Which products and versions are affected?

io.grpc:grpc-protobuf (Maven) ECOSYSTEM:introduced=1.53.0,fixed=1.53.1; grpcio (PyPI) ECOSYSTEM:introduced=1.53.0,fixed=1.53.1, ECOSYSTEM:introduced=1.53.0,fixed=1.53.1,introduced=1.54.0,fixed=1.54.2; grpc (RubyGems) ECOSYSTEM:introduced=1.53.0,fixed=1.53.1.

Is there a fix for CVE-2023-32731?

Yes. io.grpc:grpc-protobuf (Maven): upgrade to 1.53.1 or later; grpcio (PyPI): upgrade to 1.53.1, 1.54.2 or later; grpc (RubyGems): upgrade to 1.53.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2023-32731?

Check whether you run io.grpc:grpc-protobuf (Maven), grpcio (PyPI) or grpc (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• io.grpc:grpc-protobuf (Maven): upgrade to 1.53.1 or later

  # set io.grpc:grpc-protobuf to 1.53.1 in your pom.xml or build.gradle

• grpcio (PyPI): upgrade to 1.53.1, 1.54.2 or later

  pip install "grpcio>=1.54.2"

• grpc (RubyGems): upgrade to 1.53.1 or later

  bundle update grpc

Affected products

• io.grpc:grpc-protobuf (Maven) ECOSYSTEM:introduced=1.53.0,fixed=1.53.1
• grpcio (PyPI) ECOSYSTEM:introduced=1.53.0,fixed=1.53.1, ECOSYSTEM:introduced=1.53.0,fixed=1.53.1,introduced=1.54.0,fixed=1.54.2
• grpc (RubyGems) ECOSYSTEM:introduced=1.53.0,fixed=1.53.1

Identifiers

• CVE-2023-32731
• GHSA-cfgp-2977-2fmm
• PYSEC-2026-1427