p PatchFirst

PatchFirst · Latest vulnerabilities

Python stack vulnerabilities · Page 97

Vulnerabilities published for Python in the last 30 days: 350. Listed in the KEV catalogue: 1.

RSS ↗ JSON ↗
Filter vulnerabilities
Python

Vulnerabilities: 7131

  1. CVE-2026-7210

    Medium · CVSS 6.3EPSS 0.67%Fix available

    The expat and elementtree parsers use insufficient entropy for XML hash-flooding protection

    `xml.parsers.expat` and `xml.etree.ElementTree` use insufficient entropy for Expat hash-flooding protection, which allows a crafted XML document to trigger hash flooding.\r\n\r\nFully mitigating this vulnerability requires both updating libexpat to 2.8.0 or later and applying this patch.

    python python3.11 python3.13 python3.14 python2.7 python3.4 python3.5 python2.7 python3.5 python2.7 python3.6 python3.7Operating systems Python
    • Update to 3.10.22
    • Update to 3.11.16
    • Update to 3.12.14
    • Update to 3.13.14
    • Update to 3.14.6
    • Update to 3.14.6-1
    • Update to 3.15.0b2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  2. CVE-2026-44226

    Medium · CVSS 5.3EPSS 0.34%Fix available

    pyLoad: Unauthenticated traceback disclosure via global exception handler in WebUI

    pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev100, pyload-ng WebUI returns full Python traceback details to clients on unhandled exceptions. Because /web/<path:filename> is reachable without authentication and renders attacker-controlled template names, an unauthenticated user can reliably trigger a server exception (for example by requesting a non-existent template) and receive internal stack traces in the HTTP response. This vulnerability is fixed in 0.5.0b3.dev100.

    pyload pyload-ngPython
    • Update to 0.5.0b3.dev100
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  3. CVE-2026-42315

    High · CVSS 8.1EPSS 0.4%Fix available

    pyLoad: Path Traversal via Package Folder Name in set_package_data

    pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev100, when passing a folder name in the set_package_data() API function call inside the data object with key "_folder", there is no sanitization at all, allowing a user with Perms.MODIFY to specify arbitrary directories as download locations for a package. This vulnerability is fixed in 0.5.0b3.dev100.

    pyload pyload-ngPython
    • Update to 0.5.0b3.dev100
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  4. CVE-2026-42314

    Medium · CVSS 6.5EPSS 0.34%Fix available

    pyLoad: Path Traversal via Package Folder Name

    pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev100, package folder names are sanitized using insufficient string replacement. The pattern ....// becomes .._ after replacement (partial removal), leaving .. which can be exploited when the path is later resolved by the OS. This vulnerability is fixed in 0.5.0b3.dev100.

    pyload pyload-ngPython
    • Update to 0.5.0b3.dev100
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  5. CVE-2026-42312

    Medium · CVSS 6.8EPSS 0.17%Fix available

    pyload-ng: non-admin SETTINGS users can disable outbound TLS peer verification

    pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev100, the set_config_value() API method (@permission(Perms.SETTINGS)) in src/pyload/core/api/__init__.py gates security-sensitive options behind a hand-maintained allowlist ADMIN_ONLY_CORE_OPTIONS. The option ("general", "ssl_verify") is not on that allowlist. Any authenticated user with the non-admin SETTINGS permission can set general.ssl_verify = off, and every subsequent outbound pycurl request is made with SSL_VERIFYPEER=0 and SSL_VERIFYHOST=0 — TLS peer and hostname verification are fully disabled. An on-path attacker can then present forged certific

    pyload pyload-ngPython
    • Update to 0.5.0b3.dev100
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  6. CVE-2026-42313

    High · CVSS 8.3EPSS 0.4%Fix available

    pyload-ng: non-admin SETTINGS users can redirect all outbound traffic through an attacker-controlled proxy

    pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev100, the set_config_value() API method (@permission(Perms.SETTINGS)) in src/pyload/core/api/__init__.py gates security-sensitive options behind a hand-maintained allowlist ADMIN_ONLY_CORE_OPTIONS. The allowlist contains ("proxy", "username") and ("proxy", "password") — which protect the proxy credentials — but it does not include ("proxy", "enabled"), ("proxy", "host"), ("proxy", "port"), or ("proxy", "type"). Any authenticated user with the non-admin SETTINGS permission can enable proxying and point pyload at any host they control. From that point, every

    pyload pyload-ngPython
    • Update to 0.5.0b3.dev100
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  7. CVE-2026-2393

    High · CVSS 7.1EPSS 0.29%Fix available

    Server-Side Request Forgery (SSRF) in mlflow/mlflow

    A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0. The `_create_webhook()` function in `mlflow/server/handlers.py` accepts a user-controlled `url` parameter without validation, and the `_send_webhook_request()` function in `mlflow/webhooks/delivery.py` sends HTTP POST requests to this attacker-controlled URL. This allows an authenticated attacker to force the MLflow backend to send HTTP requests to internal services, cloud metadata endpoints, or arbitrary external servers. The lack of input sanitization, URL scheme filtering, or allowlist validation on the webhook URL enables exploitation, potentially

    mlflow/mlflow mlflowPython
    • Update to 3.10.0
    • Update to 3.9.0
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  8. GHSA-88q9-cmp2-c2vq

    Medium · CVSS 4.3Fix available

    oxidize-pdf: NaN/inf bypass in colour content-stream emission causes PDF rejection (DoS)

    ### Impact `oxidize-pdf` defines `Color` as a `pub enum` with public tuple-struct variants `Rgb(f64, f64, f64)`, `Gray(f64)`, and `Cmyk(f64, f64, f64, f64)`. The constructors `Color::rgb`, `Color::gray`, and `Color::cmyk` clamp incoming components to `[0.0, 1.0]`, but because the variants are `pub`, callers can construct values directly without going through the constructors: ```rust let safe = Color::rgb(f64::NAN, 0.5, 0.5); // clamps NaN to 0.0 let attack = Color::Rgb(f64::NAN, 0.5, 0.5); // bypasses clamp Color: Copy allows the non-finite value to propagate freely through API surfaces and serialisation. When such a va

    oxidize-pdf oxidizepdf.net oxidize-pdfPython
    • Update to 0.5.0
    • Update to 0.8.0
    • Update to 2.6.0
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  9. CVE-2026-44201

    Medium · CVSS 5.3EPSS 0.26%Fix available

    Wagtail: Improper restriction handling on Documents and Images API

    Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, the Documents and Images API incorrectly listed items in private collections. A user with access to the API could see the filename and name of documents and images in private collections. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.

    wagtail wagtail wagtail wagtailPython
    • Update to 7.0.7
    • Update to 7.3.2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  10. CVE-2026-44200

    Medium · CVSS 6.5EPSS 0.2%Fix available

    Wagtail: Improper permission handling when copying pages

    Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user with limited access to pages could copy a page they don't have access to to an area of the site they do. Once coped, they'd be able to view its contents, and potentially publish it. Permissions were correctly checked for the copy destination, but not for the source page. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.

    wagtail wagtail wagtail wagtailPython
    • Update to 7.0.7
    • Update to 7.3.2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  11. CVE-2026-44199

    Medium · CVSS 6.5EPSS 0.17%Fix available

    Wagtail: Improper permission handling when deleting form submissions

    Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user with limited access to form pages could delete submissions to form pages they don't have access to by crafting a form submission to delete submissions on a page they do have access to for submissions they don't. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.

    wagtail wagtail wagtail wagtailPython
    • Update to 7.0.7
    • Update to 7.3.2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  12. CVE-2026-44198

    Medium · CVSS 4.3EPSS 0.16%Fix available

    Wagtail: Improper permission handling when viewing page history

    Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user without the ability to edit a page could still access the history report for the page, potentially resulting in disclosure of sensitive information. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.

    wagtail wagtail wagtail wagtailPython
    • Update to 7.0.7
    • Update to 7.3.2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  13. CVE-2026-44197

    Medium · CVSS 6.5EPSS 0.2%Fix available

    Wagtail: Improper permission handling when comparing revisions

    Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user without the ability to edit a page could access revisions of the page through the revision compare view if they knew the primary key of two revisions. This could potentially result in disclosure of sensitive information. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.

    wagtail wagtail wagtail wagtailPython
    • Update to 7.0.7
    • Update to 7.3.2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  14. CVE-2026-7820

    Medium · CVSS 6.9EPSS 0.21%Fix available

    pgAdmin 4: Account-lockout bypass via Flask-Security default /login view

    Improper restriction of excessive authentication attempts (CWE-307) in pgAdmin 4. pgAdmin enforces MAX_LOGIN_ATTEMPTS only inside its custom /authenticate/login view. Flask-Security's default /login view, which is registered automatically by security.init_app() and is reachable on every server, never consulted the User.locked field: pgAdmin's User model relied on Flask-Security's UserMixin.is_locked() (which always returns 'not locked') and Flask-Login's is_active (which only checks the active column, not locked). An attacker who triggered an account lockout via /authenticate/login could therefore obtain a session by re-submitting valid cred

    pgadmin 4 pgadmin4Python
    • Update to 9.15
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  15. CVE-2026-7819

    High · CVSS 7.2EPSS 0.33%Fix available

    pgAdmin 4: Symbolic-link path traversal in File Manager allows arbitrary file write

    Symbolic-link path traversal (CWE-61, CWE-22) in pgAdmin 4 File Manager. check_access_permission used os.path.abspath, which resolves '..' but does not resolve symbolic links, while the subsequent kernel write follows symlinks. An authenticated user could plant a symbolic link inside their own storage directory pointing outside it and induce pgAdmin to write to any path reachable by the pgAdmin process. Fix switches the access check to os.path.realpath for both source and destination, and adds an _open_upload_target helper that opens the target with O_NOFOLLOW (mode 0o600) to close the leaf-component TOCTOU between the access check and the

    pgadmin 4 pgadmin4Python
    • Update to 9.15
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  16. CVE-2026-7818

    High · CVSS 7.3EPSS 0.13%Fix available

    pgAdmin 4: Unsafe deserialization (CWE-502) in file-backed session manager leads to remote code execution

    Deserialization of untrusted data (CWE-502) in pgAdmin 4 FileBackedSessionManager. The session manager performed unsafe deserialization of session-file contents (using Python's standard object-serialization module) before performing any HMAC integrity check. Any file dropped into the sessions directory was deserialized unconditionally. An authenticated user with write access to the sessions directory (whether by misconfiguration or in combination with another path-traversal flaw) could plant a crafted serialized payload to achieve operating-system level remote code execution under the pgAdmin process identity. Fix prepends a 64-byte hex SHA

    pgadmin 4 pgadmin4Python
    • Update to 9.15
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  17. CVE-2026-7817

    High · CVSS 7.1EPSS 0.22%Fix available

    pgAdmin 4: Local file inclusion and server-side request forgery in LLM API configuration endpoints

    Local file inclusion (LFI) and server-side request forgery (SSRF) vulnerabilities in pgAdmin 4 LLM API configuration endpoints. User-supplied api_key_file and api_url preferences were passed to the LLM provider clients without validation. An authenticated user could read arbitrary server-side files by pointing api_key_file at any path readable by the pgAdmin process, or coerce pgAdmin into making requests to internal targets (e.g. cloud metadata services such as 169.254.169.254) by setting api_url, exploiting the chat path and model-list endpoints. Fix restricts api_key_file to the user's private storage (server mode) or home directory (des

    pgadmin 4 pgadmin4Python
    • Update to 9.15
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  18. CVE-2026-7816

    High · CVSS 8.7EPSS 1.44%Fix available

    pgAdmin 4: OS command injection in Import/Export query export via psql metacommand breakout

    OS command injection (CWE-78) vulnerability in pgAdmin 4 Import/Export query export. User-supplied input was interpolated directly into a psql \copy metacommand template without sanitization. An authenticated user could inject ") TO PROGRAM 'cmd'" to break out of the \copy (...) context and achieve arbitrary command execution on the pgAdmin server, or ") TO '/path'" for arbitrary file write. Additional fields (format, on_error, log_verbosity) were also raw-interpolated and exploitable. Fix adds a parens-balance parser modeled on psql's strtokx tokenizer, allow-lists format/on_error/log_verbosity, rejects null bytes in the query, and tighten

    pgadmin 4 pgadmin4Python
    • Update to 9.15
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  19. CVE-2026-7815

    High · CVSS 8.7EPSS 0.46%Fix available

    pgAdmin 4: SQL injection in Maintenance tool option values leading to remote code execution

    SQL injection vulnerability in pgAdmin 4 Maintenance Tool. Four user-supplied JSON fields (buffer_usage_limit, vacuum_parallel, vacuum_index_cleanup, reindex_tablespace) were concatenated directly into the rendered VACUUM/ANALYZE/REINDEX command and passed to psql --command. An authenticated user with the tools_maintenance permission could break out of the option syntax and execute arbitrary SQL on the connected PostgreSQL server. The injected SQL could in turn invoke COPY ... TO PROGRAM to escalate to operating-system command execution on the database host. Fix introduces server-side allow-listing of all four fields and switches reindex_ta

    pgadmin 4 pgadmin4Python
    • Update to 9.15
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

  20. CVE-2026-7814

    Medium · CVSS 4.8EPSS 0.16%Fix available

    pgAdmin 4: Stored XSS via crafted PostgreSQL object names in Browser Tree and Explain Visualizer

    Stored cross-site scripting (XSS) vulnerability in pgAdmin 4 Browser Tree and Explain Visualizer modules. User-controlled PostgreSQL object names (database, schema, table, column, etc.) were assigned to DOM elements via innerHTML, allowing crafted object names containing HTML markup to execute attacker-supplied JavaScript in the browser of any pgAdmin user who navigated to or executed EXPLAIN over the malicious object. Fix replaces innerHTML with textContent. This issue affects pgAdmin 4: before 9.15.

    pgadmin 4 pgadmin4Python
    • Update to 9.15
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →