Bug 2440139 (CVE-2026-2574)

Summary: CVE-2026-2574 glib-networking: glib-networking: Denial of Service and information disclosure via crafted TLS client-CA list
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: crizzo, gtanzill, jbuscemi
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in glib-networking. A malicious Transport Layer Security (TLS) server can exploit an out-of-bounds read and invalid free vulnerability when a client using the OpenSSL backend connects. By advertising a specially crafted client-CA list, the server can trigger an issue where memory is accessed outside of its allocated buffer and subsequently freed incorrectly. This can lead to a denial-of-service and potentially disclose limited heap memory.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-02-16 05:03:59 UTC 
Out-of-Bounds Read and Invalid Free vulnerability in the OpenSSL backend of the glib-networking library. The flaw resides in the g_tls_client_connection_openssl_get_property() function of GTlsClientConnectionOpenssl, where i2d_X509_NAME() advances a pointer passed by reference. The code allocates a buffer using g_malloc(), then passes the pointer directly to i2d_X509_NAME(), which increments it to the end of the encoded data. This advanced pointer is subsequently stored in a GByteArray, causing reads from ba->data[0] to access memory outside of the allocated buffer and leading to an out-of-bounds heap read. Additionally, freeing the GByteArray results in freeing an interior pointer rather than the original allocation base, triggering invalid free and undefined behavior. A malicious TLS server that advertises a crafted client-CA list can remotely trigger this condition when a client using the OpenSSL backend connects, leading to denial-of-service and potential limited heap memory disclosure.