85 matches found
ALPINE-CVE-2026-86409
Setting CURLOPTAWSSIGV4 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...
DEBIAN-CVE-2026-86409
Setting CURLOPTAWSSIGV4 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...
CVE-2026-86409 stale SigV4 headers sent unintended
Setting CURLOPTAWSSIGV4 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...
CVE-2026-86409
The curl library (versions prior to 8.22.0 ) is vulnerable to an information disclosure flaw where setting CURLOPT_AWS_SIGV4 to NULL fails to disable SigV4 authentication. Consequently, a subsequent transfer using the same handle will continue to send an Authorization: AWS4-HMAC-SHA256 header to ...
CVE-2026-86409 stale SigV4 headers sent unintended
Setting CURLOPTAWSSIGV4 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...
EUVD-2026-105274
Setting CURLOPTAWSSIGV4 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...
Red Hat: CVE-2026-86409: curl: curl: stale SigV4 headers sent unintended
Setting CURLOPTAWSSIGV4 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...
CVE-2026-86409
A flaw was found in curl. When an application attempts to disable Amazon Web Services Signature Version 4 AWS SigV4 authentication on a reused connection handle, curl fails to clear the setting as expected. If the application subsequently directs a request to an untrusted or attacker-controlled...
Insertion of Sensitive Information Into Sent Data
Overview Affected versions of this package are vulnerable to Insertion of Sensitive Information Into Sent Data in the process of reusing transfer handles across different trust boundaries and attempting to clear AWS SigV4 authentication by resetting the option to null. An attacker can obtain acce...
curl: curl: stale SigV4 headers sent unintended
A flaw was found in curl. When an application attempts to disable Amazon Web Services Signature Version 4 AWS SigV4 authentication on a reused connection handle, curl fails to clear the setting as expected. If the application subsequently directs a request to an untrusted or attacker-controlled...
CURL-CVE-2026-86409 stale SigV4 headers sent unintended
Setting CURLOPTAWSSIGV4 to NULL 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 is set next, leaking state information...
stale SigV4 headers sent unintended
Setting CURLOPTAWSSIGV4 to NULL 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 is set next, leaking state information...
UBUNTU-CVE-2026-86409
Setting CURLOPTAWSSIGV4 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...
ceph: ceph: RGW SigV4 verifier allows attachment of arbitrary unsigned x-amz-* headers leading to privilege escalation
A flaw was found in Ceph RGW's SigV4 signature verification handler. When processing S3 requests, RGW verifies only the headers explicitly listed in the X-Amz-SignedHeaders field but does not reject requests that carry additional unsigned x-amz- headers. This diverges from the AWS S3 specificatio...
Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS / 26.04 LTS : Ceph vulnerability (USN-8867-1)
The remote Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS / 26.04 LTS host has packages installed that are affected by a vulnerability as referenced in the USN-8867-1 advisory. It was discovered that the Ceph Object Gateway RGW SigV4 handler did not reject requests carrying x-amz- headers that were...
USN-8867-1 ceph vulnerability
It was discovered that the Ceph Object Gateway RGW SigV4 handler did not reject requests carrying x-amz- headers that were absent from the signed header set. An attacker holding a presigned URL could possibly use this issue to attach arbitrary unsigned x-amz- headers that RGW would honor, allowin...
USN-8867-1: Ceph vulnerability
It was discovered that the Ceph Object Gateway RGW SigV4 handler did not reject requests carrying x-amz- headers that were absent from the signed header set. An attacker holding a presigned URL could possibly use this issue to attach arbitrary unsigned x-amz- headers that RGW would honor, allowin...
CVE-2026-88018
A flaw was found in rclone. When the rclone serve s3 command is configured with --auth-proxy but without --auth-key, an unauthenticated network attacker can bypass the SigV4 signature verification process. This allows the attacker to use an arbitrary access key and sign requests with an empty...
CVE-2026-94368
A flaw was found in the signature verification logic of noobaa-core, the core component of the NooBaa Multicloud Object Gateway. The issue occurs when the service processes S3 presigned URLs using Signature Version 4 SigV4. Due to improper validation, the service fails to reject requests containi...
EUVD-2026-83898
A flaw was found in the signature verification logic of noobaa-core, the core component of the NooBaa Multicloud Object Gateway. The issue occurs when the service processes S3 presigned URLs using Signature Version 4 SigV4. Due to improper validation, the service fails to reject requests containi...