← Back to scan
File as GitHub Issue repo: NVIDIA/garak

Push this scan report to NVIDIA/garak

Click the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Unsafe PyTorch Model Loading

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
HIGH SEC013 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file pat… tools/packagehallucination/ruby/main.py:43
HIGH SEC013 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file pat… tools/packagehallucination/javascript/m…:45
HIGH SEC004 [SEC004] SQL Injection Risk: String interpolation in SQL execution. Allows SQL injection. garak/cli.py:563
HIGH BINARY_RISK [BINARY] scipy: compound risk score 2194 (CVEs: 0, binary findings: 550) —
MED SEC011 [SEC011] Unsafe PyTorch Model Loading: torch.load() uses pickle internally and can execut… garak/resources/autodan/autodan.py:142
MED ERR001 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even… garak/evaluators/base.py:309
MED ERR001 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even… garak/detectors/exploitation.py:128
MED SEC014 [SEC014] SSL Verification Disabled: SSL certificate verification is disabled, allowing ma… garak/generators/websocket.py:245
MED SEC014 [SEC014] SSL Verification Disabled: SSL certificate verification is disabled, allowing ma… garak/generators/rest.py:210
MED AIC003 Duplicated implementation block across source files garak/probes/fitd.py:84
MED AIC003 Duplicated implementation block across source files garak/analyze/qual_review.py:160
MED AIC003 Duplicated implementation block across source files garak/analyze/get_tree.py:60
MED AIC003 Duplicated implementation block across source files garak-report/src/types/ProbesChart.ts:32
Reset to top 5 13 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `NVIDIA/garak`

**Score: 75/100 (B+)**  ·  18 findings  ·  scanned 2026-05-15 16:00 UTC  ·  67,009 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 4 |
| MEDIUM | 9 |
| LOW | 0 |

📊 [Full filterable report](https://repobility.com/scan/1251ce22-878f-4008-a1db-1b422bd654c9/)  ·  ![scorecard](https://repobility.com/scan/1251ce22-878f-4008-a1db-1b422bd654c9/report.png?v=1778860815-s2)

### Top findings

1. **HIGH** `SEC013` — Path Traversal — User Input in File Path
   `tools/packagehallucination/ruby/main.py:43` · A01:2021 Broken Access Control (path traversal)
2. **HIGH** `SEC013` — Path Traversal — User Input in File Path
   `tools/packagehallucination/javascript/main.py:45` · A01:2021 Broken Access Control (path traversal)
3. **HIGH** `SEC004` — SQL Injection Risk
   `garak/cli.py:563` · A03:2021 Injection
4. **HIGH** `BINARY_RISK` — scipy: compound risk score 2194 (CVEs: 0, binary findings: 550)
5. **MEDIUM** `SEC011` — Unsafe PyTorch Model Loading
   `garak/resources/autodan/autodan.py:142` · A08:2021 Software & Data Integrity Failures

---

**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/1251ce22-878f-4008-a1db-1b422bd654c9/_
Already filed
This repo publishes a SECURITY.md policy and the scan contains 3 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'NVIDIA/garak' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
I read the warnings â override Cancel

The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.

For real security findings on big repos: use the project's SECURITY.md or private advisory flow instead of a public issue.