gitsafehub
github.com/lllyasviel/fooocus ↗

lllyasviel/fooocus

scanned 2026-07-15 · git ae05379
1 of 6 checks flagged a security issue
🔴 Needs attention
6 checks ran. Start with known oss vulnerabilities below.

Informational scan, not a security audit. How this is computed.

Leaked secrets✓Vulnerable dependencies✓Known OSS vulnerabilities124Risky code patterns✓Malicious dependencies✓Project health8

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ none found ✓

Packages you depend on that have known security holes (CVEs).

Nothing found by this check. ✓

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 124 found · 12 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious PYSEC-2024-259 In PyTorch <=2.4.1, the RemoteModule has Deserialization RCE. NOTE: this is disputed by multiple parties because this is intended behavior in PyTorch distributed computing.
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2024-48063). Fix: Update that package to its patched version.
  • Serious PYSEC-2025-41 PyTorch is a Python package that provides tensor computation with strong GPU acceleration and deep neural networks built on a tape-based autograd system. In version 2.5.1 and prior, a Remote Command E
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-32434). Fix: Update that package to its patched version.
  • Serious PYSEC-2026-457 Arbitrary Code Execution in Pillow
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2023-50447). Fix: Update that package to its patched version.
  • Serious PYSEC-2023-255 Command Injection in GitHub repository gradio-app/gradio prior to main.
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_versions.txt
    A package you depend on has a known security hole (CVE-2023-6572). Fix: Update that package to its patched version.
  • Serious PYSEC-2024-215 Gradio is an open-source Python package designed for quick prototyping. This vulnerability relates to **Server-Side Request Forgery (SSRF)** in the `/queue/join` endpoint. Gradio’s `async_save_url_to_
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_versions.txt
    A package you depend on has a known security hole (CVE-2024-47167). Fix: Update that package to its patched version.
  • Serious PYSEC-2024-219 Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves **insecure communication** between the FRP (Fast Reverse Proxy) client and server when Gradio's `sha
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_versions.txt
    A package you depend on has a known security hole (CVE-2024-47871). Fix: Update that package to its patched version.
  • Serious PYSEC-2024-274 Gradio v4.36.1 was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py. This vulnerability is triggered via a crafted input. NOTE: the supplier disputes th
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_versions.txt
    A package you depend on has a known security hole (CVE-2024-39236). Fix: Update that package to its patched version.
  • Serious PYSEC-2024-321 A command injection vulnerability exists in the gradio-app/gradio repository, specifically within the 'test-functional.yml' workflow. The vulnerability arises due to improper neutralization of special
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_versions.txt
    A package you depend on has a known security hole (CVE-2024-4253). Fix: Update that package to its patched version.
  • Serious PYSEC-2025-118 Gradio is an open-source Python package that allows quick building of demos and web application for machine learning models, API, or any arbitrary Python function. Gradio's Access Control List (ACL) f
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_versions.txt
    A package you depend on has a known security hole (CVE-2025-23042). Fix: Update that package to its patched version.
  • Serious PYSEC-2026-345 Gradio allows users to access arbitrary files
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_versions.txt
    A package you depend on has a known security hole (CVE-2024-1728). Fix: Update that package to its patched version.
  • Serious PYSEC-2026-507 PyTorch Lightning path traversal vulnerability
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_versions.txt
    A package you depend on has a known security hole (CVE-2024-8019). Fix: Update that package to its patched version.
  • Serious PYSEC-2026-2290 A vulnerability in the LightGlue model loading path of huggingface/transformers version 5.2.0 allows an attacker-controlled model repository to execute arbitrary code during model initialization. The
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_versions.txt
    A package you depend on has a known security hole (CVE-2026-5241). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2024-251 Pytorch before version v2.2.0 was discovered to contain a use-after-free vulnerability in torch/csrc/jit/mobile/interpreter.cpp.
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2024-31583). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2024-252 PyTorch before v2.2.0 was discovered to contain a heap buffer overflow vulnerability in the component /runtime/vararg_functions.cpp. This vulnerability allows attackers to cause a Denial of Service (D
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2024-31580). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-191 A vulnerability, which was classified as problematic, has been found in PyTorch 2.6.0+cu124. Affected by this issue is the function torch.mkldnn_max_pool2d. The manipulation leads to denial of service
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-2953). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-198 In PyTorch through 2.6.0, when eager is used, nn.PairwiseDistance(p=2) produces incorrect results.
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-46148). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-203 An issue in the component torch.linalg.lu of pytorch v2.8.0 allows attackers to cause a Denial of Service (DoS) when performing a slice operation.
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-55551). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-204 pytorch v2.8.0 was discovered to display unexpected behavior when the components torch.rot90 and torch.randn_like are used together.
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-55552). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-205 A syntax error in the component proxy_tensor.py of pytorch v2.7.0 allows attackers to cause a Denial of Service (DoS).
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-55553). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-206 pytorch v2.8.0 was discovered to contain an integer overflow in the component torch.nan_to_num-.long().
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-55554). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-207 A Name Error occurs in pytorch v2.7.0 when a PyTorch model consists of torch.cummin and is compiled by Inductor, leading to a Denial of Service (DoS).
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-55557). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-208 A buffer overflow occurs in pytorch v2.7.0 when a PyTorch model consists of torch.nn.Conv2d, torch.nn.functional.hardshrink, and torch.Tensor.view-torch.mv() and is compiled by Inductor, leading to a
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-55558). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-209 An issue in pytorch v2.7.0 can lead to a Denial of Service (DoS) when a PyTorch model consists of torch.Tensor.to_sparse() and torch.Tensor.to_dense() and is compiled by Inductor.
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-55560). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-139 A vulnerability was identified in PyTorch 2.10.0. The affected element is an unknown function of the component pt2 Loading Handler. The manipulation leads to deserialization. The attack can only be pe
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2026-4538). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1970 PyTorch Improper Resource Shutdown or Release vulnerability
    /workdirs/scan-f122c055-e008-4103-a7ce-c4539a286a14/requirements_docker.txt
    A package you depend on has a known security hole (CVE-2025-3730). Fix: Update that package to its patched version.
… 99 more not shown

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ none found ✓

Packages that look intentionally malicious: typosquats, sneaky install scripts.

Nothing found by this check. ✓

via Guarddog v2.10.0 · Apache-2.0

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ 8 notes

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

  • Minor scorecard-overall OpenSSF Scorecard overall: 5.2/10
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-CI-Tests CI-Tests scored 0: 0 out of 19 merged PRs checked by a CI test -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-CII-Best-Practices CII-Best-Practices scored 0: no effort to earn an OpenSSF best practices badge detected
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Fuzzing Fuzzing scored 0: project is not fuzzed
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Maintained Maintained scored 0: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Pinned-Dependencies Pinned-Dependencies scored 0: dependency not pinned by hash detected -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-SAST SAST scored 0: SAST tool is not run on all commits -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Security-Policy Security-Policy scored 0: security policy file not detected
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.

via OpenSSF Scorecard v5.5.0 · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.