p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Schwachstellen im Stack Python · Seite 67

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für Python: 360. Davon im KEV-Katalog: 1.

Sicherheitslücken filtern
Python

Sicherheitslücken: 7131

  1. CVE-2026-54059

    Hoch · CVSS 7.5EPSS 0,41%Korrektur verfügbar

    Pillow: PcfFontFile._load_bitmaps()`: `Image.frombytes()` called without `_decompression_bomb_check()` — bomb protection bypass via PCF font loading

    Pillow is a Python imaging library. Prior to 12.3.0, PIL/PcfFontFile.py _load_bitmaps() read glyph dimensions from the PCF METRICS section and passed them directly to Image.frombytes() without calling Image._decompression_bomb_check(), allowing crafted PCF font data to cause excessive memory allocation. This issue is fixed in version 12.3.0.

    • Auf 12.3.0 aktualisieren
    • Auf 12.3.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-55798

    Mittel · CVSS 4.5EPSS 0,18%Korrektur verfügbar

    Pillow: WindowsViewer.get_command() OS command injection via unescaped shell path

    Pillow is a Python imaging library. Prior to 12.3.0, WindowsViewer.get_command() constructed a cmd.exe shell command by directly embedding a file path into an f-string without escaping and passed the result to subprocess.Popen(..., shell=True), allowing shell metacharacters in the file path to inject arbitrary cmd.exe commands. This issue is fixed in version 12.3.0.

    • Auf 12.3.0 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-59152

    Mittel · CVSS 5EPSS 0,2%Korrektur verfügbar

    Arbitrary server-side file read in LangSmith SDK TracingMiddleware

    LangSmith Client SDKs provide SDK's for interacting with the LangSmith platform. Prior to 0.8.18, an attacker who can send an HTTP request to a server running the LangSmith SDK's TracingMiddleware can cause that server to read an arbitrary file from its local filesystem and upload the contents to LangSmith as a trace attachment. Depending on how the distributed trace system is deployed, triggering a read may not require authentication. Retrieving the contents requires read access to the LangSmith workspace the traces are sent to. The net effect is a trust-boundary crossing: a party with workspace trace-read access (for example a low-privilege

    • Auf 0.8.18 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-58203

    Mittel · CVSS 5.3EPSS 0,18%Korrektur verfügbar

    NestedSecretsSettingsSource follows symlinks outside secrets_dir, enabling local file read and bypassing secrets_dir_max_size

    pydantic-settings provides settings management using Pydantic. From 2.12.0 until 2.14.2, NestedSecretsSettingsSource reads secret values from files in a configured secrets_dir. When secrets_nested_subdir=True, a directory entry inside secrets_dir that is a symbolic link pointing outside secrets_dir is followed, so files outside the configured directory are read into settings values. The same code path bypasses the documented secrets_dir_max_size protection. An attacker or lower-privileged component able to influence entries in the configured secrets directory (for example, a writable or shared secrets mount) can turn this into an unintended l

    • Auf 2.14.2 aktualisieren
    • Auf 2.14.2-1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-49297

    Hoch · CVSS 8.1EPSS 0,99%Korrektur verfügbar

    Apache Airflow Google provider: Path traversal via GCS object names → local/SFTP filesystem (GCSToSFTPOperator + GCSTimeSpanFileTransformOperator)

    Apache Airflow's Google provider operators `GCSToSFTPOperator` and `GCSTimeSpanFileTransformOperator` joined GCS object names returned by the bucket listing API directly to a destination filesystem path without normalisation or containment check. A user with write access to the source GCS bucket (typically a different trust principal than the DAG author — partner uploads, ingest-only service accounts, public-data buckets) could create an object whose name contains `..` segments and cause the DAG run to write the downloaded blob outside the configured destination (the SFTP `destination_path` for `GCSToSFTPOperator`; the worker-local temp direc

    • Auf 22.2.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2026-24013

    Kritisch · CVSS 9.1EPSS 0,64%Korrektur verfügbar

    Apache IoTDB: Authentication Bypass via Forged SessionID in Thrift RPC

    Authentication Bypass by Spoofing vulnerability in Apache IoTDB. Certain Thrift RPC query handlers lack strict validation of the sessionId parameter. An attacker can construct requests with a forged sessionId and, without performing openSession authentication, receive valid query results. This allows authentication bypass and unauthorized reading of time-series data. This issue affects Apache IoTDB: from 1.3.3 before 2.0.8. Users are recommended to upgrade to version 2.0.8, which fixes the issue.

    • Auf 2.0.8 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2026-24012

    Hoch · CVSS 7.5EPSS 0,74%Korrektur verfügbar

    Apache IoTDB: Denial of Service via Resource Exhaustion in Aggregation Query

    Uncontrolled Resource Consumption vulnerability in Apache IoTDB.  Some interface fails to impose reasonable limits on the time span and aggregation interval of the query. An attacker can construct a request with extreme parameters (e.g., a very large time range combined with a minimal interval). This forces the DataNode to build an enormous result set in memory, which exhausts the Java heap and causes the DataNode process to crash. This issue affects Apache IoTDB: from 1.3.3 before 2.0.8. Users are recommended to upgrade to version 2.0.8, which fixes the issue.

    • Auf 2.0.8 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2026-24014

    Kritisch · CVSS 9.8EPSS 0,69%Korrektur verfügbar

    Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write

    Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to build a file path without sufficient validation. If the internal DataNode RPC port is exposed to an untrusted network, an attacker may use path traversal sequences in the JAR name to write files outside the intended Trigger installation directory. This could allow arbitrary file write with the permissions of the IoTDB process. This issue affects Apache IoTDB: from 1.3.3 before 2.0.8. Users are recommended to upgrade to version 2.0.8, which fixes the issue.

    • Auf 2.0.8 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2026-14535

    Hoch · CVSS 8.8EPSS 0,56%Korrektur verfügbar

    Fickling MLAllowlist analysis pass rendered inoperative by shared mutable state in AnalysisContext.shorten_code()

    In Trail of Bits fickling versions up to and including 0.1.11, the UnsafeImportsML analysis pass unconditionally calls AnalysisContext.shorten_code(node) on every import node it inspects, regardless of whether the import is flagged as unsafe. This call registers the shortened code representation in the shared AnalysisContext.reported_shortened_code set. When the MLAllowlist analysis pass subsequently runs, it calls the same shorten_code() method, receives already_reported=True for every import, and executes a continue statement that skips its allowlist check entirely. This renders MLAllowlist dead code for all imports — it never evaluates whe

    • Auf 0.1.12 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2026-14534

    Hoch · CVSS 8.8EPSS 0,59%Korrektur verfügbar

    Fickling check_safety() bypass via unlisted standard library modules (_posixsubprocess, site, atexit)

    Trail of Bits fickling versions up to and including 0.1.10 do not include the Python standard library modules _posixsubprocess, site, and atexit in the UNSAFE_IMPORTS denylist (fickle.py). Because these modules are absent from the denylist, fickling's check_safety() function returns LIKELY_SAFE with zero findings for pickle payloads that invoke dangerous functions including _posixsubprocess.fork_exec (C-level process spawner capable of executing arbitrary binaries), site.execsitecustomize (executes arbitrary site customization code), and atexit._run_exitfuncs (triggers all registered exit handler callbacks). The fickling.load() API chains che

    • Auf 0.1.11 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2025-71375

    Hoch · CVSS 7.6EPSS 0,46%Korrektur verfügbar

    picklescan - Undetected Remote Code Execution via _operator.methodcaller

    picklescan before 0.0.34 fails to detect the _operator.methodcaller built-in function when scanning pickle files for malicious code. Attackers can craft malicious pickle payloads using _operator.methodcaller that evade detection and execute arbitrary code when loaded by pickle.load().

    • Auf 0.0.34 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2025-71373

    Hoch · CVSS 7.6EPSS 0,56%Korrektur verfügbar

    picklescan - Remote Code Execution via operator.methodcaller Detection Bypass

    picklescan before 0.0.33 fails to detect operator.methodcaller function calls in pickle files, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle payloads using operator.methodcaller that execute arbitrary code when loaded, compromising systems relying on picklescan for validation.

    • Auf 0.0.33 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2025-71372

    Hoch · CVSS 7.6EPSS 0,48%Korrektur verfügbar

    Picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran.getlincoef Gadget

    Picklescan before 0.0.33 fails to detect the numpy.f2py.crackfortran.getlincoef gadget in pickle __reduce__ methods, allowing arbitrary code execution. Attackers can craft malicious pickle files that execute arbitrary Python code when loaded, bypassing Picklescan's safety checks and enabling supply-chain poisoning of shared model files.

    • Auf 0.0.33 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2025-71369

    Hoch · CVSS 7.6EPSS 0,56%Korrektur verfügbar

    picklescan - Unsafe Deserialization via torch.utils.data.datapipes.utils.decoder.basichandlers

    picklescan before 0.0.28 fails to detect malicious pickle files that use torch.utils.data.datapipes.utils.decoder.basichandlers in reduce methods, allowing attackers to bypass safety checks. Remote attackers can embed undetected malicious code in pickle files that executes during deserialization, enabling remote code execution.

    • Auf 0.0.28 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2025-71367

    Hoch · CVSS 7.6EPSS 0,56%Korrektur verfügbar

    picklescan - Remote Code Execution via _operator.attrgetter Detection Bypass

    picklescan before 0.0.34 fails to detect _operator.attrgetter function calls in pickle payloads, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle files using _operator.attrgetter in reduce methods to execute arbitrary code when pickle.load() processes the file.

    • Auf 0.0.34 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2025-71366

    Hoch · CVSS 7.6EPSS 0,56%Korrektur verfügbar

    picklescan - Arbitrary Code Execution via torch.utils.bottleneck.__main__.run_cprofile

    picklescan before 0.0.28 fails to detect malicious torch.utils.bottleneck.__main__.run_cprofile function calls in pickle files, allowing attackers to bypass safety checks. Remote attackers can embed undetected code in pickle files to achieve arbitrary code execution when victims load the files.

    • Auf 0.0.28 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2025-71364

    Hoch · CVSS 7.6EPSS 0,7%Korrektur verfügbar

    picklescan - Arbitrary Code Execution via Undetected asyncio.unix_events._UnixSubprocessTransport._start

    picklescan before 0.0.30 fails to detect the asyncio.unix_events._UnixSubprocessTransport._start function in pickle reduce methods, allowing remote code execution. Attackers can craft malicious pickle files embedding this built-in function that evade detection but execute arbitrary commands when loaded.

    • Auf 0.0.30 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2025-71362

    Hoch · CVSS 7.6EPSS 0,43%Korrektur verfügbar

    picklescan - Arbitrary Code Execution via Unsafe Deserialization in numpy.f2py.crackfortran

    picklescan before 0.0.33 fails to detect unsafe deserialization when numpy.f2py.crackfortran functions call eval on arbitrary strings. Attackers can embed malicious code in pickle files that executes when loaded from untrusted sources.

    • Auf 0.0.33 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2025-71360

    Hoch · CVSS 7.6EPSS 0,38%Korrektur verfügbar

    picklescan - Remote Code Execution via Undetected idlelib.calltip.get_entity

    picklescan before 0.0.29 fails to detect malicious pickle files using idlelib.calltip.get_entity function in reduce methods. Attackers can embed undetected code in pickle files that executes remote commands when loaded by victims.

    • Auf 0.0.29 aktualisieren
    Veröffentlicht Aktualisiert
  20. CVE-2025-71359

    Hoch · CVSS 7.6EPSS 0,61%Korrektur verfügbar

    picklescan - Unsafe Deserialization via lib2to3.pgen2.grammar.Grammar.loads

    picklescan before 0.0.29 fails to detect malicious pickle payloads that utilize lib2to3.pgen2.grammar.Grammar.loads in the reduce method, allowing remote code execution. Attackers can craft pickle files embedding dangerous code that evades picklescan detection and executes during pickle.load() deserialization.

    • Auf 0.0.29 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →