Approved changes feed: RSS · Atom
cpe:2.3:a:smallnest:rpcx:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Smallnest (022f18a9-0953-51a9-9041-b98cd0dd14d7) |
|---|---|
| Product | Rpcx (26f7f9e5-0180-5d63-af2e-030373f8b366) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-59803 |
vulnerable | 2026-07-29 01:03:17.602593 |
rpcx - Denial of Service via Gzip Decompression Bomb in Wire Protocol
HIGH (7.5)
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.
Published: 2026-07-08T19:42:29.448Z
Updated: 2026-11-08T14:07:23.595Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.