Fedora Account System
Red Hat Associate
Red Hat Customer
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. A heap use-after-free vulnerability exists in libsoup's HTTP/2 client implementation. When a GNOME application sends an HTTP/2 POST request with a file body (using a non-pollable GInputStream such as GFileInputStream), the body data is read asynchronously via g_input_stream_read_async(). If the remote HTTP/2 server sends a GOAWAY frame while this async read is pending, the SoupHTTP2MessageDatastructure is freed through the shutdown path, but the async read callback on_data_read() still fires afterward, accessing the freed heap memory. This is a remotely-triggerable heap use-after-free — a malicious HTTP/2 server (or MITM attacker) can deterministically trigger it when any GNOME application uploads a file over HTTPS with HTTP/2. Affected applications include GNOME Web (Epiphany), GNOME Software, Flatpak, and any GLib-based application using SoupSession for HTTP/2 file uploads. Impact type: Heap use-after-free (CWE-416) — the freed 168-byte SoupHTTP2MessageData struct is read after free, and the freed data_source_buffer may also be written to by the still-pending async I/O operation. This constitutes memory corruption with potential for information disclosure or code execution.
Fix appears to be already in 3.7.1+, so rawhide and f45 don't need to do anyhting For f44 and f43 need to backport to 3.6.x: - https://gitlab.gnome.org/GNOME/libsoup/-/commit/ebf2d8ad8d2507787c286883a02874f0539c0206 - (ideally) https://gitlab.gnome.org/GNOME/libsoup/-/commit/a439ac2e0cc2f11a99fbfc7fa6b0079923509c94
Actually, ebf2d8 appears to be best followed-up by https://gitlab.gnome.org/GNOME/libsoup/-/commit/3bf4a56c2d7e516dd8809f8a4f7a24b22c5b07ba (it fixes a regression in the first commit). The LLM claims a438ac may be a no-op in 3.6.x, and it was optional anyway (according to the upstream report, ebf2d8 is the preferred fix!), so dropped!
FEDORA-2026-6c3a4775a6 (libsoup3-3.6.6-6.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-6c3a4775a6
FEDORA-2026-f06a7887af (libsoup3-3.6.6-11.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f06a7887af
FEDORA-2026-6c3a4775a6 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-6c3a4775a6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6c3a4775a6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-f06a7887af has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f06a7887af` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f06a7887af See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-f06a7887af (libsoup3-3.6.6-11.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-6c3a4775a6 (libsoup3-3.6.6-6.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.