Skip to content

Accept pip's vendored urllib3 2.7.0 advisories in the container scan - #33

Merged
crentb merged 1 commit into
mainfrom
fix/trivyignore-urllib3
Oct 7, 2026
Merged

crentb merged 1 commit into
mainfrom
fix/trivyignore-urllib3

Conversation

@crentb

@crentb crentb commented Oct 7, 2026

Copy link
Copy Markdown
Owner

The container scan has failed since the 2026-10-05 scheduled run on two HIGH advisories in urllib3 2.7.0: CVE-2026-97687 (GHSA-8988-9cw3-xx77) and CVE-2026-97689 (GHSA-vxq7-64xx-v4gw), both fixed in 2.8.0.

The flagged copy is pip's own vendored urllib3, not a project dependency. pip 26.2.1, the newest pip, still pins urllib3==2.7.0 in pip/_vendor/vendor.txt, and trivy sees it through pip's in-image SBOM, exactly like the msgpack and setuptools entries already in .trivyignore. Nothing in the image imports it, and pip runs only while the image is built.

This adds both IDs to .trivyignore with that justification. Remove them once a pip release vendors urllib3 2.8.0 or later.

- The container scan has failed since 2026-10-05 on urllib3 2.7.0
  (CVE-2026-97687 / GHSA-8988-9cw3-xx77 and CVE-2026-97689 /
  GHSA-vxq7-64xx-v4gw, both HIGH, fixed in 2.8.0).
- The flagged copy is pip's own vendored urllib3, surfaced through pip's
  in-image SBOM like the msgpack and setuptools entries already listed:
  pip 26.2.1, the newest pip, still pins urllib3==2.7.0. Nothing in the
  image imports it, and pip runs only while the image is built.
- Remove both entries once a pip release vendors urllib3 2.8.0 or later.
@crentb
crentb merged commit 8266a5a into main Oct 7, 2026
7 checks passed
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.

1 participant