Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven🐍 PyPI💎 RubyGems

GHSA-6628-q6j9-w8vg

HIGH

GHSA-6628-q6j9-w8vg is a high-severity (CVSS 7.5) Reachable Assertion vulnerability in io.grpc:grpc-protobuf. O3 Security confirms whether GHSA-6628-q6j9-w8vg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

gRPC Reachable Assertion issue

Also known asCVE-2023-1428PYSEC-2026-1425
Published
Jul 6, 2023
Updated
Jul 7, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

Blast Radius

3 pkgs affected
io.grpc:grpc-protobuf🐍grpcio💎grpc

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

Description

There exists an vulnerability causing an abort() to be called in gRPC.  The following headers cause gRPC's C++ implementation to abort() when called via http2:

te: x (x != trailers)

:scheme: x (x != http, https)

grpclb_client_stats: x (x == anything)

On top of sending one of those headers, a later header must be sent that gets the total header size past 8KB. We recommend upgrading past git commit 2485fa94bd8a723e5c977d55a3ce10b301b437f8 or v1.53 and above.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.grpc:grpc-protobuf1.51.0&&< 1.53.01.53.0
🐍PyPIgrpcio1.51.0&&< 1.53.01.53.0
💎RubyGemsgrpc1.51.0&&< 1.53.01.53.0

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update io.grpc:grpc-protobuf to 1.53.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6628-q6j9-w8vg is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-6628-q6j9-w8vg 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 GHSA-6628-q6j9-w8vg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

There exists an vulnerability causing an abort() to be called in gRPC.  The following headers cause gRPC's C++ implementation to abort() when called via http2: te: x (x != trailers) :scheme: x (x != http, https) grpclb_client_stats: x (x == anything) On top of sending one of those headers, a later header must be sent that gets the total header size past 8KB. We recommend upgrading past git commit 2485fa94bd8a723e5c977d55a3ce10b301b437f8 or v1.53 and above.
O3 Security · Impact-Aware SCA

Is GHSA-6628-q6j9-w8vg in your dependencies?

O3 detects GHSA-6628-q6j9-w8vg 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.