Use-After-Free in HTTP/2 Upload Leads to Potential RCE in curl: Detailed Analysis of CVE-2026-92392
curl 8.23.0 closed one of the most severe vulnerabilities in recent years, rated HIGH and assigned CVE-2026-92392 (HTTP/2 upload Use-After-Free). The flaw allows a malicious server to trigger remote code execution under specific conditions during data uploads over HTTP/2.
Use-after-free is a classic memory-safety issue in languages without guarantees such as C. A pointer remains valid after the referenced memory has been freed, and an attacker who can control the contents of that memory region can alter program behavior.
HTTP/2 multiplexing requires libcurl to manage multiple concurrent transfers over a single connection. Each transfer uses an easy handle created by the application; a multi handle coordinates any number of easy handles.
To trigger the bug, the client must upload data to an HTTPS server that supports HTTP/2. The server pauses the upload by zeroing the flow-control window, sends a partial response, then resets the stream. libcurl correctly finishes the transfer but leaves a dangling pointer to the easy handle. When the application later frees the handle and closes the multi handle, libcurl reuses the stale pointer while processing incoming data.
The library allocates a receive buffer, reads attacker-controlled data into the former location of the easy handle, and eventually calls a function pointer that has been overwritten by the downloaded payload, resulting in arbitrary code execution. The attack also leaks internal client details that help bypass ASLR.
Successful exploitation demands many conditions: the victim must upload roughly 135 KB, the attacker must know the target architecture and memory layout, and specific allocation patterns involving nghttp2 and OpenSSL TLS 1.3 must align. The payload area is limited to about 23 bytes, making a crash far more likely than code execution.
The vulnerability was reported by Luna Tong of Anthropic via their OSS Scanner. The curl security team confirmed it within hours on 15 September and shortened the release cycle from eight to six weeks to ship the fix promptly.
Developers are reducing the number of internal pointers to handles, replacing them with transfer identifiers that are looked up on demand. Additional tests and static analyzers are being introduced to catch similar errors earlier.
Related articles
Security Week 2644: Active Exploitation of PHP2Shell Vulnerabilities Confirmed
PHP developers released patches for two critical vulnerabilities collectively known as PHP2Shell on October 20, affecting PHP 8.2 through 8.5 as well as older branches. The flaws allow unauthenticated remote code execution on affected servers, which power approximately 70 percent of websites. Despite expectations of immediate exploitation, confirmed attacks with working exploits only began on October 25. CrowdStrike noted technical difficulties in weaponizing the issues in real-world environments. Only one-fifth of top Russian websites had applied the fixes by October 25. Additional incidents included compromised eMudhra certificates, a critical GitLab flaw, and a 16-year-old Broadcom router vulnerability.
Positive Technologies Offers Up to 500,000 Rubles for Bypassing PT Application Firewall
Positive Technologies has expanded its Standoff Bug Bounty program to include rewards for bypassing its web application firewalls. Researchers can earn between 150,000 and 500,000 rubles for demonstrating practical bypasses against PT Application Firewall PRO and PT Application Firewall Cloud. The program targets the core protective mechanisms, including traffic filtering, attack detection rules, and the management layer used by administrators. Submissions must include reproducible attack scenarios that show how malicious requests can pass through undetected, rather than relying on scanner reports or theoretical findings. Reward amounts vary by severity and confirmed business impact, with critical issues in the PRO version paying up to 500,000 rubles. The company plans to use validated findings to strengthen detection rules and improve overall product resilience.
Tailscale SSH Vulnerability Allows Root Access via Unix Socket Redirection
A researcher identified flaws in Tailscale that let an attacker with existing SSH access on one node escalate to root privileges and move laterally across the network. Erica Windisch of Cyberdione Labs demonstrated the issues in lab conditions against Tailscale 1.104.2 and Headscale 0.29.5. The core problem stems from privileged operations performed by the tailscaled process when handling Unix socket redirection, granting an ordinary SSH session access to root-only resources. The researcher used the technique to interact with Docker and run elevated commands, and showed that broad access policies allow automated lateral movement in under a second. Additional issues include denial-of-service conditions and bypasses of certain restrictions. Recommendations include reviewing SSH policies and disabling unnecessary socket redirection, noting that Headscale 0.29.5 lacks an independent way to turn the feature off.
Critical CVE-2026-111497 Out-of-Bounds Write Flaw in Google Brotli Decoder Impacts Broad Range of Environments
A severe vulnerability has been identified in the Google-developed Brotli decoder used for decompressing data in web communications and other applications. The flaw, tracked as CVE-2026-111497, allows out-of-bounds writes when processing specially crafted compressed data, potentially enabling arbitrary code execution, information disclosure, or denial of service. It carries a CVSS v4.0 base score of 9.2 and is rated Critical. Google has released patched versions 1.2.1, 1.1.1, and 1.0.10 of the library. Node.js incorporated the fix in its updates, while Microsoft issued an out-of-band patch for .NET on October 25, 2026, to address the issue. The vulnerability affects any environment relying on the Brotli C implementation for data decompression.