← Scan another repo

github.com/TheAlgorithms/Python

@ f5988cc09713

Submitted 8/4/2026, 10:25:51 AM · Status: ok

Risk grade
F
100 / 100
Findings
139
0 critical30 high106 medium2 low1 info0 on CISA KEV0ATT&CK
Showing 139 of 139 findings

Findings

  • Decompression-bomb safeguards bypassed when following HTTP redirects (streaming API)
    grypeCVE-2026-21441EPSS 2.7%
  • FITS GZIP decompression bomb in Pillow
    grypeCVE-2026-40192EPSS 0.7%
  • Keras Directory Traversal Vulnerability
    grypeCVE-2025-12060EPSS 0.6%
  • Keras has a Local File Disclosure via HDF5 External Storage During Keras Weight Loading
    grypeCVE-2026-1669EPSS 0.3%
  • Keras has an untrusted deserialization vulnerability
    grypeCVE-2026-1462EPSS 0.4%
  • Keras is vulnerable to Deserialization of Untrusted Data
    grypeCVE-2025-9906EPSS 0.2%
  • Keras vulnerable to CVE-2025-1550 bypass via reuse of internal functionality
    grypeCVE-2025-8747EPSS 0.1%
  • Keras vulnerable to DoS via Malicious .keras Model (HDF5 Shape Bomb Causes Petabyte Allocation in KerasFileEditor)
    grypeCVE-2026-0897EPSS 0.3%
  • lxml: Default configuration of iterparse() and ETCompatXMLParser() allows XXE to local files
    grypeCVE-2026-41066EPSS 0.3%
  • Pillow `BdfFontFile`: `Image.new()` called without `_decompression_bomb_check()` — bomb protection bypass via font loading
    grypeCVE-2026-55379EPSS 0.4%
  • Pillow `GdImageFile._open()`: image dimensions accepted without `_decompression_bomb_check()`
    grypeCVE-2026-55380EPSS 0.4%
  • Pillow `PcfFontFile._load_bitmaps()`: `Image.frombytes()` called without `_decompression_bomb_check()` — bomb protection bypass via PCF font loading
    grypeCVE-2026-54059EPSS 0.4%
  • Pillow affected by out-of-bounds write when loading PSD images
    grypeCVE-2026-25990EPSS 0.4%
  • Pillow has an OOB Write with Invalid PSD Tile Extents (Integer Overflow)
    grypeCVE-2026-42311EPSS 0.1%
  • Pillow JPEG2000 tiled decode retains a growing scratch buffer and can be used for denial of service
    grypeCVE-2026-59204EPSS 0.4%
  • Pillow vulnerability can cause write buffer overflow on BCn encoding
    grypeCVE-2025-48379EPSS 0.3%
  • Pillow: `FontFile.compile()`: `Image.new()` called without `_decompression_bomb_check()`
    grypeCVE-2026-54060EPSS 0.4%
  • Pillow: Controlled heap out-of-bounds write in Pillow `ImageCmsTransform.apply()` via output mode mismatch
    grypeCVE-2026-59205EPSS 0.4%
  • Pillow: Decompression Bomb DoS via PdfParser.PdfStream.decode()
    grypeCVE-2026-59200EPSS 0.4%
  • Pillow: Heap out-of-bounds write `Image.paste()` / `Image.crop()` via signed coordinate overflow
    grypeCVE-2026-59199EPSS 0.4%
  • Pillow: Heap out-of-bounds write in `ImageFilter.RankFilter` via integer overflow in `ImagingExpand`
    grypeCVE-2026-59197EPSS 0.4%
  • Pillow: Out-of-bounds read via attacker-controlled row stride on Pillow's mmap path (McIdas AREA files)
    grypeCVE-2026-54058EPSS 0.4%
  • Soup Sieve has Memory Exhaustion via Large Comma-Separated Selector Lists
    grypeCVE-2026-49476EPSS 0.4%
  • Soup Sieve: Regular Expression Denial of Service (ReDoS) via Selector Parser
    grypeCVE-2026-49477EPSS 0.4%
  • The Keras `Model.load_model` method **silently** ignores `safe_mode=True` and allows arbitrary code execution when a `.h5`/`.hdf5` file is loaded.
    grypeCVE-2025-9905EPSS 0.2%
  • urllib3 allows an unbounded number of links in the decompression chain
    grypeCVE-2025-66418EPSS 0.7%
  • urllib3 streaming API improperly handles highly compressed data
    grypeCVE-2025-66471EPSS 0.7%
  • urllib3: Sensitive headers forwarded across origins in proxied low-level redirects
    grypeCVE-2026-44431EPSS 0.3%
  • pickle.load/loads on non-constant data executes arbitrary code on deserialize. Use JSON or a signed/whitelisted format for untrusted input. (Apache-2.0.)
    pickle.load/loads on non-constant data executes arbitrary code on deserialize. Use JSON or a signed/whitelisted format for untrusted input. (Apache-2.0.)
    semgrepneural_network/convolution_neural_network.py:82
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivy.devcontainer/Dockerfile:0

This report is public.