CVE-2026-12549: Libsoup2.4 · The fix for CVE-2026-2443 was regressed by a subsequent rework commit that replaced
Affects libsoup2.4Source GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 4.8 Medium · fixed in 3.0.7-0ubuntu1+esm9 : update libsoup2.4 when convenient.
Data as of 3 Nov 2026, 23:14 UTC
- Patch
- Available – fixed in 3.0.7-0ubuntu1+esm9, 3.4.4-5ubuntu0.9, 3.6.6-1ubuntu3 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 22 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10libsoup2.4pkg:deb/ubuntu/libsoup2.4?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10libsoup3pkg:deb/ubuntu/libsoup3?arch=source&distro=stonkingOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlibsoup3pkg:deb/ubuntu/libsoup3?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu Pro 26.04 LTSlibsoup2.4pkg:deb/ubuntu/libsoup2.4?arch=source&distro=esm-apps/resoluteOther threats | Affected
| Fixed in– |
Ubuntu 25.10libsoup2.4pkg:deb/ubuntu/libsoup2.4?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10libsoup3pkg:deb/ubuntu/libsoup3?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The fix for CVE-2026-2443 was regressed by a subsequent rework commit that replaced specific overflow checks with a general signed comparison. When a client sends a Range request with a suffix length exceeding the content size, the resulting negative start value is not properly clamped, leading to malformed HTTP 206 responses and log flooding.