CVE-2026-82208: 
cURL vulnerability analysis and mitigation

CVE-2026-82208 is a certificate validation bypass vulnerability in curl/libcurl affecting the wolfSSL TLS backend, where CA-cache hit logic can silently reinstall a cached CA store after a CURLOPT_SSL_CTX_FUNCTION callback returns, causing an incorrectly trusted certificate to be accepted. It affects curl versions 8.9.1 through 8.21.0 (inclusive) and was introduced via a specific commit in that range. The vulnerability was reported on August 27, 2026, and publicly disclosed on September 2, 2026, alongside the release of curl 8.22.0. It carries a severity rating of Low and is classified under CWE-295 (Improper Certificate Validation) (curl Advisory, oss-sec).

The root cause (CWE-295) lies in the wolfSSL CA-cache hit logic within libcurl: when CA caching is enabled and a CURLOPT_SSL_CTX_FUNCTION callback replaces the trust store with a custom one, libcurl can silently reinstall the previously cached CA store after the callback returns. This means a certificate that would be rejected by the callback-selected store but is trusted by the cached store gets incorrectly accepted, effectively bypassing the custom certificate validation logic. The flaw is specific to the wolfSSL backend and does not affect other TLS backends or the curl command-line tool itself. The vulnerability was discovered by Stanislav Fort of Aisle Research and patched by Stefan Eissing (curl Advisory, Aisle Blog).

Successful exploitation allows a TLS peer presenting a certificate trusted by the cached CA store — but explicitly rejected by the application's custom callback — to be incorrectly accepted, undermining the application's intended certificate validation policy. This primarily affects confidentiality and integrity, as an attacker positioned to perform a man-in-the-middle attack could intercept or tamper with TLS-protected communications in applications relying on CURLOPT_SSL_CTX_FUNCTION for custom trust decisions. The impact is limited to libcurl consumers using the wolfSSL backend with both CA caching and the SSL context callback enabled simultaneously; the curl command-line tool is not affected (curl Advisory).

No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the disclosure date. The CVE status is listed as Reserved, and the vulnerability is rated Low severity, reflecting the narrow preconditions required: the target application must use libcurl built with wolfSSL, have CA caching enabled, and use a CURLOPT_SSL_CTX_FUNCTION callback to replace the trust store. There is no current CISA KEV catalog listing or known threat actor attribution for this vulnerability (curl Advisory, oss-sec).

1. Identify target: Locate an application using libcurl built against the wolfSSL TLS backend (versions 8.9.1–8.21.0) that also uses CURLOPT_SSL_CTX_FUNCTION to install a custom trust store and has CA caching enabled.
2. Obtain a certificate: Acquire or forge a TLS certificate that is trusted by the cached CA store but would be rejected by the application's custom callback-selected trust store.
3. Position for MitM: Intercept the TLS connection between the vulnerable libcurl client and its intended server (e.g., via ARP spoofing, DNS poisoning, or network-level interception).
4. Present the certificate: Serve the attacker-controlled certificate during the TLS handshake. Due to the CA-cache hit overriding the callback's trust store, libcurl incorrectly accepts the certificate.
5. Intercept traffic: With the TLS session established to the attacker's endpoint, decrypt, inspect, or modify the application's communications (curl Advisory).

The primary remediation is to upgrade curl and libcurl to version 8.22.0, released September 2, 2026, which contains the fix (curl Advisory). Alternatively, apply the patch commit ed0338befd1d865a8ea1fbaa90 to the affected version and rebuild. As a configuration-based workaround, avoid using CURLOPT_SSL_CTX_FUNCTION in combination with the wolfSSL backend until the upgrade can be applied. Applications not using wolfSSL as their TLS backend are not affected and require no action.

The vulnerability was one of six curl CVEs discovered by Stanislav Fort of Aisle Research, which drew attention given that the researcher found these issues after AI tools from OpenAI and Anthropic reportedly found zero vulnerabilities in curl — a point highlighted in Aisle's blog post (Aisle Blog). curl project lead Daniel Stenberg noted the release of curl 8.22.0 addressing these issues on his blog (Daniel's Blog). The curl advisory explicitly notes this bug is not considered a C language mistake, which is an unusual editorial note reflecting ongoing discussions in the security community about memory-safe languages.