Skip to content

litellm_fix(security): allowlist Next.js CVEs for 7 days #20169

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ishaan-jaff merged 1 commit into from
Jan 31, 2026
Merged

litellm_fix(security): allowlist Next.js CVEs for 7 days #20169

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .trivyignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# LiteLLM Trivy Ignore File
# CVEs listed here are temporarily allowlisted pending fixes

# Next.js vulnerabilities in UI dashboard (next@14.2.35)
# Allowlisted: 2026-01-31, 7-day fix timeline
Copy link
Contributor

@greptile-apps greptile-apps bot Jan 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 7-day expiration date (2026-01-31) is documented but not automatically enforced. Consider adding a reminder mechanism (GitHub issue, calendar reminder, or CI check) to ensure this allowlist is removed after the deadline.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Prompt To Fix With AI 
This is a comment left during a code review.
Path: .trivyignore
Line: 5:5

Comment:
The 7-day expiration date (2026-01-31) is documented but not automatically enforced. Consider adding a reminder mechanism (GitHub issue, calendar reminder, or CI check) to ensure this allowlist is removed after the deadline.

<sub>Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!</sub>

How can I resolve this? If you propose a fix, please make it concise.

# Fix: Upgrade to Next.js 15.5.10+ or 16.1.5+

# HIGH: DoS via request deserialization
GHSA-h25m-26qc-wcjf

# MEDIUM: Image Optimizer DoS
CVE-2025-59471
4 changes: 2 additions & 2 deletions ci_cd/security_scans.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,10 +81,10 @@ run_trivy_scans() {
echo "Running Trivy scans..."

echo "Scanning LiteLLM Docs..."
trivy fs --scanners vuln --dependency-tree --exit-code 1 --severity HIGH,CRITICAL,MEDIUM ./docs/
trivy fs --ignorefile .trivyignore --scanners vuln --dependency-tree --exit-code 1 --severity HIGH,CRITICAL,MEDIUM ./docs/

echo "Scanning LiteLLM UI..."
trivy fs --scanners vuln --dependency-tree --exit-code 1 --severity HIGH,CRITICAL,MEDIUM ./ui/
trivy fs --ignorefile .trivyignore --scanners vuln --dependency-tree --exit-code 1 --severity HIGH,CRITICAL,MEDIUM ./ui/
Comment on lines +84 to +87
Copy link
Contributor

@greptile-apps greptile-apps bot Jan 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The .trivyignore file is applied to both ./docs/ and ./ui/ scans, but the allowlisted CVEs (GHSA-h25m-26qc-wcjf, CVE-2025-59471) are specific to Next.js in the UI directory. If these CVE IDs appear in docs for unrelated packages, they'll be incorrectly ignored. Consider scoping the ignorefile to only the UI scan.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Prompt To Fix With AI 
This is a comment left during a code review.
Path: ci_cd/security_scans.sh
Line: 84:87

Comment:
The `.trivyignore` file is applied to both `./docs/` and `./ui/` scans, but the allowlisted CVEs (GHSA-h25m-26qc-wcjf, CVE-2025-59471) are specific to Next.js in the UI directory. If these CVE IDs appear in docs for unrelated packages, they'll be incorrectly ignored. Consider scoping the ignorefile to only the UI scan.

<sub>Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!</sub>

How can I resolve this? If you propose a fix, please make it concise.


echo "Trivy scans completed successfully"
}
Expand Down
Loading