Loosen lxml pin to allow 6.1.x (security: CVE-2026-41066) - #217
Open
R4F4U wants to merge 1 commit into
Open
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
lxml~=6.0.2 excludes 6.1.0, which fixes CVE-2026-41066 / GHSA-vfmq-68hx-4jfw (XXE local-file read via the resolve_entities=True default). Downstream projects that depend on python-fints cannot adopt the lxml fix while the cap stays at <6.1. python-fints uses lxml only via etree.fromstring (fints/camt_parser.py); smoke-tested with lxml 6.1.0: import, namespaced parse and client import all ok.
Copy link
Copy Markdown
|
BUMP |
Sorry, something went wrong.
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
2 participants
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.
What
Loosen the lxml cap from lxml~=6.0.2 to lxml>=6.0.2,<7.
Why
lxml 6.1.0 fixes CVE-2026-41066 (GHSA-vfmq-68hx-4jfw / PYSEC-2026-87) — an
XXE local-file read via the resolve_entities=True parser default. The current
lxml~=6.0.2 cap (<6.1) prevents any project depending on python-fints from
upgrading lxml to the patched 6.1.x, so the security fix is blocked downstream.
Compatibility
python-fints uses lxml only through etree.fromstring (fints/camt_parser.py).
Smoke-tested against lxml 6.1.0:
No lxml API used by python-fints changed between 6.0 and 6.1; 6.1.0 only changes
the parser's default entity-resolution mode, which python-fints doesn't rely on.
Change
One line in pyproject.toml: lxml~=6.0.2 → lxml>=6.0.2,<7.