CVE-2026-25645: Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function
Noroxi assessment
Priority: Monitor (action score 22/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 python-requests 2.31.0-3 on Azure Linux 3.0 2.31.0-4; azl3 python-requests 2.31.0-4 on Azure Linux 3.0 2.31.0-4; cbl2 python-requests 2.27.1-8 on CBL Mariner 2.0 2.27.1-9.
Low priority for now. Upgrade to azl3 python-requests 2.31.0-3 on Azure Linux 3.0 2.31.0-4; azl3 python-requests 2.31.0-4 on Azure Linux 3.0 2.31.0-4; cbl2 python-requests 2.27.1-8 on CBL Mariner 2.0 2.27.1-9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- CWE-377
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · GitHub_M
- 4.4
- 1.1 point gap
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| python | requests | cpe:2.3:a:python:requests |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- python requestsbefore 2.33.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
psf requests
- < 2.33.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.20 | py3-requests | before 2.33.1-r0 | 2.33.1-r0 |
| Debian:12 | requests | from 0 | — |
| Debian:14 | requests | before 2.34.2-1 | 2.34.2-1 |
| openSUSE:Leap 16.0 | python-requests | before 2.32.4-160000.3.1 | 2.32.4-160000.3.1 |
| openSUSE:Tumbleweed | python-requests | before 2.33.0-1.1 | 2.33.0-1.1 |
| PyPI | requests | before 2.33.0 | 2.33.0 |
| SUSE:Linux Enterprise Module for Public Cloud 12 | python-requests | before 2.24.0-8.26.1 | 2.24.0-8.26.1 |
| SUSE:Linux Micro 6.0 | python-requests | before 2.32.3-3.1 | 2.32.3-3.1 |
| SUSE:Linux Micro 6.1 | python-requests | before 2.32.4-slfo.1.1_2.1 | 2.32.4-slfo.1.1_2.1 |
| SUSE:Linux Micro 6.2 | python-requests | before 2.32.4-160000.3.1 | 2.32.4-160000.3.1 |
Same product
python: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-18074The Requests package before 2.20.0 for Python sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http32Monitor
- CVE-2023-32681Unintended leak of Proxy-Authorization header in requests25Monitor
- CVE-2014-1830Requests (aka python-requests) before 2.3.0 allows remote servers to obtain sensitive information by reading the Proxy-Authorization header 21Monitor
Published before and after this one in the same product
- ← EarlierCVE-2014-1829Oct 15, 2014 · Requests (aka python-requests) before 2.3.0 allows remote servers to obtain a netrc password by reading the Authorization header in a redire21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 python-requests 2.31.0-3 on Azure Linux 3.0 | 2.31.0-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 python-requests 2.31.0-4 on Azure Linux 3.0 | 2.31.0-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 python-requests 2.27.1-8 on CBL Mariner 2.0 | 2.27.1-9 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 python-requests 2.27.1-8 on CBL-Mariner 2.0 | 2.27.1-9 · Release Notes | Microsoft (MSRC) |
| alpine:py3-requests | 2.33.1-r0 · Alpine:v3.20 | Package registry (OSV) |
| debian:requests | 2.34.2-1 · Debian:14 | Package registry (OSV) |
| opensuse:python-requests | 2.33.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:requests | 2.33.0 | Package registry (OSV) |
| suse:python-requests | 2.24.0-8.26.1 · SUSE:Linux Enterprise Module for Public Cloud 12 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2025-11-16 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-130 d
- Published
- TodayOct 30, 2026+219 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-377 · Insecure Temporary FileCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.