CVE-2026-84366: Scrapy S3DownloadHandler Sends Signed S3 Requests Vulnerability
HIGHCVE-2026-84366 is a HIGH (CVSS 7.4) s3downloadhandler sends signed s3 requests vulnerability (CWE-319: Cleartext Transmission of Sensitive Information) affecting Scrapy libraries in the PyPI ecosystem. The issue involves s3downloadhandler sends signed s3 requests over plaintext http by default. Remediation is available by upgrading affected packages to version 2.17.
CVE-2026-84366 at a Glance
Security Impact
CVSS: 7.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).
How to Fix CVE-2026-84366
To remediate this vulnerability, upgrade all affected Scrapy dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install scrapy>=2.17
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show scrapy
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-84366, inspect your installed packages using pip:
pip show scrapy
Analyze the terminal output to locate any version of Scrapy in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.17), your application is affected.
Note: The pip show scrapy command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-319: Cleartext Transmission of Sensitive Information, where the product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. In Scrapy, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-84366 Affected Scrapy Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
scrapy
|
PyPI |
< 2.17
|
2.17
|
References
Frequently Asked Questions
What is CVE-2026-84366?
Which Scrapy versions are affected?
What version fixes CVE-2026-84366?
Is scrapy affected?
What is the CVSS score of CVE-2026-84366?
What CWE is associated with CVE-2026-84366?
How can I check PyPI dependencies for CVE-2026-84366?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-76g3-c3x4-crvx",
"modified" : "2026-09-02T22:50:44Z",
"published" : "2026-09-02T22:50:44Z",
"aliases" : [ "CVE-2026-84366" ],
"summary" : "Scrapy: S3DownloadHandler sends signed S3 requests over plaintext HTTP by default",
"details" : "### Problem\n\nScrapy’s `S3DownloadHandler` sends signed S3 requests over plaintext HTTP by default.\n\nA normal request like `s3://bucket/key` is converted into `http://bucket.s3.amazonaws.com/key` unless `request.meta[\"is_secure\"]` is explicitly set. The generated request is then signed with configured AWS credentials, so AWS authorization material can be sent without TLS.\n\nVulnerable code in `scrapy/core/downloader/handlers/s3.py`:\n\n```python\nscheme = \"https\" if request.meta.get(\"is_secure\") else \"http\"\nurl = f\"{scheme}://{bucket}.s3.amazonaws.com{path}\"\n```\n\nThe request is then signed and dispatched:\n\n```python\nself._signer.add_auth(awsrequest)\nrequest = request.replace(url=url, headers=awsrequest.headers.items())\n```\n\n### Impact\n\nUsers making Scrapy `s3://` requests with AWS credentials are impacted.\n\nA network attacker able to observe traffic between Scrapy and S3, such as a public Wi-Fi attacker, compromised router, ISP/corporate network observer, or local network attacker using ARP spoofing, can read:\n\n```text\nbucket/key path\nAWS Authorization header\nX-Amz-Security-Token, if temporary credentials are used\nS3 object contents\nS3 response headers\n```\n\nAn active MITM attacker can also modify the plaintext S3 response body, status code, and headers before Scrapy processes it. This can cause scraped data poisoning, poisoned exports, HTTP cache poisoning when cache is enabled, and influence over later crawl targets through forged redirects or attacker-controlled links.\n\n\nSuggested classification: **CWE-319: Cleartext Transmission of Sensitive Information**.\n\n\n### PoC\n\nA minimal PoC creates an `s3://` request, enables fake AWS settings, captures the request produced by `S3DownloadHandler`, and prints the rewritten URL and auth headers.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "scrapy"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.17"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "< 2.17.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/scrapy/scrapy/security/advisories/GHSA-76g3-c3x4-crvx"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-84366"
}, {
"type" : "WEB",
"url" : "https://github.com/scrapy/scrapy/commit/9523e1ec8c41fde265a26d14563d178b6f1ad04b"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/scrapy/scrapy"
}, {
"type" : "WEB",
"url" : "https://github.com/scrapy/scrapy/releases/tag/2.17.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-319" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-02T22:50:44Z",
"nvd_published_at" : "2026-09-01T21:18:47Z"
}
}