Skip to content

fix: update Pygments to resolve CVE-2026-4539#28

Closed
dannyneira wants to merge 1 commit into
mainfrom
independabot/pygments-cve-2026-4539
Closed

fix: update Pygments to resolve CVE-2026-4539#28
dannyneira wants to merge 1 commit into
mainfrom
independabot/pygments-cve-2026-4539

Conversation

@dannyneira

Copy link
Copy Markdown
Member

Summary

  • Updates transitive dev dependency Pygments in uv.lock from 2.19.2 to 2.20.0 to resolve CVE-2026-4539 / GHSA-5239-wwwm-4pmq.
  • Keeps the fix scoped to the lockfile; no generated SDK source was modified.
  • Regenerating uv.lock also corrected the editable package metadata from oz-agent-sdk 0.4.0 to the project version declared in pyproject.toml, 0.13.0.

Vulnerability details

Verification

  • uv tree --package pygments shows pygments v2.20.0.
  • pip-audit --path .venv/lib/python3.9/site-packages --skip-editable reports Pygments 2.20.0 with no vulnerabilities. Existing findings are for aiohttp, idna, and pytest, which already have open PRs.
  • ./scripts/lint
  • ./scripts/test
  • uv build

Conversation: https://staging.warp.dev/conversation/79ba85ba-09a8-4c6d-a123-722a0564c0b9
Run: https://oz.staging.warp.dev/runs/019e83e9-dd9f-779c-a21b-2eeabe0784ea
This PR was generated with Oz.

Co-Authored-By: Oz <oz-agent@warp.dev>
@dannyneira dannyneira requested a review from ianhodge June 1, 2026 16:05

Copy link
Copy Markdown
Contributor

Closing — these fixes will be applied via the stlc/warp-server flow instead of direct SDK commits.

@liliwilson liliwilson closed this Jun 24, 2026
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.

3 participants