# CVE-2026-102555: libsoup out-of-bounds read in data-URI base64 decoding

Source: https://junglewise.ai/threats/cve-2026-102555-a-flaw-was-found-in-libsoup-the-soup-uri-decode-data-uri  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-29. Updated: 2026-09-29  
License: CC BY 4.0 with a link back

CVE-2026-102555 · Severity: high · CVSS 8.2 · Published 2026-09-29

libsoup is an HTTP library widely used by GNOME and other Linux applications. A flaw in the soup_uri_decode_data_uri() function can cause an out-of-bounds memory read or application crash when processing crafted data URIs, potentially exposing sensitive data or causing denial of service.

Technologies: [Gnome Libsoup](https://junglewise.ai/threats/technologies/libsoup). Vendors: [Gnome](https://junglewise.ai/threats/vendors/gnome).

## Quick answers

**Is CVE-2026-102555 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-102555 being exploited in the wild.

**How severe is CVE-2026-102555?** High severity, with a CVSS score of 8.2, published 29 September 2026.

**Which products and versions are affected?** GNOME libsoup.

**Is there a fix for CVE-2026-102555?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-102555 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-102555?** Check whether you run Gnome Libsoup. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The soup_uri_decode_data_uri() function incorrectly treats base64 data-URI payloads as NUL-terminated strings when calling g_base64_decode_inplace(). If the percent-decoded payload contains embedded NUL bytes, the decoded length remains uninitialized and is used as the size of the returned GBytes, leading to out-of-bounds read. The vulnerability is triggered when an application passes untrusted data URIs to this function.

## Affected products

- GNOME libsoup

## Timeline

- 2026-09-29: disclosed

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-102555](https://access.redhat.com/security/cve/CVE-2026-102555)

## Related threats

- [libsoup HTTP request smuggling via undrained Expect: 100-continue body](https://junglewise.ai/threats/cve-2026-103399-a-flaw-was-found-in-soupserver-libsoup-when-an-http-1-x-client)
- [libsoup heap buffer overflow in permessage-deflate WebSocket extension](https://junglewise.ai/threats/cve-2026-102560-a-flaw-was-found-in-libsoup-when-the-permessage-deflate)
- [libsoup heap buffer overflow in WebSocket handling](https://junglewise.ai/threats/cve-2026-102558-a-flaw-was-found-in-libsoup-when-max-incoming-payload-size-is)
- [libsoup heap corruption in WebSocket message reassembly](https://junglewise.ai/threats/cve-2026-102557-a-flaw-was-found-in-libsoup-when-reassembling-fragmented)
- [libsoup type confusion in WebSocket Pong signal](https://junglewise.ai/threats/cve-2026-102556-a-flaw-was-found-in-libsoup-when-handling-an-incoming-websocket)