<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: grpc</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2026-33186: gRPC-Go is the Go language implementation of gRPC</title><link>https://patchthecve.com/cve/CVE-2026-33186.html</link><guid>https://patchthecve.com/cve/CVE-2026-33186.html</guid><pubDate>Fri, 18 Sep 2026 13:17:50 +0000</pubDate><description>CRITICAL 9.1: gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory l</description></item><item><title>CVE-2024-11407: There exists a denial of service through Data corruption in gRPC-C++ - gRPC-C++ servers with transmit zero cop</title><link>https://patchthecve.com/cve/CVE-2024-11407.html</link><guid>https://patchthecve.com/cve/CVE-2024-11407.html</guid><pubDate>Wed, 17 Jun 2026 06:57:42 +0000</pubDate><description>HIGH 7.5: There exists a denial of service through Data corruption in gRPC-C++ - gRPC-C++ servers with transmit zero copy enabled through the channel arg GRPC_ARG_TCP_TX_ZEROCOPY_ENABLED can experience data corruption issues. The data sent by the application may be corrupted before transmission over the netwo</description></item><item><title>CVE-2024-7246: It&#x27;s possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy </title><link>https://patchthecve.com/cve/CVE-2024-7246.html</link><guid>https://patchthecve.com/cve/CVE-2024-7246.html</guid><pubDate>Wed, 17 Jun 2026 08:19:41 +0000</pubDate><description>MEDIUM 5.3: It&#x27;s possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It&#x27;s also possible to use this vulnerability to leak other clients HTTP header keys, but not values.

This occurs because the err</description></item></channel></rss>