chore(deps): bump vulnerable dependencies

[stuxf]

Relevant issues

Closes open Dependabot alerts against uv.lock and the runtime-stage npm pins in Dockerfile.

Pre-Submission checklist

• I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Type

🚄 Infrastructure

Changes

Python (pyproject.toml):

• pypdf 6.7.5 → 6.10.2
• llm-sandbox 0.3.31 → 0.3.39
• Pillow 12.1.1 → 12.2.0
• orjson 3.11.5 → 3.11.6
• PyJWT 2.11.0 → 2.12.0
• aiohttp 3.13.3 → 3.13.4
• python-dotenv 1.0.1 → 1.2.2
• mlflow 3.9.0 → 3.11.1
• black 24.10.0 → 26.3.1
• pytest 8.3.5 → 9.0.3
• pytest-asyncio 1.2.0 → 1.3.0

Runtime-stage npm pins (Dockerfile):

• glob 11.1.0 → 13.0.6
• @isaacs/brace-expansion 5.0.1 → 5.0.5
• picomatch 4.0.4 pinned (new)

The six per-package find … | while read override stanzas in the runtime stage are collapsed into a single loop over the pinned package list.

[veria-ai]

Low: Dependency version bumps and Docker image updates

This PR bumps dependencies (aiohttp, python-dotenv, orjson, PyJWT, Pillow, etc.), updates base Docker images and uv tool versions with pinned sha256 digests, and refactors the npm package override loop in the Dockerfile. No security issues found.

---

Status: 0 open
Risk: 1/10

Posted by Veria AI · 2026-04-24T00:38:33.380Z

[greptile-apps]

Greptile Summary

This PR bumps vulnerable Python and npm dependencies, updates base image digests across all Dockerfiles, upgrades the UV tool image from 0.10.9 to 0.11.7, and refactors the npm override loop in the main Dockerfile into a single consolidated for loop.

• docker/Dockerfile.database was not updated with the new npm package versions — it still installs glob@11.1.0 and @isaacs/brace-expansion@5.0.1, leaving the Dependabot alerts open for images built from this Dockerfile.
• Dockerfile (main): @isaacs/brace-expansion remains at 5.0.1 despite the PR description stating it is bumped to 5.0.5; the unscoped brace-expansion@5.0.5 (a distinct npm package) was added instead, which may not resolve the alert against the scoped package.

Confidence Score: 3/5

Not safe to merge — two Dockerfiles still ship the vulnerable npm packages this PR is intended to fix.

Two confirmed P1 issues: Dockerfile.database was not updated and still installs glob@11.1.0/@isaacs/brace-expansion@5.0.1, and the main Dockerfile carries @isaacs/brace-expansion@5.0.1 unchanged despite the stated goal.

docker/Dockerfile.database (missing all npm security updates) and Dockerfile (line 72, @isaacs/brace-expansion still at 5.0.1)

Important Files Changed

Filename	Overview
Dockerfile	Updates base image digests, UV version, and glob to 13.0.6; refactors override loop; but @isaacs/brace-expansion remains at the vulnerable 5.0.1
docker/Dockerfile.database	Only removes the sed -i stanza; npm install line still uses glob@11.1.0 and @isaacs/brace-expansion@5.0.1, leaving vulnerable packages and missing the consolidated override loop from the main Dockerfile
pyproject.toml	Bumps python-dotenv, aiohttp, orjson, PyJWT, mlflow, pypdf, llm-sandbox, Pillow, black (24→26), pytest (8→9), pytest-asyncio; major-version jumps on dev tools worth CI validation
enterprise/pyproject.toml	Relaxes required-version from ==0.10.9 to >=0.10.9 to allow newer uv versions
litellm-proxy-extras/pyproject.toml	Same required-version relaxation as enterprise/pyproject.toml; no other changes

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[npm install global packages] --> B{Dockerfile variant}
    B -->|main Dockerfile| C["glob@13.0.6 ✅\n@isaacs/brace-expansion@5.0.1 ⚠️\nbrace-expansion@5.0.5 ✅\npicomatch@4.0.4 ✅"]
    B -->|Dockerfile.database| D["glob@11.1.0 ❌\n@isaacs/brace-expansion@5.0.1 ❌\nno picomatch ❌"]
    B -->|Dockerfile.alpine / .dev / .health_check / .non_root| E["No npm pins\nUV image updated ✅"]
    C --> F[Consolidated for-loop override]
    D --> G[Old per-package find loops - sed stanza only removed]
    F --> H[npm cache clean]
    G --> I[npm cache clean - vulnerable packages remain]

Loading

Comments Outside Diff (1)

1. docker/Dockerfile.database, line 70-86 (link)

   Vulnerable npm packages not updated

   Dockerfile.database still installs glob@11.1.0 and @isaacs/brace-expansion@5.0.1 — the exact vulnerable versions this PR is supposed to remediate. Unlike the main Dockerfile, which was refactored to use glob@13.0.6, brace-expansion@5.0.5, and picomatch@4.0.4, this file only had its sed -i stanza removed. The consolidated override loop was never added, so images built from this Dockerfile remain affected by the Dependabot alerts.

_{Reviews (5): Last reviewed commit: "chore(deps): fix brace-expansion pin and..." | Re-trigger Greptile}

[codecov]

Codecov Report

❌ Patch coverage is 90.63116% with 95 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
litellm/router_strategy/adaptive_router/hooks.py	84.67%	19 Missing ⚠️
...opic/experimental_pass_through/adapters/handler.py	42.85%	12 Missing ⚠️
...y/management_endpoints/mcp_management_endpoints.py	80.95%	12 Missing ⚠️
litellm/proxy/auth/auth_checks.py	75.00%	7 Missing ⚠️
...router_strategy/adaptive_router/adaptive_router.py	96.22%	6 Missing ⚠️
...rtex_ai/image_edit/vertex_imagen_transformation.py	58.33%	5 Missing ⚠️
.../llms/dashscope/image_generation/transformation.py	93.10%	4 Missing ⚠️
litellm/router_strategy/adaptive_router/signals.py	97.24%	4 Missing ⚠️
...lm/router_strategy/adaptive_router/update_queue.py	93.54%	4 Missing ⚠️
...llm/litellm_core_utils/prompt_templates/factory.py	25.00%	3 Missing ⚠️
... and 12 more

📢 Thoughts on this report? Let us know!