Requests is a HTTP library. Prior to version 2.33.0, the requests.utils.extract_zipped_paths() utility function uses a predictable filename when extracting files from zip archives into the system temporary directory. If the target file already exists, it is reused without validation. A local attacker with write access to the temp directory could pre-create a malicious file that would be loaded in place of the legitimate one. Standard usage of the Requests library is not affected by this vulnerability. Only applications that call extract_zipped_paths() directly are impacted. Starting in version 2.33.0, the library extracts files to a non-deterministic location. If developers are unable to upgrade, they can set TMPDIR in their environment to a directory with restricted write access.
CVE-2026-25645
This medium-severity CVE scores 4.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 4.4(low)
- EG Risk
- 20(Track)EG Risk 20/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 computedSeverity44% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
March 25, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/psf/requests/commit/66d21cb07bd6255b1280291c4fafb71803cdb3b7
- security-advisories@githubhttps://github.com/psf/requests/releases/tag/v2.33.0
- security-advisories@githubhttps://github.com/psf/requests/security/advisories/GHSA-gc5v-m9x4-r6x2
Vendor Advisories for CVE-2026-25645(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| requests | 0.0.1 ... 2.9.2 (157 versions) | 2.33.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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.
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 12:50 UTCEG score recompute
- 2026-07-27 12:50 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-25645?
When was CVE-2026-25645 disclosed?
Is CVE-2026-25645 actively exploited?
What is the CVSS score of CVE-2026-25645?
How do I remediate CVE-2026-25645?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25645
Is Your Infrastructure Affected by CVE-2026-25645?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.