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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alma_linux | — | Upgrade libsoupUpgrade libsoup-devel | Oct 15, 2026 | Oct 15, 2026 |
| Amazon Linux Ami 2 | — | Upgrade libsoup-debuginfoUpgrade libsoup-develUpgrade libsoup | Oct 19, 2026 | Oct 19, 2026 |
| Amazon_linux_2023 | — | Upgrade libsoup-docUpgrade libsoupUpgrade libsoup-debuginfoUpgrade libsoup-debugsourceUpgrade libsoup-devel | Oct 13, 2026 | Sep 29, 2026 |
| Redhat_linux | — | Upgrade libsoup3-debugsourceUpgrade libsoup-develUpgrade libsoupUpgrade libsoup3-develUpgrade libsoup-debuginfoUpgrade libsoup3Upgrade libsoup3-docNo solution existsUpgrade libsoup-debugsourceUpgrade libsoup3-debuginfo | Oct 1, 2026 | Sep 3, 2026 |
| Rocky_linux | — | Upgrade libsoup-debugsourceUpgrade libsoupUpgrade libsoup-debuginfoUpgrade libsoup-devel | Oct 19, 2026 | Oct 16, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub