How severe is CVE-2023-32732?

CVE-2023-32732 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-32732?

CVE-2023-32732 affects the following packages: io.grpc:grpc-protobuf (Maven), io.grpc:grpc-protobuf (Maven), grpcio (PyPI), grpcio (PyPI), grpc (RubyGems), grpc (RubyGems). Ecosystems affected: Maven, PyPI, RubyGems.

How do I fix CVE-2023-32732?

Update io.grpc:grpc-protobuf to 1.53.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-32732 is resolved across your whole dependency graph.

How do I detect CVE-2023-32732 in my Maven, PyPI, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.grpc:grpc-protobuf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2023-32732 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2023-32732?

O3 pinpoints whether CVE-2023-32732 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2023-32732 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-32732 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-32732?

CVE-2023-32732 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-32732?

CVE-2023-32732 is classified as CWE-440 (CWE-440). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-32732 published, and has it been updated?

CVE-2023-32732 was published on June 9, 2023 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven🐍 PyPI💎 RubyGems

CVE-2023-32732

MEDIUM

gRPC connection termination issue

Also known asGHSA-9hxf-ppjv-w6rq

Published

Jun 9, 2023

Updated

Apr 10, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk41th percentile+0.51%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

☕io.grpc:grpc-protobuf☕io.grpc:grpc-protobuf🐍grpcio🐍grpcio💎grpc💎grpc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI packages — download data is not available via public APIs for these ecosystems.

Description

gRPC contains a vulnerability whereby a client can cause a termination of connection between a HTTP2 proxy and a gRPC server: a base64 encoding error for -bin suffixed headers will result in a disconnection by the gRPC server, but is typically allowed by HTTP2 proxies. We recommend upgrading beyond the commit in https://github.com/grpc/grpc/pull/32309 https://www.google.com/url

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.grpc:grpc-protobuf`	≥ 1.53.0&&< 1.53.1	1.53.1
☕Maven	`io.grpc:grpc-protobuf`	≥ 1.54.0&&< 1.54.2	1.54.2
🐍PyPI	`grpcio`	≥ 1.53.0&&< 1.53.1	1.53.1
🐍PyPI	`grpcio`	≥ 1.54.0&&< 1.54.2	1.54.2
💎RubyGems	`grpc`	≥ 1.53.0&&< 1.53.1	1.53.1
💎RubyGems	`grpc`	≥ 1.54.0&&< 1.54.2	1.54.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.grpc:grpc-protobuf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.grpc:grpc-protobuf to 1.53.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-32732 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2023-32732 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-32732. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

gRPC contains a vulnerability whereby a client can cause a termination of connection between a HTTP2 proxy and a gRPC server: a base64 encoding error for `-bin` suffixed headers will result in a disconnection by the gRPC server, but is typically allowed by HTTP2 proxies. We recommend upgrading beyond the commit in https://github.com/grpc/grpc/pull/32309 https://www.google.com/url

O3 Security · Impact-Aware SCA

Is CVE-2023-32732 in your dependencies?

O3 detects CVE-2023-32732 across Maven, PyPI, RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works