ghsa-xqrq-4mgf-ff32
Vulnerability from github
Published
2025-08-14 18:31
Modified
2025-10-06 20:33
Severity ?
7.3 (High) - CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Summary
Withdrawn Advisory: Python-Future Module Arbitrary Code Execution via Unintended Import of test.py
Details

Withdrawn Advisory

This advisory has been withdrawn because it describes a documented feature of Python’s import system in the handling of sys.path. For more information, see https://github.com/PythonCharmers/python-future/issues/650.

Original 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.

Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "future"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.14.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-50817"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-08-14T20:36:51Z",
    "nvd_published_at": "2025-08-14T17:15:40Z",
    "severity": "HIGH"
  },
  "details": "## Withdrawn Advisory\nThis advisory has been withdrawn because it describes a documented feature of Python\u2019s import system in the handling of sys.path. For more information, see https://github.com/PythonCharmers/python-future/issues/650.\n\n## Original Description\n\nA 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\u2019s import system in the handling of sys.path.",
  "id": "GHSA-xqrq-4mgf-ff32",
  "modified": "2025-10-06T20:33:43Z",
  "published": "2025-08-14T18:31:30Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-50817"
    },
    {
      "type": "WEB",
      "url": "https://github.com/PythonCharmers/python-future/issues/650#issuecomment-3251016598"
    },
    {
      "type": "WEB",
      "url": "https://gist.github.com/fried/d2108a4932f3a22712dfc04598b5b8ce"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/PythonCharmers/python-future"
    },
    {
      "type": "WEB",
      "url": "https://github.com/PythonCharmers/python-future/blob/v1.0.0/src/future/standard_library/__init__.py#L491"
    },
    {
      "type": "WEB",
      "url": "https://medium.com/@abcd_68700/cve-2025-50817-python-future-module-arbitrary-code-execution-via-unintended-import-of-test-py-f0818ea93cf4"
    },
    {
      "type": "WEB",
      "url": "https://pypi.org/project/future"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Withdrawn Advisory: Python-Future Module Arbitrary Code Execution via Unintended Import of test.py",
  "withdrawn": "2025-10-06T20:33:43Z"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.