fix(security): update dependencies [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
cryptography (changelog)	==46.0.6 → ==46.0.7
cryptography (changelog)	46.0.6 → 46.0.7
pip (changelog)	26.0.1 → 26.1
pytest (changelog)	9.0.2 → 9.0.3
uv (source, changelog)	0.10.10 → 0.11.6

---

Cryptography vulnerable to buffer overflow if non-contiguous buffers were passed to APIs

CVE-2026-39892 / GHSA-p423-j2cm-9vmq

More information

Details

If a non-contiguous buffer was passed to APIs which accepted Python buffers (e.g. Hash.update()), this could lead to buffer overflows. For example:

h = Hash(SHA256())
b.update(buf[::-1])

would read past the end of the buffer on Python >3.11

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-p423-j2cm-9vmq
• https://nvd.nist.gov/vuln/detail/CVE-2026-39892
• http://www.openwall.com/lists/oss-security/2026/04/08/12
• https://github.com/advisories/GHSA-p423-j2cm-9vmq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Cryptography vulnerable to buffer overflow if non-contiguous buffers were passed to APIs

CVE-2026-39892 / GHSA-p423-j2cm-9vmq

More information

Details

If a non-contiguous buffer was passed to APIs which accepted Python buffers (e.g. Hash.update()), this could lead to buffer overflows. For example:

h = Hash(SHA256())
b.update(buf[::-1])

would read past the end of the buffer on Python >3.11

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/pyca/cryptography/security/advisories/GHSA-p423-j2cm-9vmq
• https://nvd.nist.gov/vuln/detail/CVE-2026-39892
• https://github.com/pyca/cryptography
• http://www.openwall.com/lists/oss-security/2026/04/08/12

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

pip has an interpretation conflict due to handling both concatenated tar and ZIP files as ZIP files

CVE-2026-3219 / GHSA-58qw-9mgm-455v

More information

Details

pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.

Severity

• CVSS Score: 4.6 / 10 (Medium)
• Vector String: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-3219
• https://github.com/pypa/pip/pull/13870
• https://github.com/pypa/pip
• https://mail.python.org/archives/list/security-announce@python.org/thread/QAJ5JIVWWCAJ4EZL2FP5MOOW35JS7LRJ
• http://www.openwall.com/lists/oss-security/2026/04/20/8

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

pytest has vulnerable tmpdir handling

CVE-2025-71176 / GHSA-6w46-j5rx-g56g

More information

Details

pytest through 9.0.2 on UNIX relies on directories with the /tmp/pytest-of-{user} name pattern, which allows local users to cause a denial of service or possibly gain privileges.

Severity

• CVSS Score: 6.8 / 10 (Medium)
• Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

References

• https://nvd.nist.gov/vuln/detail/CVE-2025-71176
• https://github.com/pytest-dev/pytest/issues/13669
• https://www.openwall.com/lists/oss-security/2026/01/21/5
• https://github.com/pytest-dev/pytest/pull/14343
• https://github.com/pytest-dev/pytest/commit/95d8423bd24992deea5b9df32555fa1741679e2c
• https://github.com/pytest-dev/pytest/releases/tag/9.0.3
• https://github.com/advisories/GHSA-6w46-j5rx-g56g

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

pytest has vulnerable tmpdir handling

CVE-2025-71176 / GHSA-6w46-j5rx-g56g

More information

Details

pytest through 9.0.2 on UNIX relies on directories with the /tmp/pytest-of-{user} name pattern, which allows local users to cause a denial of service or possibly gain privileges.

Severity

• CVSS Score: 6.8 / 10 (Medium)
• Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

References

• https://nvd.nist.gov/vuln/detail/CVE-2025-71176
• https://github.com/pytest-dev/pytest/issues/13669
• https://github.com/pytest-dev/pytest/pull/14343
• https://github.com/pytest-dev/pytest/commit/95d8423bd24992deea5b9df32555fa1741679e2c
• https://github.com/pytest-dev/pytes
• https://github.com/pytest-dev/pytest/releases/tag/9.0.3
• https://www.openwall.com/lists/oss-security/2026/01/21/5

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

uv vulnerable to arbitrary file deletion through RECORD entries

GHSA-pjjw-68hj-v9mw

More information

Details

Impact

Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall.

uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall.

uv does not use the RECORD file to determine wheel file paths. Invalid RECORD entries cannot be used to create or modify files in arbitrary locations.

Standards-compliant Python packaging tooling does not produce RECORD files that exhibit this behavior; an attacker must manually manipulate the RECORD. A user must install and uninstall the malformed wheel to be affected. An attack must guess the depth of the installation prefix path in order to target system files.

Absolute paths in RECORD files are not allowed by the specification and, when present, uv always treats them as rooted in the wheel’s installation prefix. Absolute paths cannot be used to delete arbitrary files.

Only files can be deleted, attempts to delete a directory via an invalid RECORD entry will fail.

Patches

Versions 0.11.6 and newer of uv address the validation gap above, by removing invalid entries from RECORD files on wheel installation and ignoring RECORD paths that would escape the installation prefix on uninstall.

Workarounds

Users are advised to upgrade to 0.11.6 or newer to address this advisory.

Users should experience no breaking changes as a result of the patch above.

Severity

• CVSS Score: 2.1 / 10 (Low)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/astral-sh/uv/security/advisories/GHSA-pjjw-68hj-v9mw
• https://github.com/astral-sh/uv/pull/18942
• https://github.com/astral-sh/uv/pull/18943
• https://github.com/astral-sh/uv/commit/7983c7a5bef236fd8a04580fcedae7bd5bde4cdb
• https://github.com/astral-sh/uv/commit/a0e461ac44851f9a0f6e8974733e77d46f7a9ea9
• https://github.com/astral-sh/uv/releases/tag/0.11.6
• https://github.com/advisories/GHSA-pjjw-68hj-v9mw

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

uv vulnerable to arbitrary file deletion through RECORD entries

GHSA-pjjw-68hj-v9mw

More information

Details

Impact

Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall.

uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall.

uv does not use the RECORD file to determine wheel file paths. Invalid RECORD entries cannot be used to create or modify files in arbitrary locations.

Standards-compliant Python packaging tooling does not produce RECORD files that exhibit this behavior; an attacker must manually manipulate the RECORD. A user must install and uninstall the malformed wheel to be affected. An attack must guess the depth of the installation prefix path in order to target system files.

Absolute paths in RECORD files are not allowed by the specification and, when present, uv always treats them as rooted in the wheel’s installation prefix. Absolute paths cannot be used to delete arbitrary files.

Only files can be deleted, attempts to delete a directory via an invalid RECORD entry will fail.

Patches

Versions 0.11.6 and newer of uv address the validation gap above, by removing invalid entries from RECORD files on wheel installation and ignoring RECORD paths that would escape the installation prefix on uninstall.

Workarounds

Users are advised to upgrade to 0.11.6 or newer to address this advisory.

Users should experience no breaking changes as a result of the patch above.

Severity

• CVSS Score: 2.1 / 10 (Low)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/astral-sh/uv/security/advisories/GHSA-pjjw-68hj-v9mw
• https://github.com/astral-sh/uv/pull/18942
• https://github.com/astral-sh/uv/pull/18943
• https://github.com/astral-sh/uv/commit/7983c7a5bef236fd8a04580fcedae7bd5bde4cdb
• https://github.com/astral-sh/uv/commit/a0e461ac44851f9a0f6e8974733e77d46f7a9ea9
• https://github.com/astral-sh/uv
• https://github.com/astral-sh/uv/releases/tag/0.11.6

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

pyca/cryptography (cryptography)

v46.0.7

Compare Source

pypa/pip (pip)

v26.1

Compare Source

pytest-dev/pytest (pytest)

v9.0.3

Compare Source

pytest 9.0.3 (2026-04-07)

Bug fixes

• #​12444: Fixed pytest.approx which now correctly takes into account ~collections.abc.Mapping keys order to compare them.

• #​13634: Blocking a conftest.py file using the -p no: option is now explicitly disallowed.

  Previously this resulted in an internal assertion failure during plugin loading.

  Pytest now raises a clear UsageError explaining that conftest files are not plugins and cannot be disabled via -p.

• #​13734: Fixed crash when a test raises an exceptiongroup with __tracebackhide__ = True.

• #​14195: Fixed an issue where non-string messages passed to unittest.TestCase.subTest() were not printed.

• #​14343: Fixed use of insecure temporary directory (CVE-2025-71176).

Improved documentation

• #​13388: Clarified documentation for -p vs PYTEST_PLUGINS plugin loading and fixed an incorrect -p example.
• #​13731: Clarified that capture fixtures (e.g. capsys and capfd) take precedence over the -s / --capture=no command-line options in Accessing captured output from a test function <accessing-captured-output>.
• #​14088: Clarified that the default pytest_collection hook sets session.items before it calls pytest_collection_finish, not after.
• #​14255: TOML integer log levels must be quoted: Updating reference documentation.

Contributor-facing changes

• #​12689: The test reports are now published to Codecov from GitHub Actions.
  The test statistics is visible on the web interface.

  -- by aleguy02

astral-sh/uv (uv)

v0.11.6

Compare Source

Released on 2026-04-09.

Bug fixes

• Do not remove files outside the venv on uninstall (#​18942)
• Validate and heal wheel RECORD during installation (#​18943)
• Avoid uv cache clean errors due to Win32 path normalization (#​18856)

v0.11.5

Compare Source

Released on 2026-04-08.

Python

• Add CPython 3.13.13, 3.14.4, and 3.15.0a8 (#​18908)

Enhancements

• Fix build_system.requires error message (#​18911)
• Remove trailing path separators in path normalization (#​18915)
• Improve error messages for unsupported or invalid TLS certificates (#​18924)

Preview features

• Add exclude-newer to [[tool.uv.index]] (#​18839)
• uv audit: add context/warnings for ignored vulnerabilities (#​18905)

Bug fixes

• Normalize persisted fork markers before lock equality checks (#​18612)
• Clear junction properly when uninstalling Python versions on Windows (#​18815)
• Report error cleanly instead of panicking on TLS certificate error (#​18904)

Documentation

• Remove the legacy PIP_COMPATIBILITY.md redirect file (#​18928)
• Fix uv init example-bare --bare examples (#​18822, #​18925)

v0.11.4

Compare Source

Released on 2026-04-07.

Python

• Add CPython 3.13.13, 3.14.4, and 3.15.0a8 (#​18908)

Enhancements

• Add support for --upgrade-group (#​18266)
• Merge repeated archive URL hashes by version ID (#​18841)
• Require all direct URL hash algorithms to match (#​18842)

Bug fixes

• Avoid panics in environment finding via cycle detection (#​18828)
• Enforce direct URL hashes for pyproject.toml dependencies (#​18786)
• Error on --locked and --frozen when script lockfile is missing (#​18832)
• Fix uv export extra resolution for workspace member and conflicting extras (#​18888)
• Include conflicts defined in virtual workspace root (#​18886)
• Recompute relative exclude-newer values during uv tree --outdated (#​18899)
• Respect --exclude-newer in uv tool list --outdated (#​18861)
• Sort by comparator to break specifier ties (#​18850)
• Store relative timestamps in tool receipts (#​18901)
• Track newly-activated extras when determining conflicts (#​18852)
• Patch Cargo.lock in uv-build source distributions (#​18831)

Documentation

• Clarify that --exclude-newer compares artifact upload times (#​18830)

v0.11.3

Compare Source

Released on 2026-04-01.

Enhancements

• Add progress bar for hashing phase in uv publish (#​18752)
• Add support for ROCm 7.2 (#​18730)
• Emit abi3t tags for every abi3 version (#​18777)
• Expand uv workspace metadata with dependency information from the lock (#​18356)
• Implement support for PEP 803 (#​18767)
• Pretty-print platform in built wheel errors (#​18738)
• Publish installers to /installers/uv/latest on the mirror (#​18725)
• Show free-threaded Python in built-wheel errors (#​18740)

Preview features

• Add --ignore and --ignore-until-fixed to uv audit (#​18737)

Bug fixes

• Bump simple API cache (#​18797)
• Don't drop blake2b hashes (#​18794)
• Handle broken range request implementations (#​18780)
• Remove powerpc64-unknown-linux-gnu from release build targets (#​18800)
• Respect dependency metadata overrides in uv pip check (#​18742)
• Support debug CPython ABI tags in environment compatibility (#​18739)

Documentation

• Document false opt-out for exclude-newer-package (#​18768, #​18803)

v0.11.2

Compare Source

Released on 2026-03-26.

Enhancements

• Add a dedicated Windows PE editing error (#​18710)
• Make uv self update fetch the manifest from the mirror first (#​18679)
• Use uv reqwest client for self update (#​17982)
• Show uv self update success and failure messages with --quiet (#​18645)

Preview features

• Evaluate extras and groups when determining auditable packages (#​18511)

Bug fixes

• Skip redundant project configuration parsing for uv run (#​17890)

v0.11.1

Compare Source

Released on 2026-03-24.

Bug fixes

• Add missing hash verification for riscv64gc-unknown-linux-musl (#​18686)
• Fallback to direct download when direct URL streaming is unsupported (#​18688)
• Revert treating 'Dynamic' values as case-insensitive (#​18692)
• Remove torchdata from list of packages to source from the PyTorch index (#​18703)
• Special-case == Python version request ranges (#​9697)

Documentation

• Cover --python <dir> in "Using arbitrary Python environments" (#​6457)
• Fix version annotations for PS_MODULE_PATH and UV_WORKING_DIR (#​18691)

v0.11.0

Compare Source

Released on 2026-03-23.

Breaking changes

This release includes changes to the networking stack used by uv. While we think that breakage will be rare, it is possible that these changes will result in the rejection of certificates previously trusted by uv so we have marked the change as breaking out of an abundance of caution.

The changes are largely driven by the upgrade of reqwest, which powers uv's HTTP clients, to v0.13 which included some breaking changes to TLS certificate verification.

The following changes are included:

• rustls-platform-verifier is used instead of rustls-native-certs and webpki for certificate verification

  This change should have no effect unless you are using the native-tls option to enable reading system certificates.

  rustls-platform-verifier delegates to the system for certificate validation (e.g., Security.framework on macOS) instead of eagerly loading certificates from the system and verifying them via webpki. The effects of this change will vary based on the operating system. In general, uv's certificate validation should now be more consistent with browsers and other native applications. However, this is the most likely cause of breaking changes in this release. Some previously failing certificate chains may succeed, and some previously accepted certificate chains may fail. In either case, we expect the validation to be more correct and welcome reports of regressions.

  In particular, because more responsibility for validating the certificate is transferred to your system's security library, some features like CA constraints or revocation of certificates via OCSP and CRLs may now be used.

  This change should improve performance when using system certificate on macOS, as uv no longer needs to load all certificates from the keychain at startup.

• aws-lc is used instead of ring for a cryptography backend

  There should not be breaking changes from this change. We expect this to expand support for certificate signature algorithms.

• --native-tls is deprecated in favor of a new --system-certs flag

  The --native-tls flag is still usable and has identical behavior to --system-certs.

  This change was made to reduce confusion about the TLS implementation uv uses. uv always uses rustls not native-tls.

• Building uv on x86-64 and i686 Windows requires NASM

  NASM is required by aws-lc. If not found on the system, a prebuilt blob provided by aws-lc-sys will be used.

  If you are not building uv from source, this change has no effect.

  See the CONTRIBUTING guide for details.

• Empty SSL_CERT_FILE values are ignored (for consistency with SSL_CERT_DIR)

See #​18550 for details.

Python

• Enable frame pointers for improved profiling on Linux x86-64 and aarch64

See the python-build-standalone release notes for details.

Enhancements

• Treat 'Dynamic' values as case-insensitive (#​18669)
• Use a dedicated error for invalid cache control headers (#​18657)
• Enable checksum verification in the generated installer script (#​18625)

Preview features

• Add --service-format and --service-url to uv audit (#​18571)

Performance

• Avoid holding flat index lock across indexes (#​18659)

Bug fixes

• Find the dynamic linker on the file system when sniffing binaries fails (#​18457)
• Fix export of conflicting workspace members with dependencies (#​18666)
• Respect installed settings in uv tool list --outdated (#​18586)
• Treat paths originating as PEP 508 URLs which contain expanded variables as relative (#​18680)
• Fix uv export for workspace member packages with conflicts (#​18635)
• Continue to alternative authentication providers when the pyx store has no token (#​18425)
• Use redacted URLs for log messages in cached client (#​18599)

Documentation

• Add details on Linux versions to the platform policy (#​18574)
• Clarify FLASH_ATTENTION_SKIP_CUDA_BUILD guidance for flash-attn installs (#​18473)
• Split the dependency bots page into two separate pages (#​18597)
• Split the alternative indexes page into separate pages (#​18607)

v0.10.12

Compare Source

Released on 2026-03-19.

Python

• Add pypy 3.11.15 (#​18468)
• Add support for using Python 3.6 interpreters (#​18454)

Enhancements

• Include uv's target triple in version report (#​18520)
• Allow comma separated values in --no-emit-package (#​18565)

Preview features

• Show uv audit in the CLI help (#​18540)

Bug fixes

• Improve reporting of managed interpreter symlinks in uv python list (#​18459)
• Preserve end-of-line comments on previous entries when removing dependencies (#​18557)
• Treat abi3 wheel Python version as a lower bound (#​18536)
• Detect hard-float support on aarch64 kernels running armv7 userspace (#​18530)

Documentation

• Add Python 3.15 to supported versions (#​18552)
• Adjust the PyPy note (#​18548)
• Move Pyodide to Tier 2 in the Python support policy (#​18561)
• Move Rust and Python version support out of the Platform support policy (#​18535)
• Update Docker guide with changes from uv-docker-example (#​18558)
• Update the Python version policy (#​18559)

v0.10.11

Compare Source

Released on 2026-03-16.

Enhancements

• Fetch Ruff release metadata from an Astral mirror (#​18358)
• Use PEP 639 license metadata for uv itself (#​16477)

Performance

• Improve distribution id performance (#​18486)

Bug fixes

• Allow --project to refer to a pyproject.toml directly and reduce to a warning on other files (#​18513)
• Disable SYSTEM_VERSION_COMPAT when querying interpreters on macOS (#​18452)
• Enforce available distributions for supported environments (#​18451)
• Fix uv sync --active recreating active environments when UV_PYTHON_INSTALL_DIR is relative (#​18398)

Documentation

• Add missing -o requirements.txt in uv pip compile example (#​12308)
• Link to organization security policy (#​18449)
• Link to the AI policy in the contributing guide (#​18448)

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • "before 4am"
• Automerge
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.