p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de la pile Python · Page n° 76

Vulnérabilités publiées pour Python au cours des 30 derniers jours : 354. Présentes dans le catalogue KEV : 1.

Filtrer les vulnérabilités
Python

Vulnérabilités : 7131

  1. CVE-2026-55443

    Moyenne · CVSS 5.1EPSS 0,21%Correctif disponible

    LangChain: Path traversal and sandbox escape in LangChain file-search middleware and loaders

    LangChain is a framework for building agents and LLM-powered applications. Prior to 1.3.9, several LangChain components that resolve filesystem paths or expand search patterns do not consistently confine the resolved path to the intended root directory. Affected behaviors include: a file-search agent middleware that validates a starting directory but not the search pattern or the resolved target of matched files, so glob patterns and symlinks can reach files outside the configured root; prompt- and chain/agent-configuration loaders that accept path fields and resolve them without confining the result to a trusted base or rejecting symlink tar

    • Mettez à jour vers 1.3.9
    • Mettez à jour vers 1.4.6
    Publication Mise à jour
  2. CVE-2026-53540

    Faible · CVSS 3.7EPSS 0,34%Correctif disponible

    Python-Multipart: Negative Content-Length in parse_form buffers the entire body in memory

    Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.31, parse_form() did not validate the Content-Length header before using it to bound its chunked read of the request body. A negative Content-Length turned the bounded read into a read-until-EOF, so the entire body was loaded into memory in a single read instead of in fixed-size chunks. This vulnerability is fixed in 0.0.31.

    • Mettez à jour vers 0.0.31
    • Mettez à jour vers 0.0.32-1
    Publication Mise à jour
  3. CVE-2026-53537

    Faible · CVSS 3.7EPSS 0,29%Correctif disponible

    Python-Multipart: Content-Disposition parameter smuggling via RFC 2231/5987 extended parameters

    Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, parse_options_header parsed Content-Disposition (and Content-Type) headers with email.message.Message, which transparently applies RFC 2231/5987 decoding. The extended parameter syntax (filename*=charset'lang'value, name*=..., and the filename*0/filename*1 continuation form) is decoded and surfaced under the bare filename/name key, and overrides the plain parameter when both are present. RFC 7578 §4.2 explicitly forbids the filename* form in multipart/form-data. Components that follow RFC 7578, or that do not implement RFC 2231/5987 decoding for multipart/form-data

    • Mettez à jour vers 0.0.30
    • Mettez à jour vers 0.0.32-1
    Publication Mise à jour
  4. CVE-2026-53538

    Faible · CVSS 3.7EPSS 0,26%Correctif disponible

    Python-Multipart: Semicolon treated as querystring field separator enables parameter smuggling

    Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, QuerystringParser treated ; as a field separator in application/x-www-form-urlencoded bodies, in addition to &. The WHATWG URL standard, modern browsers, and Python's urllib.parse (since the CVE-2021-23336 fix) treat only & as a separator. This creates a parser differential: the same bytes are tokenized into different fields than a WHATWG compliant intermediary would produce, allowing an attacker to smuggle extra form fields past an upstream body inspecting component. This vulnerability is fixed in 0.0.30.

    • Mettez à jour vers 0.0.30
    • Mettez à jour vers 0.0.32-1
    Publication Mise à jour
  5. CVE-2026-53539

    Élevée · CVSS 7.5EPSS 0,46%Correctif disponible

    Python-Multipart: Quadratic-time querystring parsing with semicolon separators causes CPU denial of service

    Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, when parsing application/x-www-form-urlencoded bodies, QuerystringParser located the field separator with a two step lookup: it first scanned the entire remaining buffer for &, and only when no & existed anywhere ahead did it fall back to scanning for ;. For a body that uses ; as the separator and contains no &, every field iteration performed a full failed & scan over the entire remaining buffer before locating the nearby ;. With N semicolon separated fields in a chunk of size B, this yields O(B^2) byte comparisons per chunk. An attacker can submit a small crafted

    • Mettez à jour vers 0.0.30
    • Mettez à jour vers 0.0.32-1
    Publication Mise à jour
  6. CVE-2026-54283

    Élevée · CVSS 7.5EPSS 0,48%Correctif disponible

    Starlette: request.form() limits silently ignored for application/x-www-form-urlencoded enable DoS

    Starlette is a lightweight ASGI framework/toolkit. From 0.4.1 until 1.3.1, request.form() accepts max_fields and max_part_size to bound resource consumption while parsing form data. These limits are enforced for multipart/form-data, but silently ignored for application/x-www-form-urlencoded. An unauthenticated attacker can therefore send a urlencoded body with an arbitrarily large number of fields or an arbitrarily large field, even when the application configured limits it believed would apply. This vulnerability is fixed in 1.3.1.

    • Mettez à jour vers 0.26.1-1+deb12u2
    • Mettez à jour vers 0.46.1-3+deb13u3
    • Mettez à jour vers 1.3.1
    • Mettez à jour vers 1.3.1-1
    Publication Mise à jour
  7. CVE-2026-54282

    Faible · CVSS 3.7EPSS 0,27%Correctif disponible

    Starlette: Unvalidated request path concatenated into authority poisons request.url.hostname

    Starlette is a lightweight ASGI framework/toolkit. Prior to 1.3.0, the HTTP request path is not validated before being used to reconstruct request.url. Because request.url is rebuilt by concatenating {scheme}://{host}{path} and re-parsing the result, a path that does not begin with / (for example @google.com) moves the authority boundary during re-parsing, so request.url.hostname and request.url.netloc become attacker-controlled. Code that reads request.url.hostname (rather than the Host header or scope) can therefore be misled into trusting an attacker-supplied host. This vulnerability is fixed in 1.3.0.

    • Mettez à jour vers 0.26.1-1+deb12u2
    • Mettez à jour vers 0.46.1-3+deb13u3
    • Mettez à jour vers 1.3.0
    • Mettez à jour vers 1.3.1-1
    Publication Mise à jour
  8. CVE-2026-54273

    Moyenne · CVSS 6.6EPSS 0,49%Correctif disponible

    AIOHTTP: HTTP/1 Pipelined Requests Queue Without Limit

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, no limit was present on the number of pipelined requests that could be queued. An attacker may be able to use pipelined requests to use excessive amounts of memory, potentially leading to DoS. This vulnerability is fixed in 3.14.1.

    • Mettez à jour vers 3.14.1
    • Mettez à jour vers 3.14.1-1
    Publication Mise à jour
  9. CVE-2026-54280

    Faible · CVSS 1.7EPSS 0,46%Correctif disponible

    AIOHTTP: Payload Response Resources Are Not Closed After Mid-Body Disconnect

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, payload resources are not closed correctly when a client disconnects in the middle of a write. If a payload is using an open file or similar limited resource, then an attacker may be able to cause resource starvation temporarily until garbage collection or similar closes the file. This vulnerability is fixed in 3.14.1.

    • Mettez à jour vers 3.14.1
    • Mettez à jour vers 3.14.1-1
    • Mettez à jour vers 3.8.4-1+deb12u2
    Publication Mise à jour
  10. CVE-2026-54278

    Moyenne · CVSS 6.6EPSS 0,49%Correctif disponible

    AIOHTTP: Unread Compressed Request Bodies Bypass client_max_size During Cleanup

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, during cleanup it is possible for a compressed request body to be decompressed into memory in one chunk. An attacker may be able to send a compressed payload in specific situations that could be decompressed into memory, potentially leading to DoS (a zip bomb edge case). This vulnerability is fixed in 3.14.1.

    • Mettez à jour vers 3.14.1
    • Mettez à jour vers 3.14.1-1
    Publication Mise à jour
  11. CVE-2026-54277

    Moyenne · CVSS 6.6EPSS 0,56%Correctif disponible

    AIOHTTP: C HTTP Parser Bypasses max_line_size for Fragmented Lines

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, it is possible to bypass the max_line_size check in parts of an HTTP request in the C parser. If using the optimised C parser (the default in pre-built wheels), then an attacker may be able to send oversized lines through the HTTP parser and use an excessive amount of memory, potentially leading to DoS. This vulnerability is fixed in 3.14.1.

    • Mettez à jour vers 3.14.1
    • Mettez à jour vers 3.14.1-1
    • Mettez à jour vers 3.8.4-1+deb12u2
    Publication Mise à jour
  12. CVE-2026-54276

    Moyenne · CVSS 6.3EPSS 0,31%Correctif disponible

    AIOHTTP: DigestAuthMiddleware Applies Credentials to Cross-Origin Redirect Challenges

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, DigestAuthMiddleware can send an authentication response after following a cross-origin redirect. This likely requires an open redirect vulnerability or similar on the target domain for an attacker to be able to execute. Further, the attacker is only receiving the digest, so should only be able to extract the user's credentials if the cryptography is weak or there is some kind of password reuse. This vulnerability is fixed in 3.14.1.

    • Mettez à jour vers 3.14.1
    • Mettez à jour vers 3.14.1-1
    Publication Mise à jour
  13. CVE-2026-54275

    Faible · CVSS 2.7EPSS 0,47%Correctif disponible

    AIOHTTP: TLS Server Hostname Override Is Ignored When Reusing HTTPS Connections

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed when an existing connection is reused. If an application makes multiple requests to the same domain, but with different per-request server_hostname parameters, then the later calls may succeed by reusing the existing connection when they should have been rejected due to the TLS SNI check. This vulnerability is fixed in 3.14.1.

    • Mettez à jour vers 3.14.1
    • Mettez à jour vers 3.14.1-1
    Publication Mise à jour
  14. CVE-2026-54274

    Moyenne · CVSS 6.6EPSS 0,54%Correctif disponible

    AIOHTTP: Incomplete websocket frame payloads bypass memory limits

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, if an attacker sends large incomplete websocket frame payloads, it may be possible to bypass the usual size limits on memory use. This vulnerability is fixed in 3.14.1.

    • Mettez à jour vers 3.14.1
    • Mettez à jour vers 3.14.1-1
    • Mettez à jour vers 3.8.4-1+deb12u2
    Publication Mise à jour
  15. CVE-2026-54279

    Faible · CVSS 1.3EPSS 0,49%Correctif disponible

    AIOHTTP: Host-Only Cookies Become Domain Cookies After CookieJar Persistence

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, host-only cookies that are saved with CookieJar.save() and then restored later with CookieJar.load() lose their host-only status. This vulnerability is fixed in 3.14.1.

    • Mettez à jour vers 3.14.1
    • Mettez à jour vers 3.14.1-1
    • Mettez à jour vers 3.8.4-1+deb12u2
    Publication Mise à jour
  16. CVE-2026-50269

    Faible · CVSS 2.7EPSS 0,53%Correctif disponible

    AIOHTTP: CRLF injection in multipart headers

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.0, attacker-controlled input included into multipart/payload headers can be used to modify a request to inject additional headers or similar. In the unlikely situation that an application is passing user-controlled strings into MultipartWriter.append(headers=...) or Payload.headers, then an attacker may be able to modify the request to inject headers or change the contents of the request. This vulnerability is fixed in 3.14.0.

    • Mettez à jour vers 3.14.0
    • Mettez à jour vers 3.14.0-1
    • Mettez à jour vers 3.8.4-1+deb12u2
    Publication Mise à jour
  17. CVE-2026-12479

    Moyenne · CVSS 6.1EPSS 0,36%Correctif disponible

    Path Traversal in keras-team/keras

    A path traversal vulnerability exists in keras-team/keras version 3.14.0, specifically in the `DiskIOStore.make` method within the Keras 3 model saving and loading library. This vulnerability arises from the improper handling of user-provided layer names, which are used to construct directory paths without sanitizing for parent directory components (`..`). While forward slashes (`/`) are restricted in layer names, directory traversal sequences are not. This allows an attacker to craft a malicious Keras model that, when saved or loaded, can escape the intended temporary working directory and perform unauthorized file system operations, such as

    • Mettez à jour vers 3.12.3
    • Mettez à jour vers 3.15.0
    Publication Mise à jour
  18. CVE-2026-56104

    Élevée · CVSS 8.8EPSS 0,42%Correctif disponible

    Chainlit < 2.10.1 Session Hijacking via WebSocket Session Restoration

    Chainlit before 2.10.1 contains a session hijacking vulnerability that allows unauthenticated attackers to restore and inherit authenticated user sessions by presenting a valid sessionId during WebSocket session restoration without ownership verification. Attackers can exploit the restore_existing_session path to assume a victim's permissions and roles, enabling unauthorized invocation of tools and access to data restricted to the authenticated victim.

    • Mettez à jour vers 2.10.1
    Publication Mise à jour
  19. CVE-2026-10561

    Critique · CVSS 10EPSS 0,82%Code d’exploitation publicCorrectif disponible

    Unauthenticated Remote Code Execution in Langflow OSS PythonREPLComponent via Builtins Injection

    IBM Langflow OSS 1.0.0 through 1.9.3 has an vulnerability due to an improper isolation of Python execution combined with an authentication bypass that allows an unauthenticated attacker to execute arbitrary code on the host system, resulting in complete compromise

    • Mettez à jour vers 1.10.1
    Publication Mise à jour
  20. CVE-2025-66336

    Élevée · CVSS 8.1EPSS 0,56%Correctif disponible

    Apache Doris MCP Server: SQL injection leading the authentication bypass

    Apache Doris MCP Server contains a SQL injection vulnerability in a metadata query path. A user-controlled database name is directly interpolated into a SQL query, and the query is executed without passing the caller's authorization context. This may allow an authenticated attacker, or an anonymous attacker if authentication is disabled, to bypass SQL security validation and access metadata outside the intended database scope. Affected users are recommended to upgrade to Doris version 0.6.1 or later, which fixes the issue.

    • Mettez à jour vers 0.6.1
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →