Libsoup: out-of-bounds read in libsoup websocket frame processing
Products / packages Red Hat Enterprise Linux 10 · Red Hat Enterprise Linux 6 · Red Hat Enterprise Linux 7 · 2 more
Published
Severity and exploitation
KEV coverage does not rule out exploitation.
Assessment vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:LSeverity
medium4.8CVSS measures technical severity, not the likelihood of an attack.
Known exploitation
Not listed in the checked CISA KEV catalog
Absence from CISA KEV does not rule out attacks.
Public exploit
Not established by this record
Missing evidence does not mean no public exploit exists.
Remediation
Source guidance available
Review the recorded instructions. Guidance may be a workaround rather than a fixed version.
What this means
Libsoup has an out-of-bounds read weakness in WebSocket frame processing when the maximum incoming payload size is unset. This can cause memory exposure or a crash in affected Red Hat Enterprise Linux versions. Local access is required.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Attack conditions
No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.
Review supporting sources →Affected versions
Check the exact model, release, and any platform requirements against your installation.
Red Hat · redhat
Red Hat Enterprise Linux 10
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 10
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:enterprise_linux:10Red Hat · redhat
Red Hat Enterprise Linux 6
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 6
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: unaffected
Product identifiers (CPE)
cpe:/o:redhat:rhel_els:6Red Hat · redhat
Red Hat Enterprise Linux 7
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 7
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/o:redhat:rhel_els:7Red Hat · redhat
Red Hat Enterprise Linux 8
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 8
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:enterprise_linux:8Red Hat · redhat
Red Hat Enterprise Linux 9
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 9
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:enterprise_linux:9What to do
Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.
To mitigate this issue, applications utilizing libsoup's WebSocket support should ensure that the max_incoming_payload_size is explicitly set to a non-zero value. This prevents the library from processing WebSocket frames with an unset or zero maximum payload size, which can lead to out-of-bounds reads. Consult application-specific documentation for configuring libsoup parameters.
cve.new guidance unless attributed to a publisher. This page does not inspect your installation.
Public exploit evidence
No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.
Original source description
Read the full publisher description
A flaw was found in libsoup’s WebSocket frame processing when handling incoming messages. If a non-default configuration is used where the maximum incoming payload size is unset, the library may read memory outside the intended bounds. This can cause unintended memory exposure or a crash. Applications using libsoup’s WebSocket support with this configuration may be impacted.
References
3 sourcesInside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-0716View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Source updated
Latest modification date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.