Skip to content

CVE-2026-92392: curl HTTP/2 Upload Stream Reset Use-After-Free to Client RCE

Density:
C-Level Executive Briefing CVE-2026-92392 HIGH SCORE 87/100

High-severity Use-After-Free (UAF) in libcurl HTTP/2 stream management reported by Anthropic researcher Luna Tong and analyzed by JFrog. When a remote server shuts flow control and resets an active upload stream, out-of-order cleanup retains a dangling stream pointer, enabling client-side code execution.

HYBRID

HERMES THREAT SCORE & CLOUD-NATIVE CLIENT RISK EVALUATION

Target: libcurl HTTP/2 Multiplexing Engine (Curl_http2_done / nghttp2 wrapper)
Confidence: 97%
87 / 100
HIGH

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 17 / 20
Threat Activity 16 / 20
Weaponization 18 / 20
Exposure 18 / 20
Prevalence 20 / 20
Impact 18 / 20
Exploit Maturity 17 / 20
Attack Chain Potential 18 / 20
โš–๏ธ Divergence & Operational Rationale

While CVSS assigns an 8.1 with High Attack Complexity (AC:H) due to the necessity of concurrent bidirectional stream grooming, libcurl is ubiquitously embedded across thousands of cloud-native microservices, API proxies, Git clients, and automated data pipelines. An adversary controlling a webhook destination or intermediary reverse proxy can exploit this race condition to achieve code execution inside unprivileged backend containers.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-92392: curl HTTP/2 Upload Stream Reset Use-After-Free to Client RCEVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTJFrog Artifactory
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in JFrog Artifactory documented in Hermes dossier.”

Supporting Verified Evidence:

Disclosed in curl 8.23.0 on October 14, 2026 and discovered by Luna Tong (Anthropic), CVE-2026-92392 is a high-severity Use-After-Free (UAF) vulnerability (CWE-416) in the HTTP/2 framing implementation of curl and libcurl (versions >= 7.88.0 up to 8.22.0).

The vulnerability manifests when curl transmits request payloads over an HTTP/2 connection. If the remote peer shuts down its flow-control window (sending WINDOW_UPDATE 0) and immediately sends an RST_STREAM frame while curl has pending data in its pause buffer, the error recovery path deallocates the stream struct before clearing the active stream descriptor from the multiplexed session manager. Under specific multi-threaded or multi-connection configurations (such as simultaneous upload and download tasks), an attacker-controlled HTTP/2 server can reclaim the freed memory chunk and achieve remote code execution in the client process context.


When curl uploads data over HTTP/2 via nghttp2, it maintains a stream abstraction struct (struct HTTP) linked to the transfer session:

// Vulnerable Sequence in lib/http2.c
static int cf_h2_stream_close(struct Curl_cfilter *cf, struct Curl_easy *data) {
struct stream_ctx *stream = data->req.p.http;
// Step 1: Free internal stream tracking data
free_stream_ctx(stream);
// Step 2: DANGEROUS - Stream pointer remains referenced in session queue!
// If a concurrent event fires before Curl_http2_done unlinks the pointer,
// subsequent nghttp2 callbacks invoke methods on deallocated memory.
}

If the attacker controls the server endpoints, they can synchronize two concurrent connections:

  1. Connection A (Upload): Forces curl to pause buffering via window starvation, then sends RST_STREAM.
  2. Connection B (Download / Heap Grooming): Floods the process with carefully sized HTTP/2 headers to reallocate the freed stream_ctx structure with attacker-controlled function pointers.
  3. Upon completing stream teardown, curl calls the vtable function pointer on the reclaimed chunk, redirecting instruction pointer control.
sequenceDiagram
participant Client as libcurl Client
participant Server as Malicious HTTP/2 Server
Client->>Server: HTTP/2 HEADERS + DATA (Upload Payload)
Server-->>Client: WINDOW_UPDATE: 0 (Pause Flow Window)
Note over Client: curl pauses upload & queues buffer
Server-->>Client: RST_STREAM (Stream Cancelled)
Note over Client: cf_h2_stream_close frees stream_ctx
Server->>Client: Concurrent Stream Response (Heap Grooming Spray)
Note over Client: Reclaims freed stream_ctx memory block
Client->>Client: Invokes teardown callback -> HIJACKED CONTROL FLOW

Suricata Signature: Abrupt HTTP/2 Window Depletion & Immediate RST_STREAM

Section titled โ€œSuricata Signature: Abrupt HTTP/2 Window Depletion & Immediate RST_STREAMโ€
alert tcp any any -> any any (msg:"HERMES CODEX - Suspected CVE-2026-92392 curl HTTP/2 UAF Exploit Trigger"; flow:established,to_client; content:"|00 00 04 08 00|"; depth:5; content:"|00 00 00 00|"; distance:0; within:4; content:"|00 00 04 03|"; distance:0; within:16; classtype:attempted-admin; sid:202692392; rev:1;)

  1. Upgrade curl & libcurl to 8.23.0 Distribution packages have released security errata. Update via apt-get upgrade curl or dnf update curl.
  2. Operational Workaround: Force HTTP/1.1 for Uploads If binary updates cannot be deployed immediately, force HTTP/1.1 on sensitive automated workloads:
    Terminal window
    curl --http1.1 --upload-file payload.dat https://api.endpoint.internal/
    Or set CURLOPT_HTTP_VERSION = CURL_HTTP_VERSION_1_1 in libcurl client applications.