rpcx through 1.9.3, fixed in commit 047aec1, contains a denial-of-service vulnerability in protocol.Message.Decode (protocol/message.go). When a message has the compression flag set, the payload is gzip-decompressed via util.Unzip with no limit on the decompressed output size. The only built-in size guard, protocol.MaxMessageLength, is checked against the compressed on-the-wire frame length, not the decompressed size, so it provides no protection. Because decoding (and decompression) occurs in readRequest before authentication, a single unauthenticated connection can send a small (under 2 MB) gzip-compressed message that expands to gigabytes of heap allocation, leading to out-of-memory conditions and service unavailability.
CVE-2026-59803
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- —
- EPSS
- 33.3%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 8, 2026rpcx - Denial of Service via Gzip Decompression Bomb in Wire Protocol | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rpcx-denial-of-service-via-gzip-decompression-bomb-in-wire-protocolfix(protocol): cap decompressed payload size to prevent gzip bombs (#942)
Fix merged in smallnest/rpcx PR #943 on 2026-07-07 — awaiting tagged release
https://github.com/smallnest/rpcx/pull/943Unauthenticated gzip decompression bomb in rpcx wire protocol causes multi-GB memory allocation from a single small request · Issue #942 · smallnest/rpcx · GitHub
https://github.com/smallnest/rpcx/issues/942commit 047aec18efa7 (smallnest/rpcx)
Fix landed in smallnest/rpcx commit 047aec18efa7 — awaiting tagged release
https://github.com/smallnest/rpcx/commit/047aec18efa7d037105e2b72c36dd2ae05e1acc6Vendor Advisories for CVE-2026-59803(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 39× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 00:34 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 12:58 UTCGHSA enrichment
- 2026-07-16 01:24 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 13:49 UTCGHSA enrichment
- 2026-07-15 02:13 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 14:39 UTCGHSA enrichment
- 2026-07-14 03:04 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 15:30 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 03:55 UTCGHSA enrichment
- 2026-07-12 16:21 UTCGHSA enrichment
Show 14 moreShow fewer
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 04:47 UTCGHSA enrichment
- 2026-07-11 17:13 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 05:39 UTCGHSA enrichment
- 2026-07-10 18:05 UTCGHSA enrichment
- 2026-07-10 06:30 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 18:56 UTCGHSA enrichment
- 2026-07-09 07:22 UTCGHSA enrichment
- 2026-07-08 19:46 UTCEG score recompute
- 2026-07-08 19:44 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59803?
When was CVE-2026-59803 disclosed?
Is CVE-2026-59803 actively exploited?
What is the CVSS score of CVE-2026-59803?
How do I remediate CVE-2026-59803?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59803
Is Your Infrastructure Affected by CVE-2026-59803?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.