libsoup WebSocket Fragment Reassembly Does Not Cap Total Message Size, Allowing Heap Exhaustion via Large Fragmented Payloads
Last refreshed2026-10-30
Status: UPDATED
| Advisory ID: CVE-2026-102557
Key Details
CVE
CVE-2026-102557
CVSS Score / Version
8.6 (High) / CVSS v3.1
Updated
2026-10-29
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is low; integrity impact is low; availability impact is high.
Affected products
Red Hat Enterprise Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, and Red Hat Enterprise Linux 7
Classified as
CWE-125 (Out-of-bounds Read)
Exploitation prediction (EPSS)
0.27% probability of exploitation in the next 30 days (18% percentile) -- FIRST.org's EPSS model.
Affected Products, Subsystems & Sectors
Vendor
Product
Affected Versions
Patch Status
Red Hat
Enterprise Linux
Red Hat
Red Hat Enterprise Linux 10
Red Hat
Red Hat Enterprise Linux 8
Red Hat
Red Hat Enterprise Linux 9
Red Hat
Red Hat Enterprise Linux 7
Subsystems
OT Supporting Infrastructure
Sectors
All Sectors
What to Know
A flaw was found in libsoup. When reassembling fragmented WebSocket messages into a GByteArray, libsoup did not adequately cap total message size against the limits of the underlying buffer type. A remote peer could send fragments that caused size truncation while the implementation still used the full length, leading to heap corruption or a crash. (NVD)
What to Do
Monitor Red Hat's web page for any future patch releases.