gitsafehub
github.com/cvlab-kaist/trackcraft3r ↗

cvlab-kaist/trackcraft3r

scanned 2026-07-23 · git 21e8fca
1 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets✓Vulnerable dependencies✓Known OSS vulnerabilities23Risky 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ⓘ 23 found · 2 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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2025-32434). 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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.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-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2025-3730). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2286 PyTorch is a Python package that provides tensor computation. Prior to version 2.10.0, a vulnerability in PyTorch's `weights_only` unpickler allows an attacker to craft a malicious checkpoint file (`.
    /workdirs/scan-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2026-24747). Fix: Update that package to its patched version.
  • Worth fixing GHSA-c678-jfcj-6jmf PyTorch Tuple Handler is Vulnerable to Memory Corruption through Manipulation of None Argument
    /workdirs/scan-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2025-2148). Fix: Update that package to its patched version.
  • Worth fixing GHSA-f4hp-rmr7-r7v8 PyTorch is Vulnerable to Memory Consumption through pad_packed_sequence Function
    /workdirs/scan-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2025-2998). Fix: Update that package to its patched version.
  • Worth fixing GHSA-qfhq-4f3w-5fph PyTorch is vulnerable to memory corruption through its torch.lstm_cell function
    /workdirs/scan-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2025-3001). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rrmf-rvhw-rf47 PyTorch is vulnerable to memory corruption through its torch.jit.script function
    /workdirs/scan-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2025-3000). Fix: Update that package to its patched version.
  • Worth fixing GHSA-vgrw-7cvw-pwgx PyTorch is vulnerable to memory corruption through its unpack_sequence function
    /workdirs/scan-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2025-2999). Fix: Update that package to its patched version.
  • Minor GHSA-x3gm-94wq-g975 PyTorch: Manipulation of the argument scale/zero_point leads to improper initialization via Quantized Sigmoid Module
    /workdirs/scan-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2025-2149). Fix: Update that package to its patched version.
  • FYI PYSEC-2024-250 Pytorch before v2.2.0 has an Out-of-bounds Read vulnerability via the component torch/csrc/jit/mobile/flatbuffer_loader.cpp.
    /workdirs/scan-3b7c9a2c-e3a7-4e6d-9879-e354fb6ecb4a/requirements.txt
    A package you depend on has a known security hole (CVE-2024-31584). Fix: Update that package to its patched version.

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ⓘ timed out

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

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via Guarddog v2.10.0 · Apache-2.0

error: pypi:timeout

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.

  • Worth fixing scorecard-overall OpenSSF Scorecard overall: 2.0/10
    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-Code-Review Code-Review scored 0: Found 0/5 approved changesets -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Dependency-Update-Tool Dependency-Update-Tool scored 0: no update tool 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: project was created within the last 90 days. Please review its contents carefully
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-SAST SAST scored 0: no SAST tool detected
    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.