libcurl HTTP/2 stream-dependency tree use-after-free
CVE-2026-10536 is a low-severity use-after-free vulnerability in libcurl’s HTTP/2 stream-dependency handling. The flaw occurs when an application configures an HTTP/2 stream-dependency tree using CURLOPT_STREAM_DEPENDS or CURLOPT_STREAM_DEPENDS_E, then calls curl_easy_reset(), and later destroys the easy handle with curl_easy_cleanup(). In the affected code path, reset frees internal dependency-related state, but cleanup later still accesses and modifies that already-freed structure, resulting in a use-after-free. The issue affects libcurl versions 7.88.0 through 8.20.0 inclusive. The curl command-line tool is not affected. The vulnerability was introduced by commit 71b7e0161032927cdfb and fixed by commit bfbff7852f050232edd3e5ca.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free vulnerability in libcurl's HTTP/2 stream dependency handling where resetting and then cleaning up a handle using HTTP/2 dependency options could cause libcurl to access already-freed state.
A use-after-free vulnerability in curl/libcurl related to HTTP/2 stream dependency handling during reset and cleanup of dependency handles.
A curl/libcurl use-after-free vulnerability.
A low-severity curl/libcurl use-after-free vulnerability in HTTP/2 stream dependency tree handling.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.