CVE-2026-2436: Libsoup: libsoup: denial of service via use-after-free in soupserver during tls handshake

Published Feb 26, 2026
·
Updated

A flaw was found in libsoup's SoupServer. A remote attacker could exploit a use-after-free vulnerability where the soupserverdisconnect() function frees connection objects prematurely, even if a TLS handshake is still pending. If the handshake completes after the connection object has been freed, a dangling pointer is accessed, leading to a server crash and a Denial of Service.

Other sources

Libsoup: libsoup: denial of service via use-after-free in soupserver during tls handshake

Microsoft

SoupServer is vulnerable to use after free vulnerability because soupserverdisconnect() frees all SoupServerConnection objects, even if there is a pending GNUTLS handshake to be finished.

A TLS handshake is initiated asynchronously. After creating the SoupServerConnection, libsoup calls gtlsconnectionhandshakeasync(), which registers tlsconnectionhandshakereadycb as a callback. The handshake runs in the background andthe callback fires later when it completes. When the TLS handshake completes successfully, GNUTLS invokes tlsconnectionhandshakereadycb() asynchronously

soupserverdisconnect() is called ( due to some scenario, like a server restart, or other cases). This iterates through all active connections and disconnects them. When the last reference to a SoupServerConnection is dropped, soupserverconnectionfinalize() is called, freeing the object. If the TLS handshake completes after soupserverdisconnect() has freed the connection object, tlsconnectionhandshakereadycb() still fires with a dangling pointer. The callback then calls soupserverconnectionconnected(conn), which attempts to access the freed SoupServerConnection via soupserverconnectiongetiostream(), causing a crash

Red Hat

Affected Software

9 affected componentsFixes available
Gnome libsoup
Microsoft azl3 libsoup 3.4.4-14
Microsoft azl3 libsoup 3.4.4-15
Gnome libsoup
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
redhat Enterprise Linux=10.0

Event History

Feb 26, 2026
Data Sourced
via Red Hat·01:15 AM
DescriptionSeverityAffected Software
Mar 26, 2026
CVE Published
via MITRE·07:31 PM
Data Sourced
via MITRE·07:31 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeaknessAffected Software
Apr 2, 2026
Data Sourced
via Microsoft·08:05 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:05 AM
Affected Software
Updated
via Microsoft·08:05 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-2436?

The severity of CVE-2026-2436 is considered to be high due to its potential to cause a denial of service through a use-after-free vulnerability.

2

How do I fix CVE-2026-2436?

To fix CVE-2026-2436, update to the latest version of libsoup where the vulnerability has been patched.

3

Which software is affected by CVE-2026-2436?

CVE-2026-2436 affects GNOME libsoup, as well as specific versions of azl3 libsoup used in Microsoft products and multiple versions of Red Hat Enterprise Linux.

4

What exploit does CVE-2026-2436 provide to attackers?

CVE-2026-2436 allows remote attackers to exploit a use-after-free condition during a TLS handshake, potentially leading to denial of service.

5

Is CVE-2026-2436 present in older versions of libsoup?

Yes, CVE-2026-2436 is likely present in older versions of libsoup prior to the patch that addresses this vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203