This collection is limited to only include the reports that were submitted as security vulnerabilities to the curl bug-bounty program on Hackerone.
Several other issues not included here are highly suspcious as well.
- [Critical] Curl CVE-2023-38545 vulnerability code changes are disclosed on the internet. #2199174
- Buffer Overflow Vulnerability in WebSocket Handling #2298307
- Exploitable Format String Vulnerability in curl_mfprintf Function #2819666
- Buffer overflow in strcpy #2823554
- Buffer Overflow Vulnerability in strcpy() Leading to Remote Code Execution #2871792
- Buffer Overflow Risk in Curl_inet_ntop and inet_ntop4 #2887487
- bypass of this Fixed #2437131 [ Inadequate Protocol Restriction Enforcement in curl ] #2905552
- Hackers Attack Curl Vulnerability Accessing Sensitive Information #2912277
- ("possible") UAF #2981245
- Path Traversal Vulnerability in curl via Unsanitized IPFS_PATH Environment Variable #3100073
- Buffer Overflow in curl MQTT Test Server (tests/server/mqttd.c) via Malicious CONNECT Packet #3101127
- Use of a Broken or Risky Cryptographic Algorithm (CWE-327) in libcurl #3116935
- Double Free Vulnerability in
libcurlCookie Management (cookie.c) #3117697 - HTTP/2 CONTINUATION Flood Vulnerability #3125820
- HTTP/3 Stream Dependency Cycle Exploit #3125832
- Memory Leak #3137657
- Memory Leak in libcurl via Location Header Handling (CWE-770) #3158093
- Stack-based Buffer Overflow in TELNET NEW_ENV Option Handling #3230082
- HTTP Proxy Bypass via
CURLOPT_CUSTOMREQUESTVerb Tunneling #3231321 - Use-After-Free in OpenSSL Keylog Callback via SSL_get_ex_data() in libcurl #3242005
- HTTP Request Smuggling Vulnerability Analysis - cURL Security Report #3249936
- Disk Space Exhaustion leading to a Denial of Service (DoS) #3250490
- Vulnerability Report: Public Exposure of Security Audit File #3272982
- Vulnerability Report: Local File Disclosure via file:// Protocol in cURL #3293884
- Exposure of Hard-coded Private Keys and Credentials in curl Source Repository (CWE-321) #3295650
- TOCTOU Race Condition in HTTP/2 Connection Reuse Leads to Certificate Validation Bypass #3335085
- Stack Buffer Overflow in cURL Cookie Parsing Leads to RCE #3340109
- Timing Attack Vulnerability in curl Digest Authentication via Non-Constant-Time String Comparison #3346118
- Buffer Overflow in WebSocket Handshake (lib/ws.c:1287) #3392174
- Use of Deprecated strcpy() with Fixed-Size Buffers in Progress Time Formatting #3395218
- Use of Deprecated strcpy() with User-Controlled Environment Variable in Memory Debug Initialization #3395227
- Integer Overflow to Heap Overflow in DoH Response Handling #3399774
- CURLX_SET_BINMODE(NULL) can call fileno(NULL) and cause undefined behavior / crash #3400831
- Logical Flaw in curl_url_set Leads to Inconsistent Query Parameter Encoding #3403880
- Unsafe use of strcpy in Curl_ldap_err2string (packages/OS400/os400sys.c) — stack-buffer-overflow (PoC + ASan) #3418528
- Arbitrary Configuration File Inclusion: via External Control of File Name or Path #3418646
- Title: Use-After-Free in cURL Test Suite via Improper Cleanup of Global Handle #3452725
- Stack Buffer Overflow in cURL wolfSSL Backend (lib/vtls/wolfssl.c) #3459636
- Buffer Overflow in cURL Internal printf Function #3462525
- Path Traversal Bypass in file:// URLs Due to Incomplete URL-Encoded Path Normalization #3465094
- Curl Alt-Svc Parser Stack Buffer Overflow #3466883
- Heap Overflow in cURL AmigaOS Socket Implementation #3466896
- Heap buffer overflow in Curl_ipv4_resolve_r due to incorrect buffer alignment and size calculation on AmigaOS #3468410
- Heap Buffer Over-Read via Malicious SMB Server READ_ANDX Response #3470095
- A logic error in detect_proxy caused truncation of environment variable names for long protocol schemes. #3473182
- Heap Out-of-Bounds Read in lib/http2.c via Malformed PUSH_PROMISE Headers #3506159
- libcurl: Improper Authentication State Management on Cross-Protocol Redirects #3514263
- Cookie Max-Age Integer Overflow Vulnerability #3516186
- Cookie Replacement Use-After-Free Vulnerability #3516202
Our current policy says that we instantly ban all reporters submitting AI slop.

The really scary part is that all of the effort put into filtering out this slop could have been used addressing real problems. If I were a hacker with a valuable zero day that I didn't want fixed, I'd do exactly this. Basically, it's a DoS attack on the maintenance process.