PULSE
FEED
ransomkrybit reclama a STL International Pte Ltd · SG · Otherransomakira reclama a Bench Equity · Financial Servicesransomakira reclama a Audiotec · Technologyransomrhysida reclama a WILLIAMS, BRODERSEN, PRITCHETT & RUIZ LLP · Professional Servicesransomakira reclama a Flagship Cruises & Events · US · Hospitalityransompixelleaks reclama a Permit Pros LLC · Professional Servicesransomwhitearmor reclama a Jeld-wen · US · Manufacturingransomhyflock reclama a Colombian Real Estate · CO · Retail & E-Commerceransomrhysida reclama a SteelTech Inc. · Manufacturingransomemperador reclama a Scooter Autoservice gmbh · DE · Transportationransomhyflock reclama a bestcorp · INransomhyflock reclama a ASIA FM Taiwan Inc · TW · Technologyransomthegentlemen reclama a AARP · US · Healthcareransomthegentlemen reclama a NVIDIA · US · Technologyransomkrybit reclama a STL International Pte Ltd · SG · Otherransomakira reclama a Bench Equity · Financial Servicesransomakira reclama a Audiotec · Technologyransomrhysida reclama a WILLIAMS, BRODERSEN, PRITCHETT & RUIZ LLP · Professional Servicesransomakira reclama a Flagship Cruises & Events · US · Hospitalityransompixelleaks reclama a Permit Pros LLC · Professional Servicesransomwhitearmor reclama a Jeld-wen · US · Manufacturingransomhyflock reclama a Colombian Real Estate · CO · Retail & E-Commerceransomrhysida reclama a SteelTech Inc. · Manufacturingransomemperador reclama a Scooter Autoservice gmbh · DE · Transportationransomhyflock reclama a bestcorp · INransomhyflock reclama a ASIA FM Taiwan Inc · TW · Technologyransomthegentlemen reclama a AARP · US · Healthcareransomthegentlemen reclama a NVIDIA · US · Technology
← Todos los CVEs
CVE Watch9 nov 2026

CVE-2024-4741

Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situation

CVSS

9.8

Crítico

EPSS

3.3%

p89

KEV

—

Exploit Today

27

0-100

Publicado: 13 nov 2024 · Última mod.: 9 nov 2026 · CWE-416

EPSS · 30d
2.9%EPSS · 30 días3.3%
2026-10-202026-11-17
Descripción técnica

Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use. The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use. The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use. While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-1236348.1 ALT
—
———This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI) or mirror directive sends a subrequest to a location that resolves the same server name. Under these conditions, a specially crafted HTTP request may cause a use-after-free condition in a worker process. An attacker may also be able to execute code if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or perform remote code execution (RCE) Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.3h
CVE-2026-1236338.1 ALT
—
———When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client requests to a backend, a specially crafted request can result in use-after-free in the worker process, if this process is running low on worker_connections. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or may allow a code execution. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.3h
CVE-2026-1218108.1 ALT
—
———Description: This issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/3. A remote, unauthenticated attacker can cause a use-after-free condition in the NGINX worker process, leading to a restart. Exploitation also depends on conditions beyond the attacker’s control. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.3h
CVE-2026-1134258.1 ALT
—
———When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: A remote unauthenticated attacker may crash an nginx worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.3h
CVE-2026-958237.5 ALT
—
———tcp_pkt_linearize() in subsys/net/ip/tcp.c is used by th_get() whenever a received TCP header is not contiguous in a single net_buf. While pulling the header bytes out of the following fragments, the loop called net_buf_unref() on an emptied fragment without first detaching its frags pointer. net_buf_unref() walks the whole fragment list, so the payload buffers still linked behind that fragment were freed as well, and the stale pointer was then reinstalled into the packet as buf->frags, producing a use-after-free and a later double free during packet teardown. The same loop also advanced to second->frags unconditionally: when the fragment still held payload after the header remainder was pulled, it was spliced out of the packet without ever being unreferenced, permanently leaking that buffer and silently dropping the data it carried. The defect is reached from tcp_recv() via th_get() on every received TCP segment, before connection lookup or any header validation, so a single unauthenticated segment that matches a listening socket is sufficient. An attacker only needs the TCP header to straddle a net_buf boundary, which they can arrange from off-link: IPv6 extension headers are accepted on receive and their length is added to the header offset by th_get(), so a Destination Options header of a suitable length places the TCP header across the boundary of the fixed-size receive buffers (CONFIG_NET_BUF_DATA_SIZE). Packet chains assembled from several sources - IPv4/IPv6 reassembly, 6LoWPAN/802.15.4 reassembly, tunnel or virtual interfaces that strip an outer header, or drivers producing scatter-gather chains - can additionally present a short interior fragment that the loop empties exactly, which is the case that frees the remainder of the packet while it is still in use. The reliably reachable consequence is exhaustion of the receive buffer pool: each crafted segment leaks one net_buf from the fixed CONFIG_NET_BUF_RX_COUNT pool, the buffers are never reclaimed, and once the pool is empty the device can no longer receive network traffic until it is rebooted. Where a fragment is emptied exactly, the impact rises to memory corruption: freed pool buffers are written through by the remainder of the loop, their contents may be delivered to the application, and the packet is double-freed on teardown. The fix saves and clears second->frags before the net_buf_unref() so only the emptied header fragment is released, and advances to the next fragment only when second->len == 0, keeping any fragment that still holds payload in the packet. This restores the detach-before-unref ownership pattern used elsewhere in the stack, for example in net_pkt_trim_buffer().5h
CVE-2026-1306623.7 BAJ
—
——0ImageMagick before 7.1.2-35 contains a use after free vulnerability in the MSL decoder that can be triggered when processing crafted MSL image files. Attackers can supply a specially crafted MSL image to cause memory corruption, potentially crashing the application or leading to further compromise.6h