CVE-2026-102555 @ Library

"CVE-2026-102555"
"libsoup-gnome2.4-1-2.56.0-2+deb9u2"
"libsoup-gnome2.4-1"
"libsoup"
"libsoup2.4-1-2.56.0-2+deb9u2"
"Am I vulnerable?"

Status

new

Priority

1.96

Match score

4.0

Risk

DoS Remote

CVSS

8.2 HIGH

Reason

cpe: libsoup; pkgs: libsoup-gnome2.4-1; version: in-range: libsoup-gnome2.4-1-2.56.0-2+deb9u2; risk:dos

Created

2026-10-16T10:16:56Z

Updated

2026-10-20T10:18:04Z

Package interrogation (copy)

Run on the host — click to copy a command. Debian/apt

Package	Commands
libsoup-gnome2.4-1-2.56.0-2+deb9u2
libsoup-gnome2.4-1
libsoup
libsoup2.4-1-2.56.0-2+deb9u2

Inventory lookup

Search package inventory across systems, then return here. Create a ticket on systems the matcher missed.

Suggestions: libsoup-gnome2.4 · libsoup · libsoup-gnome2.4-1

Same product CVEs in your queue

Other open tickets that look like the same product. Closed tickets are omitted unless they are already pegged to this CVE.

CVE	CVSS	Systems	Status	Matched	Already related
CVE-2026-102560	8.6	Archive, Library, Saiph	new	libsoup-gnome2.4	—
CVE-2026-102558	8.6	Archive, Library, Saiph	new	libsoup-gnome2.4	—
CVE-2026-102557	8.6	Archive, Library, Saiph	new	libsoup-gnome2.4	—
CVE-2026-102556	8.6	Archive, Library, Saiph	new	libsoup-gnome2.4	—
CVE-2026-102559	8.6	Archive, Library, Saiph	new	libsoup-gnome2.4	—

Related CVE (same fix)

Point this ticket’s CVE at a higher-priority / same-fix primary so you only triage one.

Host OS / kernel

Debian GNU/Linux 9 (stretch) (9) · debian

Arch

x86_64

kernel_release

uname -r → 4.9.0-19-amd64

kernel_version

uname -v → #1 SMP Debian 4.9.320-2 (2022-06-30)

For Linux kernel CVEs, kernel_version (Debian packaging / build string) often decides fixed vs not; kernel_release is used for upstream NVD range compares.

Same CVE on other hosts

Open the ticket for this CVE on another system.

System	Status	Priority	Updated
Archive	new	0.73	2026-10-20T10:18:04Z	Open
Saiph	new	0.73	2026-10-20T10:18:04Z	Open

Description

A flaw was found in libsoup. The soup_uri_decode_data_uri() function incorrectly treated base64 data-URI payloads as NUL-terminated strings when calling g_base64_decode_inplace(). If the percent-decoded payload contained embedded NUL bytes, the decoded length could remain uninitialized and be used as the size of the returned GBytes. This can lead to an out-of-bounds read or application crash when processing a crafted data URI.

Update status

Add note only

References

NVD: CVE-2026-102555