CVE-2026-59803
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 34% of all known CVEs.
References
Related Vulnerabilities
Other CWE-409 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2026-49975 | High | 7.5 | 28% | - | Fix |
| CVE-2026-21441 | High | 7.5 | 2.7% | - | Fix |
| CVE-2024-43499 | High | 7.5 | 2.6% | - | Fix |
| CVE-2024-28180 | Medium | 4.3 | 2.0% | - | Fix |
| CVE-2017-16129 | Medium | 5.9 | 1.8% | - | Fix |
| CVE-2022-29225 | High | 7.5 | 1.5% | - | Fix |
Common questions
How do I fix CVE-2026-59803?
No published fix for CVE-2026-59803 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-59803 being actively exploited?
Not that we know of. CVE-2026-59803 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.41% is the estimated probability that it will be exploited in the next 30 days. That is higher than 34% of all scored CVEs.
How severe is CVE-2026-59803?
CVE-2026-59803 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-59803
Markdown
[](https://tridentstack.com/cve/CVE-2026-59803)HTML
<a href="https://tridentstack.com/cve/CVE-2026-59803"><img src="https://tridentstack.com/cve/badge/CVE-2026-59803.svg" alt="CVE-2026-59803"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-10.