Skip to content

Patch 39 of 41 dependabot alerts and 7 npm advisories#63

Open
MaxGhenis wants to merge 1 commit into
mainfrom
security-dep-bumps
Open

Patch 39 of 41 dependabot alerts and 7 npm advisories#63
MaxGhenis wants to merge 1 commit into
mainfrom
security-dep-bumps

Conversation

@MaxGhenis

Copy link
Copy Markdown
Contributor

Why

GitHub flags 41 dependabot alerts on the default branch (1 critical, 13 high), all in uv.lock. A bun audit pass on the app found 9 more npm advisories that dependabot misses because it doesn't scan bun.lock.

What

Python — 39 of 41 alerts fixed, lock-only bumps (every pyproject range already allowed the patched versions):

Package From → To Alerts
litellm 1.81.15 → 1.88.1 1 critical, 5 high
jupyter-server 2.17.0 → 2.19.0 3 high, 1 medium
tornado 6.5.4 → 6.5.7 2 high, 1 medium
urllib3 2.6.3 → 2.7.0 2 high
mistune 3.2.0 → 3.2.1 1 high, 5 medium
aiohttp 3.13.3 → 3.14.1 12 (low–medium)
nbconvert, requests, idna, python-dotenv, pygments → patched rest

Not fixable by bumping (2 alerts stay open):

  • pytest 8.4.2 (medium, GHSA-6w46-j5rx-g56g): policyengine-core pins pytest<9. Dev-only test runner; clears whenever the policyengine stack bump (e.g. #59) pulls a core that allows pytest 9.
  • diskcache 5.6.3 (medium, GHSA-w8v5-vhqr-4h9v): no patched release exists. Used only via litellm[caching] for the local, self-written response cache in .policybench_cache/ — exploitation requires an attacker who can already write local files.

npm — 7 of 9 advisories fixed via @lobehub/icons 5.2 → 5.10 plus package.json overrides: dompurify 3.4.8, lodash/lodash-es 4.18.1 (high, _.template code injection), postcss 8.5.14, js-cookie 3.0.8, mermaid 11.15.0, uuid 13.0.1. All transitive — none of these ship in the client bundle (they ride in via @lobehub/icons → @lobehub/ui → mermaid/ahooks).

Accepted for now (2): brace-expansion 5.0.5 and picomatch 4.0.3 — both dev/build-only (eslint and tailwind/next toolchains), and both trees hold two majors of the package, which bun's flat overrides can't scope to one side without forcing unrelated consumers across a major.

Verification

  • Python: 279 tests pass, ruff clean, policybench --help imports the full CLI against litellm 1.88
  • App: lint, bun tests, and a production next build (with static generation) pass
  • bun audit down from 9 advisories to the 2 accepted dev-only ones

Follow-up worth considering

@lobehub/icons pulls ~1,000 packages (mermaid, dagre, ahooks, uuid…) to render a handful of provider marks — replacing it with inline SVGs would delete most of this attack surface permanently.

🤖 Generated with Claude Code

Python (uv.lock, lock-only bumps; pyproject ranges already allowed them):
litellm 1.81.15->1.88.1 (the critical alert plus five high), tornado
6.5.7, jupyter-server 2.19.0, mistune 3.2.1, urllib3 2.7.0, aiohttp
3.14.1, pygments 2.20.0, python-dotenv 1.2.2, nbconvert 7.17.1,
requests 2.34.2, idna 3.18.

Not fixable by bumping:
- pytest stays 8.4.2: policyengine-core pins pytest<9 (medium, tmpdir
  handling in a dev-only test runner)
- diskcache 5.6.3: no patched release exists (unsafe pickle; only used
  for the local self-written litellm response cache)

npm (bun audit; dependabot does not scan bun.lock): bump
@lobehub/icons to 5.10.0 and pin overrides for dompurify 3.4.8,
lodash 4.18.1, lodash-es 4.18.1, postcss 8.5.14, js-cookie 3.0.8,
mermaid 11.15.0, uuid 13.0.1 - all transitive, mostly via the
@lobehub/icons -> @lobehub/ui graph. brace-expansion 5.0.5 and
picomatch 4.0.3 remain: dev/build-only chains where the tree holds two
majors and bun's flat overrides cannot scope to one of them.

Verified: 279 Python tests, ruff, CLI smoke; app lint, bun tests, and
a production next build all pass on the upgraded stack.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
policybench-site Ready Ready Preview, Comment Jun 10, 2026 5:22am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant