Skip to content

fix(deps): remediate GitPython and AnyIO vulnerabilities #1857

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mldangelo-oai wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix(deps): remediate GitPython and AnyIO vulnerabilities #1857

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
46986e6
fix(deps): upgrade GitPython security floor
mldangelo-oai Sep 19, 2026
ac1483f
fix(deps): upgrade AnyIO security floor
mldangelo-oai Sep 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

- Upgrade gzip, PCRE2, SQLite, and Perl in Docker runtime images to pick up Debian security fixes.
- Upgrade locked GitPython to 3.1.59 to address four dependency audit advisories.
- Upgrade locked GitPython to 3.1.60 to address newly disclosed dependency audit advisories.
- Inspect hidden ZIP archives and malicious pickle payloads in legacy GGML model variants.
- Stop reporting a ZIP polyglot for GGUF/GGML files whose tensor data merely contains an end-of-central-directory signature.
- Upgrade Debian util-linux packages in all Docker runtime images to remediate CVE-2026-53615.
Expand Down
4 changes: 3 additions & 1 deletion tests/test_dependency_lock.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,8 @@
ROOT_PYPROJECT = ROOT_DIR / "pyproject.toml"
RENOVATE_CONFIG = ROOT_DIR / "renovate.json"
PICKLESCAN_PYPROJECT = ROOT_DIR / "packages" / "modelaudit-picklescan" / "pyproject.toml"
PATCHED_GITPYTHON_FLOOR = (3, 1, 59)
PATCHED_GITPYTHON_FLOOR = (3, 1, 60)

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 19, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Enforce the patched GitPython floor in package metadata

This guard only raises the version in uv.lock, which is not included in the published wheel's dependency metadata. The mlflow, all-ci, and all extras still declare only mlflow-skinny>=3.13.0; because that release already resolved successfully with GitPython 3.1.59 in the parent lock, an installation with 3.1.59 already present or constrained can retain the vulnerable version. Add GitPython>=3.1.60 to the relevant extras and make this regression test assert those declarations so the security floor also protects package consumers.

Useful? React with 👍 / 👎.

PATCHED_ANYIO_FLOOR = (4, 14, 2)
PINNED_MATURIN_BACKEND = "maturin===1.13.3"
REQUIRED_PICKLESCAN_RELEASE = "modelaudit-picklescan>=0.1.10,<0.2.0"
PATCHED_PY7ZR_REQUIREMENT = "py7zr>=1.1.3"
Expand Down Expand Up @@ -81,6 +82,7 @@ def test_gitpython_lock_stays_on_patched_release_floor() -> None:
("package_name", "patched_floor"),
[
("aiohttp", (3, 14, 3)),
("anyio", PATCHED_ANYIO_FLOOR),
("cryptography", (50, 0, 0)),
("keras", (3, 15, 0)),
("sqlparse", (0, 6, 0)),
Expand Down
12 changes: 6 additions & 6 deletions uv.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading