CVE-2025-50817

A vulnerability in the Python-Future 1.0.0 module allows for arbitrary code execution via the unintended import of a file named test.py. When the module is loaded, it automatically imports test.py, if present in the same directory or in the sys.path. This behavior can be exploited by an attacker who has the ability to write files to the server, allowing the execution of arbitrary code. NOTE: Multiple third parties have disputed this issue and stated that it is not a security flaw in python-future and is a documented feature of Python’s import system in the handling of sys.path.

Published: 2025-08-14 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-50817 is rated Low Risk (39.4/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.27%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-50817

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-10 0.05% 0.27% +0.22%
2 2026-03-20 0.03% 0.05% +0.02%
3 2026-01-10 — 0.03% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-50817

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.4 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.5 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-50817

GitHub Security Advisory for CVE-2025-50817

GHSA-xqrq-4mgf-ff32 · Severity: high · Ecosystem: pip — Withdrawn Advisory: Python-Future Module Arbitrary Code Execution via Unintended Import of test.py

OS Trackers for CVE-2025-50817

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2025-50817
suse high — https://www.suse.com/security/cve/CVE-2025-50817/
ubuntu medium CVE-2025-50817 medium priority: Ubuntu including 1 source packages (python-future), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): not-affected 5, DNE 2, needs-triage 1. https://ubuntu.com/security/CVE-2025-50817

Affected software / configurations for CVE-2025-50817

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-50817

cvelogic Threat Intelligence