Skip to content

chore: release v10.36.7 — security: bump pygments to 2.20.0 (CVE-2026-4539)#699

Merged
doobidoo merged 2 commits intomainfrom
fix/pygments-cve-2026-4539
Apr 14, 2026
Merged

chore: release v10.36.7 — security: bump pygments to 2.20.0 (CVE-2026-4539)#699
doobidoo merged 2 commits intomainfrom
fix/pygments-cve-2026-4539

Conversation

@doobidoo
Copy link
Copy Markdown
Owner

Summary

  • Bump pygments to 2.20.0 to fix CVE-2026-4539 (GHSA-5239-wwwm-4pmq): ReDoS via inefficient regex for GUID matching, transitive dependency via rich
  • Version bumped: 10.36.610.36.7 in _version.py, pyproject.toml, uv.lock
  • CHANGELOG, README Latest Release, and CLAUDE.md version callout updated

Test plan

  • CI passes (PyPI publish triggered by tag push)
  • 1,537 tests continue to pass
  • No landing page update needed (PATCH release)

Ref: CVE-2026-4539, GHSA-5239-wwwm-4pmq, PR #698

🤖 Generated with Claude Code

doobidoo and others added 2 commits April 14, 2026 18:28
Fixes a ReDoS via inefficient regex for GUID matching in Pygments'
highlighting. Transitive dependency (pulled in via rich); targeted
uv.lock update only.

GHSA-5239-wwwm-4pmq

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Bump pygments to 2.20.0 to fix CVE-2026-4539 (GHSA-5239-wwwm-4pmq,
ReDoS via inefficient regex for GUID matching, transitive via rich).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@doobidoo doobidoo merged commit 7552538 into main Apr 14, 2026
@doobidoo doobidoo deleted the fix/pygments-cve-2026-4539 branch April 14, 2026 16:37
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request increments the project version to 10.36.7 and updates the pygments dependency to 2.20.0 in the lock file to resolve a ReDoS vulnerability (CVE-2026-4539). Feedback suggests explicitly adding pygments>=2.20.0 to the project dependencies in pyproject.toml to ensure protection for users who do not utilize the lock file.

Comment thread pyproject.toml
[project]
name = "mcp-memory-service"
version = "10.36.6"
version = "10.36.7"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

security-medium medium

While updating the lock file addresses the security vulnerability for environments using it, pygments is a transitive dependency (via rich). To ensure that all users—including those installing via pip without the lock file—are protected from CVE-2026-4539, consider adding an explicit version constraint for pygments (e.g., pygments>=2.20.0) to the dependencies section of pyproject.toml.

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