libcurl/curl is widely embedded across software and systems; a high-severity use-after-free during HTTP/2 uploads can crash processes or enable remote code execution, impacting many organizations.
CVE-2026-92392
curl HTTP/2 upload use-after-free enabling crashes or potential remote code execution
Is CVE-2026-92392 being exploited?
Not confirmed. CVE-2026-92392 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.63% probability of exploitation in the next 30 days.
How severe is CVE-2026-92392?
CVE-2026-92392 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-92392?
Not known from our data. No patch reference has been recorded for CVE-2026-92392, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-92392 affect?
CVE-2026-92392 affects curl, libcurl, applications using libcurl with HTTP/2 uploads enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92392?
Apply vendor fix when available; temporarily disable HTTP/2 uploads or block untrusted HTTP/2 servers
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free in libcurl during HTTP/2 uploads via crafted RST_STREAM (HTTP_1_1_REQUIRED/REFUSED_STREAM) can crash clients or enable remote code execution.
Patch when possible
- affected<= 8.22.0
- affected<= 8.21.0
- affected<= 8.20.0
- affected<= 8.19.0
- affected<= 8.18.0
- affected<= 8.17.0
- affected<= 8.16.0
- affected<= 8.15.0
- affected<= 8.14.1
- affected<= 8.14.0
- affected<= 8.13.0
- affected<= 8.12.1
- affected<= 8.12.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.