chore(deps): bump lxml from 6.0.1 to 6.1.0 in /02-use-cases/customer-support-assistant-vpc/agent by dependabot[bot] · Pull Request #1387 · awslabs/agentcore-samples

dependabot · 2026-04-21T22:48:09Z

Bumps lxml from 6.0.1 to 6.1.0.

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.

Bumps [lxml](https://github.com/lxml/lxml) from 6.0.1 to 6.1.0. - [Release notes](https://github.com/lxml/lxml/releases) - [Changelog](https://github.com/lxml/lxml/blob/master/CHANGES.txt) - [Commits](lxml/lxml@lxml-6.0.1...lxml-6.1.0) --- updated-dependencies: - dependency-name: lxml dependency-version: 6.1.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

github-actions · 2026-04-21T22:53:55Z

Latest scan for commit: 44041b1 | Updated: 2026-04-21 22:53:54 UTC

Security Scan Results

Scan Metadata

Project: ASH
Scan executed: 2026-04-21T22:53:32+00:00
ASH version: 3.0.0

Summary

Scanner Results

The table below shows findings by scanner, with status based on severity thresholds and dependencies:

Column Explanations:

Severity Levels (S/C/H/M/L/I):

Suppressed (S): Security findings that have been explicitly suppressed/ignored and don't affect the scanner's pass/fail status
Critical (C): The most severe security vulnerabilities requiring immediate remediation (e.g., SQL injection, remote code execution)
High (H): Serious security vulnerabilities that should be addressed promptly (e.g., authentication bypasses, privilege escalation)
Medium (M): Moderate security risks that should be addressed in normal development cycles (e.g., weak encryption, input validation issues)
Low (L): Minor security concerns with limited impact (e.g., information disclosure, weak recommendations)
Info (I): Informational findings for awareness with minimal security risk (e.g., code quality suggestions, best practice recommendations)

Other Columns:

Time: Duration taken by each scanner to complete its analysis
Action: Total number of actionable findings at or above the configured severity threshold that require attention

Scanner Results:

PASSED: Scanner found no security issues at or above the configured severity threshold - code is clean for this scanner
FAILED: Scanner found security vulnerabilities at or above the threshold that require attention and remediation
MISSING: Scanner could not run because required dependencies/tools are not installed or available
SKIPPED: Scanner was intentionally disabled or excluded from this scan
ERROR: Scanner encountered an execution error and could not complete successfully

Severity Thresholds (Thresh Column):

CRITICAL: Only Critical severity findings cause scanner to fail
HIGH: High and Critical severity findings cause scanner to fail
MEDIUM (MED): Medium, High, and Critical severity findings cause scanner to fail
LOW: Low, Medium, High, and Critical severity findings cause scanner to fail
ALL: Any finding of any severity level causes scanner to fail

Threshold Source: Values in parentheses indicate where the threshold is configured:

(g) = global: Set in the global_settings section of ASH configuration
(c) = config: Set in the individual scanner configuration section
(s) = scanner: Default threshold built into the scanner itself

Statistics calculation:

All statistics are calculated from the final aggregated SARIF report
Suppressed findings are counted separately and do not contribute to actionable findings
Scanner status is determined by comparing actionable findings to the threshold

Scanner	C	M	L	Time	Action	Result	Thresh
bandit	0	0	0	697ms	0	PASSED	MED (g)
cdk-nag	0	0	0	28.0s	0	PASSED	MED (g)
cfn-nag	0	0	0	31ms	0	PASSED	MED (g)
checkov	0	0	0	4.7s	0	PASSED	MED (g)
detect-secrets	0	0	0	658ms	0	PASSED	MED (g)
grype	6	9	12	35.3s	15	FAILED	MED (g)
npm-audit	0	0	0	190ms	0	PASSED	MED (g)
opengrep	0	0	0	<1ms	0	SKIPPED	MED (g)
semgrep	0	0	0	<1ms	0	MISSING	MED (g)
syft	0	0	0	2.2s	0	PASSED	MED (g)