fix(security): bump pyarrow >=23.0.1 for PYSEC-2026-113#55
Merged
Conversation
OSV scanner flagged pyarrow 17.0.0 in space/requirements.txt with PYSEC-2026-113 (CVSS 7.0 High), fixed in 23.0.1. This was blocking the Merge Gate on every open PR. Raise the lower-bound to >=23.0.1. HF Spaces resolves the actual installed version against this constraint, so the Space will pick up a fix-version build on next deploy. No code changes needed; the viewer only uses pandas/pyarrow.Table for parquet reads, both of which are stable across the 17→23 window. Added a new line in the CVE history comment to document why the lower-bound was raised, matching the existing pillow / orjson / idna entries. Assisted-by: Claude <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the pyarrow dependency in space/requirements.txt to version 23.0.1 to address a high-severity security vulnerability (PYSEC-2026-113). The reviewer suggests extending this update to pyproject.toml to ensure the fix is applied to the core library and not just the Space deployment.
Gemini's review on PR #55 correctly flagged that the previous commit only bumped the Space requirements.txt; the core mlx-benchmarks library still declared `pyarrow>=17.0.0` in pyproject.toml. Library users installing this package as a dependency would still resolve to a vulnerable pyarrow without an explicit floor. Bump pyproject.toml's pyarrow constraint to >=23.0.1 (matching the Space). uv lock regenerated; the actual resolved version stays at 24.0.0 (latest), so no behavioral change — just the declared security floor. Assisted-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OSV scanner flagged
pyarrow 17.0.0inspace/requirements.txtwith PYSEC-2026-113 (CVSS 7.0 High), fixed in 23.0.1. The Merge Gate on every open PR (#54, #49, #47) was blocked on this.Raise the lower-bound to
>=23.0.1. HF Spaces resolves the actual installed version against the constraint, so the Space picks up a fix-version build on next deploy — no Space code changes required (the viewer only usespandas/pyarrow.Tablefor parquet reads, stable across the 17→23 window).Adds a new line in the CVE-history comment block to document why the lower-bound was raised, matching the existing
pillow/orjson/idnaentries.Test plan
pre-commit run --all-filesclean (space/requirements.txtis a one-line edit)Unblocks
🤖 Generated with Claude Code