CVE-2026-86409
Awaiting Analysis Awaiting Analysis - Queue

libcurl AWS SigV4 Authentication State Leak

Vulnerability report for CVE-2026-86409, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-20

Last updated on: 2026-10-29

Assigner: curl

Description

Setting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL isset next, leaking state information.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-20
Last Modified
2026-10-29
Generated
2026-11-10
AI Q&A
2026-10-21
EPSS Evaluated
2026-11-08
NVD
EUVD

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-201 The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves curl's CURLOPT_AWS_SIGV4 option. When set to NULL, it fails to disable AWS SigV4 authentication as expected. Instead, subsequent transfers using the same handle still send an Authorization header with AWS4-HMAC-SHA256, potentially leaking state information like access-key identifiers.

Detection Guidance

Check curl version with 'curl --version' to see if it is between 7.75.0 and 8.21.0. Review application code for use of CURLOPT_AWS_SIGV4 set to NULL. Monitor network traffic for unexpected AWS4-HMAC-SHA256 headers in requests after credential handling.

Impact Analysis

If an application reuses an easy handle and sets CURLOPT_AWS_SIGV4 to NULL before making a request to an attacker-controlled URL, it may unintentionally send a signed SigV4 header. This exposes the access-key identifier and request-bound signature, risking unauthorized access or data leaks. The secret key is not transmitted.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by exposing AWS access-key identifiers and request-bound signatures through leaked SigV4 headers. Unauthorized data exposure may violate confidentiality requirements under these regulations.

Mitigation Strategies

Upgrade curl to version 8.22.0 or later. If upgrading is not possible, apply the specific patch for your version. Avoid setting CURLOPT_AWS_SIGV4 to NULL in application code. Reuse of easy handles with credentials should be avoided.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-86409. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...