# CVE-2025-50817: Code injection in n/a > The Python-Future library automatically imports test.py from the current directory, potentially allowing arbitrary code execution if an attacker can write files there. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 Aug 2025 - **Updated:** 26 Sep 2025 - **Also known as:** ROOT-APP-PYPI-CVE-2025-50817, SUSE-SU-2025:03028-1, SUSE-SU-2025:03029-1, SUSE-SU-2025:03038-1, SUSE-SU-2025:03049-1 ## What is CVE-2025-50817? CVE-2025-50817 is a medium-severity code injection vulnerability in n/a, published on 14 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2025-50817? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `python-future` | SUSE:Enterprise Storage 7.1 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Linux Enterprise Micro 5.1 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Micro 5.2 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Micro 5.3 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Micro 5.4 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Micro 5.5 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 0.15.2-3.6.1 | | `python-future` | SUSE:Linux Enterprise Module for Python 3 15 SP6 | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Linux Enterprise Module for Python 3 15 SP7 | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 0.15.2-3.8.1 | | `python-future` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.15.2-3.8.1 | | `python-future` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 0.18.3-150400.6.6.1 | | `python-future` | SUSE:Manager Proxy LTS 4.3 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | SUSE:Manager Server LTS 4.3 | All versions | 0.18.2-150300.3.6.1 | | `python-future` | openSUSE:Leap 15.6 | All versions | 0.18.3-150400.6.6.1 | ## How do I fix CVE-2025-50817? No fix published yet. ## Is CVE-2025-50817 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50817 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-50817 and fix it if it is affected. What it is: CVE-2025-50817 is a medium-severity code injection vulnerability in n/a, published on 14 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50817 exists. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-50817/ (Markdown: https://insights.sbomify.com/CVE-2025-50817/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-50817 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-50817 - OSV: https://osv.dev/vulnerability/CVE-2025-50817 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-50817/ Summaries are generated and may contain mistakes; the official description above is the record.