{"schema_version":"1.7.2","id":"OESA-2026-3692","modified":"2026-09-05T15:03:59Z","published":"2026-09-05T15:03:59Z","upstream":["CVE-2026-12548","CVE-2026-12549","CVE-2026-15711","CVE-2026-66338","CVE-2026-77014","CVE-2026-77680"],"summary":"libsoup security update","details":"libsoup is an HTTP client/server library for GNOME. It uses GObjects and the glib main loop, to integrate well with GNOME applications, and also has a synchronous API, for use in threaded applications.\r\n\r\nSecurity Fix(es):\n\nA heap out-of-bounds read flaw was found in libsoup. When parsing multipart HTTP messages, an integer type mismatch between the caller and soup_headers_parse() can cause the length parameter to be incorrectly truncated, leading to a heap buffer over-read. A remote attacker could use this flaw to crash an application using libsoup or potentially disclose heap memory contents.(CVE-2026-12548)\n\nThe 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.(CVE-2026-12549)\n\nA vulnerability was found in libsoup's WebSocket frame parsing implementation. The library fails to validate length rules specified in RFC 6455 §5.5, which mandates that all WebSocket control frames (e.g., PING, PONG, CLOSE) contain a payload of 125 bytes or less. A remote, unauthenticated attacker can exploit this by sending a non-compliant, oversized control frame. Because the parser handles this protocol violation improperly instead of throwing an immediate connection termination error, it triggers a internal processing crash, resulting in a remote denial of service (DoS) for applications utilizing libsoup WebSockets.(CVE-2026-15711)\n\nA flaw was found in libsoup. The chunked transfer encoding parser uses a permissive parsing function for chunk sizes that silently accepts inputs violating RFC 9112, including leading whitespace, plus sign prefixes, and trailing invalid characters. When libsoup operates behind a strict frontend proxy, this parsing differential can be exploited to smuggle HTTP requests.(CVE-2026-66338)\n\nA flaw was found in libsoup's SoupServer HTTP Range header processing. The sort_ranges() comparator in soup-message-headers.c truncates a 64-bit subtraction result to 32-bit int, flipping the sign for range offsets differing by more than INT_MAX. This causes silent omission of requested byte ranges from HTTP 206 Partial Content responses on resources larger than approximately 2 GB.(CVE-2026-77014)\n\nAn algorithmic complexity flaw exists in libsoup's HTTP Range header processing that persists after the CVE-2025-32907 fix. CVE-2025-32907 addressed memory amplification when a client repeated the same range many times in a single Range header. Commit 9bb92f7a corrected merge correctness in soup_message_headers_get_ranges_internal() in libsoup/soup-message-headers.c, but the coalescing loop still removes merged ranges using g_array_remove_index() for each coalesced element. Because GArray is contiguous, each mid-array removal performs an O(N) memmove. When many identical satisfiable ranges are supplied (for example bytes=0-0 repeated thousands of times), the loop performs O(N²) work coalescing them into a single range. The vulnerable path is reachable server-side from handle_partial_get() in libsoup/server/http1/soup-server-message-io-http1.c when a SoupServer handler returns HTTP 200 with a non-empty body. No authentication is required. The number of ranges is bounded only by the maximum request header size (~100 KiB), allowing roughly 25,000 ranges per request. This is a CPU exhaustion / availability issue only. No memory corruption or information disclosure occurs.(CVE-2026-77680)","affected":[{"package":{"ecosystem":"openEuler:24.03-LTS-SP3","name":"libsoup","purl":"pkg:rpm/openEuler/libsoup&distro=openEuler-24.03-LTS-SP3"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.74.3-25.oe2403sp3"}]}],"ecosystem_specific":{"aarch64":["libsoup-2.74.3-25.oe2403sp3.aarch64.rpm","libsoup-debuginfo-2.74.3-25.oe2403sp3.aarch64.rpm","libsoup-debugsource-2.74.3-25.oe2403sp3.aarch64.rpm","libsoup-devel-2.74.3-25.oe2403sp3.aarch64.rpm"],"noarch":["libsoup-help-2.74.3-25.oe2403sp3.noarch.rpm"],"src":["libsoup-2.74.3-25.oe2403sp3.src.rpm"],"x86_64":["libsoup-2.74.3-25.oe2403sp3.x86_64.rpm","libsoup-debuginfo-2.74.3-25.oe2403sp3.x86_64.rpm","libsoup-debugsource-2.74.3-25.oe2403sp3.x86_64.rpm","libsoup-devel-2.74.3-25.oe2403sp3.x86_64.rpm"]}}],"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3692"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-12548"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-12549"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-15711"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-66338"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77014"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77680"}],"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"}],"database_specific":{"severity":"High"}}