CVE-2026-84366

What it is

Scrapy is a high-level web crawling and scraping framework for Python. Prior to 2.17.0, in scrapy/core/downloader/handlers/s3.py, Scrapy's S3DownloadHandler converts an S3-scheme bucket and key request into a plaintext HTTP request to the corresponding S3 endpoint unless request.meta["is_secure"] is explicitly enabled, then signs and sends the plaintext request with configured AWS credentials. A network attacker who can observe traffic between Scrapy and S3 can read the bucket and key path, AWS Authorization header, X-Amz-Security-Token when temporary credentials are used, S3 object contents, and S3 response headers. An active man-in-the-middle attacker can also modify the plaintext S3 response body, status code, and headers before Scrapy processes them, causing scraped-data poisoning, poisoned exports, HTTP cache poisoning when caching is enabled, or influence over later crawl targets through forged redirects or attacker-controlled links. Users making S3-scheme requests with AWS credentials are affected. This issue is fixed in version 2.17.0.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-01 21:18 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-09 21:09 UTC Last updatedMost recent change to the record

Details

Published

2026-09-01 21:18 UTC

Last modified

2026-09-09 21:09 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-319 · Cleartext transmission

Record status

Deferred

Attack profile CVSS 3.1 · 7.4

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None