Skip to content

build(security): ignore pygments CVE-2026-4539 in pip-audit#2333

Merged
mattbit merged 1 commit intomainfrom
ci/pygments-cve
Mar 25, 2026
Merged

build(security): ignore pygments CVE-2026-4539 in pip-audit#2333
mattbit merged 1 commit intomainfrom
ci/pygments-cve

Conversation

@mattbit
Copy link
Copy Markdown
Member

@mattbit mattbit commented Mar 25, 2026

pip-audit fails until pygments ships a fix for this low-severity ReDoS issue. Since all pygments versions are affected and there's no patch we can't do much right now. (Added TODO note to remove --ignore-vuln once a patch is released)

pip-audit fails until pygments ships a fix for this low-severity ReDoS issue. The Makefile documents the TODO to remove --ignore-vuln when a patch exists.

Made-with: Cursor
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request provides a temporary workaround for a pip-audit failure caused by an unpatched, low-severity ReDoS vulnerability in pygments. By instructing pip-audit to ignore this specific CVE, the security checks can proceed without interruption, while also including a clear reminder to revert this change once a permanent fix is available.

Highlights

  • Security Scan Adjustment: Modified the security target in the Makefile to temporarily ignore CVE-2026-4539 for pygments during pip-audit scans.
  • Temporary Vulnerability Ignore: Added a TODO comment to remove the --ignore-vuln flag once a patch for the low-severity ReDoS issue in pygments is released.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@mattbit mattbit merged commit 0959675 into main Mar 25, 2026
13 checks passed
@mattbit mattbit deleted the ci/pygments-cve branch March 25, 2026 12:22
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 updates the Makefile to temporarily ignore a low-severity ReDoS vulnerability in pygments during pip-audit security checks. The reviewer identified that the CVE identifier used (CVE-2026-4539) is incorrect and should be CVE-2024-34064, which needs to be corrected for the --ignore-vuln flag to work as intended.

Comment on lines +82 to +84
# TODO: Remove --ignore-vuln CVE-2026-4539 flag when patch exists for pygments
# This is a low severity redos vulnerability: https://www.cve.org/CVERecord?id=CVE-2026-4539
uv run pip-audit --skip-editable --ignore-vuln CVE-2026-4539
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.

high

It appears there's a typo in the CVE identifier. The correct identifier for the recent low-severity ReDoS vulnerability in pygments that affects all versions is likely CVE-2024-34064, not CVE-2026-4539. Using the incorrect identifier will not suppress the pip-audit warning as intended and can cause confusion.

Please update the CVE identifier in the comments and the pip-audit command.

	# TODO: Remove --ignore-vuln CVE-2024-34064 flag when patch exists for pygments
	# This is a low severity redos vulnerability: https://www.cve.org/CVERecord?id=CVE-2024-34064
	uv run pip-audit --skip-editable --ignore-vuln CVE-2024-34064

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants