gRPC-Go is a widely used RPC library; this remote crash vulnerability can disrupt many production services across organizations.
CVE-2026-84445
Malformed RPC in gRPC-Go can crash servers (remote DoS); update to 1.82.2/1.83.2
Is CVE-2026-84445 being exploited?
Not confirmed. CVE-2026-84445 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-84445?
CVE-2026-84445 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-84445?
Yes. A fix has been recorded for CVE-2026-84445. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84445 affect?
CVE-2026-84445 affects gRPC-Go versions prior to 1.82.2 and 1.83.2, Servers created with xds.NewGRPCServer(), Applications using gRPC-Go for RPC services. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84445?
Upgrade to gRPC-Go 1.82.2 or 1.83.2; enforce mTLS and block malformed requests
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can send an RPC missing :authority/Host to trigger an index-out-of-bounds panic and terminate the server process (remote DoS). Unauthenticated unless strict mTLS.
Immediate action required
- affected< 1.82.2
- affected>= 1.83.0 and < 1.83.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.