[GHSA-9f4q-q82q-4359] Docling's METS GBS backend is vulnerable to XML Entity Expansion (XXE) attacks - #9914
Open
chrikrah wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
chrikrah/advisory-improvement-9914
October 1, 2026 00:22
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
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.
Updates
Comments
The record says
introduced: 0,last_affected: 2.61.0. The METS GBS backend first shipped in 2.45.0, and_validate_mets_xmlcalledetree.fromstring(xml_string)with no parser until docling-project/docling#3336, first released in 2.91.0. This change moves both bounds to>= 2.45.0, < 2.91.0and adds the fix PR, commit and release.A
.tar.gzwith one METS file that holds five nested entities, loaded byMetsGbsDocumentBackendfrom a worktree at each tag:The JATS fix, docling-project/docling#3009, did not touch this backend, so GHSA-cr42-rg2m-mq4q gets 2.74.0 in a separate PR.
If you would rather keep
last_affected, the value is 2.90.0: 2.90.1 was tagged but never published to PyPI.