p PatchFirst

PatchFirst · Latest vulnerabilities

Python stack vulnerabilities · Page 50

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

Filter vulnerabilities
Python

Vulnerabilities: 7131

  1. CVE-2026-70489

    Medium · CVSS 6.5EPSS 0.57%Fix available

    Open WebUI: Instance-wide stall via automation recurrence rules that force multi-second parsing

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.0 until 0.11.0, automation recurrence parsing in backend/open_webui/utils/automations.py anchored minutely and hourly rules at a fixed date of 2000-01-01 and then walked forward one interval at a time to find the next run. A single FREQ=MINUTELY rule enumerates roughly a quarter-century of occurrences synchronously on the event loop that also serves scheduler, HTTP, and WebSocket traffic, and the scheduler recomputes the next run for every claimed row on each poll. This causes availability impact for every other user of the instance. This issue is f

    • Update to 0.11.0
    Published Updated
  2. CVE-2026-54020

    Medium · CVSS 6.3EPSS 0.25%Fix available

    Open WebUI: DNS Rebinding SSRF Bypass

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. Prior to 0.11.0, Open WebUI resolved a hostname during URL validation and rejected private, loopback, and link-local addresses, but the HTTP clients resolved the hostname again at connection time. An authenticated attacker who controlled authoritative DNS for a submitted hostname could answer with a public address during validation and an internal one during connection, reaching cloud metadata, loopback admin APIs, or internal services through URL ingest, chat image_url fetches, image editing, or OAuth profile-picture fetches, with most paths returning the r

    • Update to 0.11.0
    Published Updated
  3. CVE-2026-70488

    Medium · CVSS 4.3EPSS 0.37%Fix available

    Open WebUI: Deletion of directories and file embeddings in other knowledge bases via sync cleanup

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.6 until 0.11.0, the sync cleanup endpoint authorized write access to the knowledge base in the URL but then acted on directory and file ids supplied in the request body without checking that those objects belonged to that knowledge base. A user with write access to one knowledge base could delete directories and remove file embeddings from another knowledge base, causing documents to drop out of retrieval results and breaking chat-with-file for targeted documents without disclosing contents. This issue is fixed in 0.11.0.

    • Update to 0.11.0
    Published Updated
  4. CVE-2026-70487

    Medium · CVSS 5.3EPSS 0.42%Fix available

    Open WebUI: Cross-user file content disclosure via request-scoped direct model knowledge metadata

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.8.8 until 0.11.0, inline direct model metadata accepted client-supplied knowledge attachments without filtering them against the caller's read access. Any authenticated user who knew another user's file id could have the builtin knowledge tools return indexed chunks from that file, causing a read-only cross-user confidentiality loss while leaving knowledge-base permissions and saved workspace model validation unaffected. This issue is fixed in 0.11.0.

    • Update to 0.11.0
    Published Updated
  5. CVE-2026-70486

    High · CVSS 8.2EPSS 0.38%Fix available

    Open WebUI: Same-origin XSS to account takeover via terminal file-preview iframe hardcoding allow-same-origin

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.0 until 0.11.0, the terminal file-preview serveUrl iframe branch always granted allow-same-origin together with allow-scripts for HTML files served from the application origin. Any authenticated user with access to a configured terminal server could cause script in a previewed file to run in the Open WebUI origin, read the victim's session token from localStorage, and take over the account, with possible server-side code execution if the victim was an admin or held workspace.functions. This issue is fixed in 0.11.0.

    • Update to 0.11.0
    Published Updated
  6. CVE-2026-70485

    High · CVSS 7.1EPSS 0.35%Fix available

    Open WebUI: Any authenticated user can reach internal services and cloud metadata via NAT64-encoded URLs

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.0 until 0.11.0, Open WebUI checked whether a user-supplied URL destination was globally routable by applying ipaddress.is_global to the literal IPv6 address without examining IPv4 addresses embedded in transition encodings. On a deployment with a NAT64 gateway, any verified user could wrap an internal or cloud-metadata IPv4 address in the NAT64 well-known prefix, pass the filter, and receive the internal response body through RAG URL ingestion, URL-to-markdown conversion, or web-search content retrieval. This issue is fixed in 0.11.0.

    • Update to 0.11.0
    Published Updated
  7. CVE-2026-70484

    Medium · CVSS 4.3EPSS 0.41%Fix available

    Open WebUI: Users denied the image-generation permission can still generate images via chat completions

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.7.0 until 0.11.0, the legacy chat-completions features block trusted a client-supplied image_generation flag and did not re-check the features.image_generation permission that the direct image routes and native function-calling path enforce. An authenticated user whose image-generation permission had been revoked could still consume the operator's configured image provider through chat completions, spending API credits and provider quota and writing generated files to operator storage, without exposing provider credentials or other users' data. This i

    • Update to 0.11.0
    Published Updated
  8. CVE-2026-70483

    Low · CVSS 3.1EPSS 0.46%Fix available

    Open WebUI: Any authenticated user can cancel another user's chat generation via the chat delete endpoint

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.6 until 0.11.0, DELETE /api/v1/chats/{id} cancelled a chat's in-flight tasks before checking whether the caller could delete that chat. Any authenticated user who knew another user's chat id could abort that user's running model response, title generation, or tag generation, even though the delete was refused and no chat data was deleted, modified, or disclosed. This issue is fixed in 0.11.0.

    • Update to 0.11.0
    Published Updated
  9. CVE-2026-70482

    High · CVSS 8.1EPSS 0.57%Fix available

    Open WebUI: Account takeover via OAuth token exchange accepting tokens issued to any client

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.8.0 until 0.11.0, when ENABLE_OAUTH_TOKEN_EXCHANGE=True, /oauth/{provider}/token/exchange accepts a raw provider access token and validates it by calling the provider userinfo endpoint without confirming which OAuth client the token was issued to. Anyone holding an access token minted for any client registered with the same provider could exchange it for an Open WebUI session as that token user, including applications the operator does not control and has never authorized. This issue is fixed in 0.11.0.

    • Update to 0.11.0
    Published Updated
  10. CVE-2026-70481

    Medium · CVSS 5.4EPSS 0.43%Fix available

    Open WebUI: Any member with write access to a standard channel can edit or delete other members' messages

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.5.0 until 0.11.0, the standard channel message update and delete handlers accepted any caller holding write access on the channel without checking that the caller wrote the message. Because write access is the same grant a member needs to post, any ordinary participant in a shared standard channel could rewrite or permanently delete another participant message, while group and direct message handlers enforced authorship. This issue is fixed in 0.11.0.

    • Update to 0.11.0
    Published Updated
  11. CVE-2026-70480

    Medium · CVSS 4.1EPSS 0.35%Fix available

    Open WebUI: Client-side SSRF via unrestricted external resource loading in Vega/Vega-Lite chart rendering

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.6.34 until 0.11.0, Open WebUI renders vega and vega-lite fenced code blocks in chat content by building a Vega view in the viewer browser without a restricted resource loader. Any user who can place such a block where another user will see it can make that user browser issue attacker-chosen outbound GET requests and read responses from same-origin or CORS-permissive targets into the rendered page. This issue is fixed in 0.11.0.

    • Update to 0.11.0
    Published Updated
  12. CVE-2026-70479

    High · CVSS 7.7EPSS 0.47%Fix available

    Open WebUI: SSRF into internal services via unvalidated sub-resource requests in the Playwright web loader

    Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.6 until 0.11.0, with WEB_LOADER_ENGINE=playwright, the Playwright web loader validates only the top-level page request and lets sub-resource requests pass unvalidated. A page supplied by an authenticated user can use JavaScript to reach blocked internal addresses, and returned DOM can include data read from those addresses in web-search or RAG output. This issue is fixed in 0.11.0.

    • Update to 0.11.0
    Published Updated
  13. CVE-2026-47781

    High · CVSS 8.4EPSS 0.19%Fix available

    pdm: Project-Controlled `.pdm-plugins` Content Executes Before CLI Parsing

    PDM is a Python package and dependency manager. In versions up to and including 2.26.9, PDM automatically loads project-local plugins from a .pdm-plugins directory during initialization, allowing an attacker-controlled file in an untrusted repository checkout to execute arbitrary Python code before any command is parsed. This happens because load_plugins() runs during Core.init() and adds .pdm-plugins via site.addsitedir(), which processes .pth files and immediately executes any line beginning with import, so the code runs with the privileges of the user invoking pdm and even a benign command such as pdm --version triggers it (making the impa

    • Update to 2.27.0
    • Update to 2.27.0-1
    Published Updated
  14. CVE-2026-47764

    High · CVSS 8.4EPSS 0.2%Fix available

    pdm: Path traversal in wheel installation via overridden write_to_fs

    pdm is a Python package and dependency manager supporting the latest PEP standards. Versions prior to 2.27.0 are vulnerable to path traversal through write_to_fs. InstallDestination.write_to_fs() in src/pdm/installers/installers.py overrides the base class to add symlink/hardlink support but replaces the safe _path_with_destdir() (which validates via Path.resolve() + is_relative_to()) with a bare os.path.join() that performs no path validation. A malicious wheel with traversal entries can write arbitrary files. This issue has been fixed in version 2.27.0.

    • Update to 2.27.0
    • Update to 2.27.0-1
    Published Updated
  15. CVE-2026-47763

    Medium · CVSS 6.8EPSS 0.2%Fix available

    pdm: Project-Local State and Config Writes Follow Symlinks

    pdm is a Python package and dependency manager supporting the latest PEP standards. In versions prior to 2.27.0, pdm writes several project-local state or configuration files without symlink protection. If a malicious repository places those files as symlinks, local PDM operations can overwrite the symlink targets. This creates an arbitrary file clobber primitive relative to the privileges of the invoking user. Config.__init__() resolves the project-local pdm.toml path and _save_config() writes to the resolved target. If PROJECT_ROOT/pdm.toml is a symlink to another file, pdm config -l ... updates the target file instead of refusing the write

    • Update to 2.27.0
    • Update to 2.27.0-1
    Published Updated
  16. CVE-2026-15830

    Medium · CVSS 6.9EPSS 1.11%Fix available

    Potential denial-of-service vulnerability via nested geometry collections

    An issue was discovered in Django 6.0 before 6.0.9 and 5.2 before 5.2.18. GeoDjango's `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew MacP

    • Update to 3:5.2.17-1
    • Update to 5.2.17
    • Update to 5.2.18
    • Update to 6.0.8
    • Update to 6.0.9
    • Update to 6.1.1
    Published Updated
  17. CVE-2026-15307

    High · CVSS 8.7EPSS 1.13%Fix available

    Server-side file-write and request forgery via spatial lookups

    An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff user with view permission. A `dict`, or a `str` holding its JSON representation, is opened in write mode regardless of the constructor's `write=False` default, allowing a file with an

    • Update to 2:3.2.12-2ubuntu1.29
    • Update to 3:4.2.11-1ubuntu1.18
    • Update to 3:5.2.17-1
    • Update to 3:5.2.9-0ubuntu4.3
    • Update to 5.2.17
    • Update to 6.0.8
    Published Updated
  18. CVE-2026-12075

    High · CVSS 8.6Fix available

    Natural Language Toolkit (NLTK): DNS-rebinding SSRF filter bypass in nltk.pathsec.urlopen (nltk.download / nltk.data.load) defeats ENFORCE mode

    ### Summary `nltk.pathsec` provides an SSRF filter that NLTK documents as a security control, blocking loopback, private, link-local, and multicast ranges (including obfuscated forms) and recommending strict `ENFORCE` mode for security-sensitive environments. The filter is bypassable by DNS rebinding: `validate_network_url()` resolves the hostname and checks the resulting IP, but the actual HTTP connection re-resolves the hostname independently at connect time and connects to that second result. The validated IP is never the one connected to. An attacker controlling DNS for a hostname (a TTL-0 rebinding record) returns a public IP for the val

    • Update to 3.10.0
    Published Updated
  19. CVE-2026-69249

    High · CVSS 8.7EPSS 0.26%Fix available

    python-cryptography: Duplicate self-signed intermediates can cause exponential path-building

    python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 42.0.0 through 48.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource ex

    • Update to 46.0.5-1ubuntu2.2
    • Update to 49.0.0
    • Update to 49.0.0-1
    Published Updated
  20. CVE-2026-69248

    Medium · CVSS 6.9EPSS 0.24%Fix available

    python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees

    cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 45.0.0 through 48.0.0, if an intermediate constrained CA permits the DNS name foo.example.com, and the leaf certificate has a wildcard in its DNS SAN of *.example.com, python-cryptography's verifier accepts which allows escaping outside of the permitted names. The core issue is in DNSConstraint::matches, where a wildcard pattern was treated as matching a more-specific permitted constraint even though *.example.com can expand to sibling names such as bar.example.com outside foo.example.com. This allows acceptance of an invalid ce

    • Update to 46.0.5-1ubuntu2.2
    • Update to 49.0.0
    • Update to 49.0.0-1
    Published Updated

Check your server

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

Check your server →