Vulnerability · CVE-2026-102557
A flaw was found in libsoup.
Published Sep 29, 2026 · catalog updated Oct 15, 2026 · A flaw was found
Check if you run it
No confirmed exploitation is on record for CVE-2026-102557. EPSS is 0.27%. Act only if a listed version of A flaw was found is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (A flaw was found).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High8.6
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.27%
- Remediation
- Advisory link
- Affected products
- cpe gnome/libsoup · cpe redhat/enterprise linux · vendor Red Hat Red Hat Enterprise Linux 10 · vendor Red Hat Red Hat Enterprise Linux 6 · vendor Red Hat Red Hat Enterprise Linux 7 · vendor Red Hat Red Hat Enterprise Linux 8
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe gnome/libsoupversion unspecified
- cpe redhat/enterprise linux10.0
- cpe redhat/enterprise linux7.0
- cpe redhat/enterprise linux8.0
- cpe redhat/enterprise linux9.0
- vendor Red Hat Red Hat Enterprise Linux 10version unspecified
- vendor Red Hat Red Hat Enterprise Linux 6version unspecified
- vendor Red Hat Red Hat Enterprise Linux 7version unspecified
- vendor Red Hat Red Hat Enterprise Linux 8version unspecified
- vendor Red Hat Red Hat Enterprise Linux 9version unspecified
How to fix CVE-2026-102557
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-102557. EPSS is 0.27%. Act only if a listed version of A flaw was found is installed.
Which versions are affected?
Compare what you have installed with redhat/enterprise linux 10.0; redhat/enterprise linux 7.0; redhat/enterprise linux 8.0; redhat/enterprise linux 9.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-125: Out-of-bounds Read. EPSS 0.27%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Sep 29, 2026 · NIST NVD
Detected
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.
Oct 15, 2026 · NIST NVD
Updated
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.
Oct 15, 2026 · NIST NVD
Updated
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.
Oct 15, 2026 · NIST NVD
Updated
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.
Sources
- CIRCL Vulnerability LookupVulnerability recordCVE-2026-102557
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 implementat
vulnerability.circl.lu - CVE.orgVulnerability recordCVE-2026-102557
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-102557
30-day exploitation probability 0.3%
first.org - JVN iPediaGovernment advisoryCVE-2026-102557
libsoupに脆弱性が発見されました。分割されたWebSocketメッセージをGByteArrayに再構成する際、libsoupは基盤となるバッファ型の制限に対してメッセージの総サイズを十分に制限していませんでした。リモートのピアは、サイズの切り捨てを引き起こす断片を送信でき、その実装は依然としてフルサイズを使用するため、ヒープの破損やクラッシュを引き起こす可能性があります。
jvndb.jvn.jp - NIST NVDVulnerability recordCVE-2026-102557
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 implementat
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.