Skip to content

[Snyk] Security upgrade lxml from 5.4.0 to 6.1.0#1

Open
appfire-developer wants to merge 1 commit intomasterfrom
snyk-fix-3d72065e682fca5c11fbcd992e266cfa
Open

[Snyk] Security upgrade lxml from 5.4.0 to 6.1.0#1
appfire-developer wants to merge 1 commit intomasterfrom
snyk-fix-3d72065e682fca5c11fbcd992e266cfa

Conversation

@appfire-developer
Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • requirements.txt
⚠️ Warning
locust 1.3.1 requires pyzmq, which is not installed.
Flask 2.2.5 has requirement importlib-metadata>=3.6.0; python_version < "3.10", but you have importlib-metadata 3.1.1.
bzt 1.15.1 has requirement zipp==2.2.0, but you have zipp 3.15.0.
Appium-Python-Client 5.1.3 has requirement selenium<5.0,~=4.26, but you have selenium 4.11.2.

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 XML External Entity (XXE) Injection

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-LXML-16119103
@appfire-developer
Copy link
Copy Markdown
Author

Merge Risk: Medium

This major version upgrade from lxml 5.4.0 to 6.1.0 introduces breaking changes related to Python version support and security defaults.

Key Changes:

  • Python Version Support: Support for Python versions below 3.8 has been removed. Python 3.7 reached its end-of-life in June 2023, so projects should be on a newer version.
  • Security Default Change: To address a vulnerability (CVE-2026-41066), the resolve_entities option in iterparse and ETCompatXMLParser now defaults to 'internal' instead of True. This prevents external entity injection (XXE) by default.
  • Deprecation: The Schematron class is now deprecated and is planned to be removed in a future version.

Action Required:

  • Verify Python Version: Ensure your environment is running Python 3.8 or a newer version.
  • Check Parser Usage: If you use iterparse or ETCompatXMLParser and rely on resolving external entities, you must now explicitly set resolve_entities=True in the parser. It is recommended to review this usage for potential security implications.

Source: lxml Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants