chore(deps): bump pillow to 12.3.0 to resolve osv-scan CVEs

[yucheng-berri]

Relevant issues

Fixes #33091

Linear ticket

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have added meaningful tests
• My PR passes all CI/CD checks (e.g., lint, format, unit tests)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

Screenshots / Proof of Fix

Before (any PR against litellm_internal_staging, e.g. #31099): the osv-scan check fails with

Total 1 package affected by 5 known vulnerabilities (0 Critical, 4 High, 1 Medium, 0 Low, 0 Unknown)

| https://osv.dev/PYSEC-2026-2253 | 7.5 | pillow | 12.2.0 | 12.3.0 |
| https://osv.dev/PYSEC-2026-2254 | 7.5 | pillow | 12.2.0 | 12.3.0 |
| https://osv.dev/PYSEC-2026-2255 | 7.5 | pillow | 12.2.0 | 12.3.0 |
| https://osv.dev/PYSEC-2026-2256 | 7.5 | pillow | 12.2.0 | 12.3.0 |
| https://osv.dev/PYSEC-2026-2257 | 4.5 | pillow | 12.2.0 | 12.3.0 |

After: the osv-scan check on this PR runs against pillow 12.3.0 and reports no known vulnerabilities (proof is the green osv-scan check on this PR's HEAD, commit 84dd160; will update here once CI completes)

No runtime behavior changes; pillow is only in the ci dependency group, so there is no live-proxy surface to exercise

Type

🐛 Bug Fix
🚄 Infrastructure

Changes

Bumps Pillow from 12.2.0 to 12.3.0 in the ci dependency group of pyproject.toml and regenerates uv.lock via uv lock --upgrade-package pillow. The lock was regenerated with uv 0.10.9 (the version family that wrote the current staging lock) so the diff touches only pillow's entry (version, sdist, per-platform wheel hashes) plus the exclude-newer timestamp that uv refreshes on every relock; regenerating with uv 0.11.x adds a few hundred lines of unrelated marker and option normalization churn. Verified with uv lock --check under both uv 0.10.9 and 0.11.26 against current litellm_internal_staging

Pillow 12.2.0 has 5 known CVEs (PYSEC-2026-2253 through PYSEC-2026-2257, 4 High and 1 Medium) that are fixed in 12.3.0, which made the osv-scan check fail on every PR

Credit

Adopted from #33089 by @yamaceay. Mirrored onto a litellm_ branch because fork PRs must not modify uv.lock, so lockfile changes have to come from a branch in the canonical repository

Final Attestation

• The tests check the right things, including the edge cases, and regressions in the respective real-world customer use-cases are not possible after this PR

---

Note

Low Risk
Dependency-only bump in the CI group with no application code changes; typical patch-level security upgrade risk.

Overview
Bumps Pillow from 12.2.0 to 12.3.0 in the ci dependency group in pyproject.toml and refreshes uv.lock (pillow pins, wheel hashes, and uv’s exclude-newer timestamp).

This addresses five known vulnerabilities on 12.2.0 (PYSEC-2026-2253–2257) so osv-scan can pass. Pillow stays CI-only, not in core or proxy installs, so production dependency surfaces are unchanged.

^{Reviewed by Cursor Bugbot for commit 84dd160. Bugbot is set up for automated code reviews on this repo. Configure here.}

[yucheng-berri]

@greptileai

[greptile-apps]

Greptile Summary

This PR bumps Pillow from 12.2.0 to 12.3.0 in the ci dependency group of pyproject.toml and regenerates uv.lock accordingly. Pillow is used only in CI (not in production/proxy code), so there is no runtime surface affected.

• pyproject.toml: Single-line version change; correctly scoped to the ci dependency group.
• uv.lock: Pillow entry updated to 12.3.0 with new sdist/wheel hashes; the exclude-newer timestamp advances to the relock time (2026-07-10T16:47:58.286372Z), and some dependency marker conditions for unrelated packages were normalized as a uv relocking side-effect.

Confidence Score: 5/5

Safe to merge — Pillow is a CI-only dependency with no production surface, and the version bump correctly targets the patched release.

The pyproject.toml change is a single targeted line touching only the ci dependency group. The uv.lock update carries the expected wheel/sdist hash replacements for Pillow plus minor marker normalization from relocking, which does not affect resolved package versions for any production or SDK dependency.

No files require special attention.

Important Files Changed

Filename	Overview
pyproject.toml	Single-line version bump of Pillow from 12.2.0 to 12.3.0 in the ci dependency group — clean and targeted
uv.lock	Lockfile regenerated: Pillow entry updated to 12.3.0 (new sdist/wheel hashes), exclude-newer timestamp updated to 2026-07-10; broader marker/dependency normalization changes are also present as uv relocking artifacts

_{Reviews (3): Last reviewed commit: "chore(ci): regenerate uv.lock with uv 0...." | Re-trigger Greptile}

[yucheng-berri]

Addressed in 84dd160; the lock was regenerated with uv 0.10.9 (matching the version family that wrote the staging lock), which removes the marker normalization churn and the exclude-newer sentinel rewrite. The remaining diff is the pillow entry plus the exclude-newer timestamp refresh that any relock performs, and the PR description was updated to say exactly that

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[yucheng-berri]

@greptileai

[codspeed-hq]

Merging this PR will not alter performance

✅ 31 untouched benchmarks

---

_{Comparing litellm_bump_pillow_12_3_0 (84dd160) with litellm_internal_staging (e6d916b)}

[yucheng-berri]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 84dd160. Configure here.}