p PatchFirst

PatchFirst · Latest vulnerabilities

Python stack vulnerabilities · Page 175

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

Filter vulnerabilities
Python

Vulnerabilities: 7135

  1. PYSEC-2025-5

    Not ratedNo fix published

    Exfiltrates user cookies to hardcoded server endpoint during normal operations

    Published in 2020, the autodzee package is a Python library that bypasses Deezer API restrictions to download music. The package was found to exfiltrate user data to a hardcoded server, which could be used for malicious purposes.

    Published Updated
  2. PYSEC-2025-3

    Not ratedNo fix published

    When using the project to bypass Deezer API restrictions, project exfiltrates user data to a hardcoded server.

    Published in 2019, the autodzee package is a Python library that bypasses Deezer API restrictions to download music. The package was found to exfiltrate user data to a hardcoded server, which could be used for malicious purposes.

    Published Updated
  3. PYSEC-2025-4

    Not ratedNo fix published

    When using the project to bypass Deezer API restrictions, project exfiltrates user data to a hardcoded server.

    Published in 2019, the automslc package is a Python library that bypasses Deezer API restrictions to download music. The package was found to exfiltrate user data to a hardcoded server, which could be used for malicious purposes.

    Published Updated
  4. CVE-2025-1716

    Medium · CVSS 5.3EPSS 1.72%Fix available

    picklescan - Security scanning bypass via 'pip main'

    picklescan before 0.0.21 does not treat 'pip' as an unsafe global. An attacker could craft a malicious model that uses Pickle to pull in a malicious PyPI package (hosted, for example, on pypi.org or GitHub) via `pip.main()`. Because pip is not a restricted global, the model, when scanned with picklescan, would pass security checks and appear to be safe, when it could instead prove to be problematic.

    • Update to 0.0.21
    • Update to 0.0.22
    Published Updated
  5. CVE-2023-25574

    Critical · CVSS 10EPSS 0.36%Fix available

    JupyterHub's LTI13Authenticator: JWT signature not validated

    `jupyterhub-ltiauthenticator` is a JupyterHub authenticator for learning tools interoperability (LTI). LTI13Authenticator that was introduced in `jupyterhub-ltiauthenticator` 1.3.0 wasn't validating JWT signatures. This is believed to allow the LTI13Authenticator to authorize a forged request. Only users that has configured a JupyterHub installation to use the authenticator class `LTI13Authenticator` are affected. `jupyterhub-ltiauthenticator` version 1.4.0 removes LTI13Authenticator to address the issue. No known workarounds are available.

    • Update to 1.4.0
    Published Updated
  6. CVE-2025-27145

    Low · CVSS 3.6EPSS 0.47%Fix available

    copyparty renders unsanitized filenames as HTML when user uploads empty files

    copyparty, a portable file server, has a DOM-based cross-site scripting vulnerability in versions prior to 1.16.15. The vulnerability is considered low-risk. By handing someone a maliciously-named file, and then tricking them into dragging the file into copyparty's Web-UI, an attacker could execute arbitrary javascript with the same privileges as that user. For example, this could give unintended read-access to files owned by that user. The bug is triggered by the drag-drop action itself; it is not necessary to actually initiate the upload. The file must be empty (zero bytes). Note that, as a general-purpose webserver, it is intentionally pos

    • Update to 1.16.15
    Published Updated
  7. CVE-2025-26622

    Low · CVSS 2.3EPSS 0.33%Fix available

    sqrt doesn't define rounding behavior in Vyper

    vyper is a Pythonic Smart Contract Language for the EVM. Vyper `sqrt()` builtin uses the babylonian method to calculate square roots of decimals. Unfortunately, improper handling of the oscillating final states may lead to sqrt incorrectly returning rounded up results. This issue is being addressed and a fix is expected in version 0.4.1. Users are advised to upgrade as soon as the patched release is available. There are no known workarounds for this vulnerability.

    • Update to 0.4.1
    Published Updated
  8. CVE-2025-27104

    Low · CVSS 2.3EPSS 0.45%Fix available

    double eval in For List Iter in Vyper

    vyper is a Pythonic Smart Contract Language for the EVM. Multiple evaluation of a single expression is possible in the iterator target of a for loop. While the iterator expression cannot produce multiple writes, it can consume side effects produced in the loop body (e.g. read a storage variable updated in the loop body) and thus lead to unexpected program behavior. Specifically, reads in iterators which contain an ifexp (e.g. `for s: uint256 in ([read(), read()] if True else [])`) may interleave reads with writes in the loop body. Vyper for loops allow two kinds of iterator targets, namely the `range()` builtin and an iterable type, like SArr

    • Update to 0.4.1
    Published Updated
  9. CVE-2025-27105

    Low · CVSS 2.3EPSS 0.57%Fix available

    AugAssign evaluation order causing OOB write within the object in Vyper

    vyper is a Pythonic Smart Contract Language for the EVM. Vyper handles AugAssign statements by first caching the target location to avoid double evaluation. However, in the case when target is an access to a DynArray and the rhs modifies the array, the cached target will evaluate first, and the bounds check will not be re-evaluated during the write portion of the statement. This issue has been addressed in version 0.4.1 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

    • Update to 0.4.1
    Published Updated
  10. CVE-2025-1403

    High · CVSS 8.6EPSS 0.72%Fix available

    Qiskit SDK denial of service

    Qiskit SDK 0.45.0 through 1.2.4 could allow a remote attacker to cause a denial of service using a maliciously crafted QPY file containing a malformed symengine serialization stream which can cause a segfault within the symengine library.

    • Update to 1.3.0
    Published Updated
  11. CVE-2025-26623

    Medium · CVSS 5.3EPSS 0.92%Fix available

    Use After Free in Exiv2

    Exiv2 is a C++ library and a command-line utility to read, write, delete and modify Exif, IPTC, XMP and ICC image metadata. A heap buffer overflow was found in Exiv2 versions v0.28.0 to v0.28.4. Versions prior to v0.28.0, such as v0.27.7, are **not** affected. Exiv2 is a command-line utility and C++ library for reading, writing, deleting, and modifying the metadata of image files. The heap overflow is triggered when Exiv2 is used to write metadata into a crafted image file. An attacker could potentially exploit the vulnerability to gain code execution, if they can trick the victim into running Exiv2 on a crafted image file. Note that this bug

    • Update to 0.28.4+dfsg-2
    • Update to 0.28.5
    Published Updated
  12. CVE-2025-25305

    High · CVSS 7EPSS 0.25%Fix available

    SSL validation for outgoing requests in Home Assistant Core and used libs not correct

    Home Assistant Core is an open source home automation that puts local control and privacy first. Affected versions are subject to a potential man-in-the-middle attacks due to missing SSL certificate verification in the project codebase and used third-party libraries. In the past, `aiohttp-session`/`request` had the parameter `verify_ssl` to control SSL certificate verification. This was a boolean value. In `aiohttp` 3.0, this parameter was deprecated in favor of the `ssl` parameter. Only when `ssl` is set to `None` or provided with a correct configured SSL context the standard SSL certificate verification will happen. When migrating integrati

    • Update to 2024.1.6
    Published Updated
  13. CVE-2025-25297

    High · CVSS 8.6EPSS 0.67%Fix available

    Label Studio allows Server-Side Request Forgery in the S3 Storage Endpoint

    Label Studio is an open source data labeling tool. Prior to version 1.16.0, Label Studio's S3 storage integration feature contains a Server-Side Request Forgery (SSRF) vulnerability in its endpoint configuration. When creating an S3 storage connection, the application allows users to specify a custom S3 endpoint URL via the s3_endpoint parameter. This endpoint URL is passed directly to the boto3 AWS SDK without proper validation or restrictions on the protocol or destination. The vulnerability allows an attacker to make the application send HTTP requests to arbitrary internal services by specifying them as the S3 endpoint. When the storage sy

    • Update to 1.16.0
    Published Updated
  14. CVE-2025-25296

    Medium · CVSS 6.1EPSS 1.9%Public exploitFix available

    Label Studio allows Cross-Site Scripting (XSS) via GET request to `/projects/upload-example` endpoint

    Label Studio is an open source data labeling tool. Prior to version 1.16.0, Label Studio's `/projects/upload-example` endpoint allows injection of arbitrary HTML through a `GET` request with an appropriately crafted `label_config` query parameter. By crafting a specially formatted XML label config with inline task data containing malicious HTML/JavaScript, an attacker can achieve Cross-Site Scripting (XSS). While the application has a Content Security Policy (CSP), it is only set in report-only mode, making it ineffective at preventing script execution. The vulnerability exists because the upload-example endpoint renders user-provided HTML co

    • Update to 1.16.0
    Published Updated
  15. CVE-2025-25295

    High · CVSS 8.7EPSS 0.76%Fix available

    Label Studio has a Path Traversal Vulnerability via image Field

    Label Studio is an open source data labeling tool. A path traversal vulnerability in Label Studio SDK versions prior to 1.0.10 allows unauthorized file access outside the intended directory structure. The flaw exists in the VOC, COCO and YOLO export functionalities. These functions invoke a `download` function on the `label-studio-sdk` python package, which fails to validate file paths when processing image references during task exports. By creating tasks with path traversal sequences in the image field, an attacker can force the application to read files from arbitrary server filesystem locations when exporting projects in any of the mentio

    • Update to 1.0.10
    Published Updated
  16. CVE-2024-3220

    Low · CVSS 2.3EPSS 0.71%Fix available

    Default mimetype known files writeable on Windows

    There is a defect in the CPython standard library module “mimetypes” where on Windows the default list of known file locations are writable meaning other users can create invalid files to cause MemoryError to be raised on Python runtime startup or have file extensions be interpreted as the incorrect file type. This defect is caused by the default locations of Linux and macOS platforms (such as “/etc/mime.types”) also being used on Windows, where they are user-writable locations (“C:\etc\mime.types”). To work-around this issue a user can call mimetypes.init() with an empty list (“[]”) on Windows platforms to avoid using the default list of k

    • Update to 3.11.18
    • Update to 3.12.16
    • Update to 3.13.18
    • Update to 3.14.9
    • Update to 3.15.1
    • Update to 3.16.0
    Published Updated
  17. CVE-2024-12797

    Medium · CVSS 6.3EPSS 2.53%Fix available

    RFC7250 handshakes with unauthenticated servers don't abort as expected

    Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The

    • Update to 3.2.4
    • Update to 3.3.3
    • Update to 3.4.1
    • Update to 3.4.1-1
    • Update to 44.0.1
    Published Updated
  18. CVE-2024-8550

    High · CVSS 7.5EPSS 0.52%No fix published

    Local File Inclusion (LFI) in modelscope/agentscope

    A Local File Inclusion (LFI) vulnerability exists in the /load-workflow endpoint of modelscope/agentscope version v0.0.4. This vulnerability allows an attacker to read arbitrary files from the server, including sensitive files such as API keys, by manipulating the filename parameter. The issue arises due to improper sanitization of user input passed to the os.path.join function, which can be exploited to access files outside the intended directory.

    Published Updated

Check your server

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

Check your server →