CVE-2026-0716 | Libsoup: out-of-bounds read in libsoup websocket frame processing

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.

Published: 2026-01-13 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-0716 is rated Low Risk (25.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.26%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-0716

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 0.26% +0.21%
2 2026-06-10 0.05% 0.05% -0.00%
3 2026-02-14 0.05%

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-0716

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
2.2 2.5 [email protected]

Weakness enumeration for CVE-2026-0716

OS Trackers for CVE-2026-0716

vendor priority summary link
debian not yet assigned CVE-2026-0716 not yet assigned priority: Debian including 2 source packages (libsoup2.4, libsoup3), 7 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-0716
redhat medium https://access.redhat.com/security/cve/CVE-2026-0716
suse medium CVE-2026-0716 severity moderate: SUSE including 82 source package names (13.2-9.12:libpython3_11-1_0-3.11.13-1.1, 13.2-9.12:python311-base-3.11.13-1.1, …), 222 product×package rows across 46 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/toolbox, … (46 product lines)): Fixed 218, First Fixed 4. https://www.suse.com/security/cve/CVE-2026-0716/
ubuntu medium CVE-2026-0716 medium priority: Ubuntu including 2 source packages (libsoup2.4, libsoup3), 13 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): deferred 9, ignored 2, needs-triage 2. https://ubuntu.com/security/CVE-2026-0716

Affected software / configurations for CVE-2026-0716

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-0716

cvelogic Threat Intelligence