chore(deps): bump lxml from 6.0.2 to 6.1.0

[dependabot]

Bumps lxml from 6.0.2 to 6.1.0.

Changelog

Sourced from lxml's changelog.

6.1.0 (2026-04-17)

This release fixes a possible external entity injection (XXE) vulnerability in iterparse() and the ETCompatXMLParser.

Features added

• GH#486: The HTML ARIA accessibility attributes were added to the set of safe attributes in lxml.html.defs. This allows lxml_html_clean to pass them through. Patch by oomsveta.

• The default chunk size for reading from file-likes in iterparse() is now configurable with a new chunk_size argument.

Bugs fixed

• LP#2146291: The resolve_entities option was still set to True for iterparse and ETCompatXMLParser, allowing for external entity injection (XXE) when using these parsers without setting this option explicitly. The default was now changed to 'internal' only (as for the normal XML and HTML parsers since lxml 5.0). Issue found by Sihao Qiu as CVE-2026-41066.

6.0.4 (2026-04-12)

Bugs fixed

• LP#2148019: Spurious MemoryError during namespace cleanup.

6.0.3 (2026-04-09)

Bugs fixed

• Several out of memory error cases now raise MemoryError that were not handled before.

• Slicing with large step values (outside of +/- sys.maxsize) could trigger undefined C behaviour.

• LP#2125399: Some failing tests were fixed or disabled in PyPy.

• LP#2138421: Memory leak in error cases when setting the public_id or system_url of a document.

... (truncated)

Commits

• 43722f4 Update changelog.
• 8747040 Name version of option change in docstring.
• 6c36e6c Fix pypistats URL in download statistics script.
• c7d76d6 Change security policy to point to Github security advisories.
• 378ccf8 Update project income report.
• 315270b Docs: Reduce TOC depth of package pages and move module contents first.
• 6dbba7f Docs: Show current year in copyright line.
• e4385bf Update project income report.
• 5bed1e1 Validate file hashes in release download script.
• c13ee10 Prepare release of 6.1.0.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

Note

Medium Risk
Dependency-only change, but lxml is a widely used XML/HTML parsing library and version bumps can subtly change parsing/serialization behavior. The update is security-motivated (XXE hardening), which may affect code relying on previous entity-resolution defaults.

Overview
Updates the pinned lxml dependency in uv.lock from 6.0.2 to 6.1.0, refreshing the associated sdist and wheel artifact hashes/URLs.

This brings in upstream security fixes (notably XXE hardening in iterparse()/ETCompatXMLParser) and other minor release changes via the lockfile update.

^{Reviewed by Cursor Bugbot for commit 73ffbe9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Security review completed for this PR.

Result: No high-confidence vulnerabilities found.

What changed

• Only uv.lock was modified.
• lxml was bumped from 6.0.2 to 6.1.0.
• Locked artifact hashes were updated (sdist/wheels remain hash-pinned to PyPI artifacts).

Threat-model assessment

• No application code changes, so no new injection/authn/authz/SSRF/XSS/request-forgery paths were introduced in this diff.
• No secrets handling or logging paths changed.

Residual supply-chain risk (low confidence / general)

• As with any dependency upgrade, trust shifts to the upstream release contents.
• Recommended validation before merge: keep CI green, run dependency vulnerability scanning (pip-audit/equivalent), and ensure lockfile install is performed in frozen mode.

  

_{Sent by Cursor Automation: Find vulnerabilities}