CVE-2026-84366

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Sep 1, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github_release Patch Available

2.17.0

Patch available: scrapy/scrapy 2.17.0

https://github.com/scrapy/scrapy/releases/tag/2.17.0
github_commit Patch Available

commit 9523e1ec8c41 (scrapy/scrapy)

Patch available: scrapy/scrapy 2.17.0 (contains commit 9523e1ec8c41)

https://github.com/scrapy/scrapy/commit/9523e1ec8c41fde265a26d14563d178b6f1ad04b
github Patch Available🟡 PoC Available

S3DownloadHandler sends signed S3 requests over plaintext HTTP by default · Advisory · scrapy/scrapy · GitHub

https://github.com/scrapy/scrapy/security/advisories/GHSA-76g3-c3x4-crvx

Vendor Advisories for CVE-2026-84366(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-scrapy2.10.0-1 ... 2.9.0-2 (27 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-scrapy2.12.0-2 ... 2.18.0-1 (14 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-scrapy2.12.0-2 ... 2.16.0-2 (12 versions)2.17.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
scrapy0.10.4.2364 ... 2.9.0 (112 versions)2.17—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 20:03 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 20:40 UTCEG score recompute
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-16 18:38 UTCEG score recompute
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 06:02 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 06:05 UTCEG score recompute
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-15 03:12 UTCEPSS rescore
  12. 2026-09-13 18:55 UTCEG score recompute
  13. 2026-09-12 19:30 UTCEG score recompute
  14. 2026-09-11 20:10 UTCEG score recompute
  15. 2026-09-10 20:32 UTCEG score recompute
  16. 2026-09-08 23:18 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 02:33 UTCEG score recompute
  19. 2026-09-06 14:06 UTCEG score recompute
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-06 02:25 UTCEG score recompute
  22. 2026-09-05 15:31 UTCEPSS rescore
  23. 2026-09-04 15:19 UTCEG score recompute
  24. 2026-09-04 05:07 UTCEPSS rescore
  25. 2026-09-03 04:01 UTCEG score recompute
Show 5 more
  1. 2026-09-02 16:20 UTCEG score recompute
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 21:26 UTCEG score recompute
  4. 2026-09-01 20:33 UTCEG score recompute
  5. 2026-09-01 20:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84366?
CVE-2026-84366 is a high vulnerability published on September 1, 2026. 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"]…
When was CVE-2026-84366 disclosed?
CVE-2026-84366 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84366 actively exploited?
CVE-2026-84366 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.4% of all scored CVEs.
What is the CVSS score of CVE-2026-84366?
CVE-2026-84366 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-84366?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84366, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84366

Explore →

Is Your Infrastructure Affected by CVE-2026-84366?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs