You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,17 @@
1
1
# Changelog
2
2
3
+
## [v0.24.1] - 2026-04-22
4
+
5
+
### Security
6
+
7
+
-**lxml floor `>=6.1.0`** to patch CVE-2026-41066 (GHSA-vfmq-68hx-4jfw): default configuration of `iterparse()` and `ETCompatXMLParser()` allowed XXE to local files (`resolve_entities=True`). lxml 6.1.0 changes the default to `resolve_entities='internal'`. Transitive via `docling`; floor added to the `docling` extra in `pyproject.toml` so downstream installs of `pipelex[docling]` cannot resolve a vulnerable version.
8
+
-**cryptography floor `>=46.0.7`** to patch CVE-2026-39892 (GHSA-p423-j2cm-9vmq): non-contiguous Python buffers passed to hashing APIs (e.g. `Hash.update()`) could read past the end of the buffer on Python >3.11. Transitive via `google-auth` (pulled by `google`, `gcp-storage`, `google-genai` extras) and `moto` (dev). Floor added to each affected extra in `pyproject.toml` — previous bump was lockfile-only, which did not protect downstream users resolving fresh from PyPI metadata.
9
+
-**pytest bumped to 9.0.3** to patch CVE-2025-71176 (GHSA-6w46-j5rx-g56g): vulnerable `/tmp/pytest-of-{user}` directory handling on UNIX could let a local user cause DoS or gain privileges. Dev-only dependency; `pyproject.toml` minimum bumped from `>=9.0.2` to `>=9.0.3`.
10
+
-**transformers CVE-2026-1839 (GHSA-69w3-r845-3855) risk-accepted, alert dismissed.** The vulnerability requires calling `transformers.Trainer._load_rng_state()` with an attacker-controlled checkpoint file. Pipelex only pulls `transformers` transitively through `docling-ibm-models` for PDF layout inference; the `Trainer` class is never imported or executed. Upgrade path is blocked upstream: `docling-ibm-models` 3.13.0 pins `transformers!=5.0.*,!=5.1.*,!=5.2.*,!=5.3.*,<6.0.0,>=4.42.0`, explicitly excluding the patched 5.0.0rc3 release. Revisit when `docling-ibm-models` adds support for `transformers>=5.4`.
11
+
-**Release-publishing GitHub Actions pinned to SHAs**: `pypa/gh-action-pypi-publish` and `sigstore/gh-action-sigstore-python` in `publish-pypi.yml` are now pinned to full commit SHAs (version kept as a trailing comment) so a compromised tag on a third-party action cannot silently alter a PyPI release. Dependabot keeps them fresh.
12
+
-**`.github/dependabot.yml` added**: declares `pip` and `github-actions` ecosystems, weekly cadence, with dev and runtime deps grouped to reduce PR noise. Security updates fire immediately regardless of schedule.
13
+
-**`dependency-review.yml` workflow added**: runs GitHub's `dependency-review-action` on PRs to `main`, `dev`, and release branches. Fails the PR if it introduces a dependency with a moderate-or-higher CVE. Respects the existing transformers (GHSA-69w3-r845-3855) risk-acceptance via `allow-ghsas`. Enable as a required status check in branch protection for `main` to block vulnerable merges.
0 commit comments