Libsoup (<= 3.x) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/libsoup--3.x/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 29 Sep 2026 18:29:03 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgOut-of-Bounds Read Vulnerability in libsoup data URI handlinghttps://feed.craftedsignal.io/briefs/2026-09-libsoup-data-uri-vulnerability/Tue, 29 Sep 2026 18:29:03 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-libsoup-data-uri-vulnerability/A memory corruption vulnerability in the libsoup soup_uri_decode_data_uri function allows for out-of-bounds reads or application crashes when processing crafted data URI payloads.A memory safety vulnerability, identified as CVE-2026-102555, exists within the libsoup library, specifically in the soup_uri_decode_data_uri() function. The library incorrectly handles base64 data-URI payloads by treating them as NUL-terminated strings during the invocation of g_base64_decode_inplace(). When a percent-decoded payload contains embedded NUL bytes, the function fails to correctly initialize the decoded length. This uninitialized length is subsequently used as the size for the returned GBytes object, leading to an out-of-bounds memory read. An attacker capable of influencing the data URIs processed by a libsoup-based application can trigger an application crash, potentially leading to a denial-of-service condition or information disclosure from the process memory space. This vulnerability impacts applications relying on libsoup for URI and network data processing on Linux environments.

Impact

Successful exploitation of this vulnerability can result in the crash of any service or application utilizing the libsoup library to parse data URIs, causing denial-of-service. Furthermore, the out-of-bounds read may allow an attacker to access sensitive information residing in the memory adjacent to the improperly handled buffer, which could facilitate more complex exploitation in the context of the vulnerable application's privileges.

Recommendation

  1. Identify all applications and services within the environment that utilize the libsoup library.
  2. Monitor vendor security advisories from the GNOME project and distributions (e.g., Debian, Fedora, RHEL) for the release of patched libsoup versions.
  3. Update libsoup to the vendor-provided patched version immediately upon availability.
  4. Implement memory-safe coding practices in downstream applications that pass untrusted URI inputs to libsoup, including input validation and sanitization of data URI components prior to processing.
]]>highadvisorymemory-safetyvulnerabilitylibsoupheap-overflowcvememory-corruptionlinux