Access of Resource Using Incompatible Type ('Type Confusion') Affecting py3.13-uv-build-bin package, versions <0.11.0-r0


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.4% (32nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-PY313UVBUILDBIN-15793281
  • published27 Mar 2026
  • disclosed20 Mar 2026

Introduced: 20 Mar 2026

CVE-2026-33055  (opens in a new tab)
CWE-843  (opens in a new tab)

How to fix?

Upgrade Minimos:latest py3.13-uv-build-bin to version 0.11.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream py3.13-uv-build-bin package and not the py3.13-uv-build-bin package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue. Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size - other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers. This issue has been fixed in version 0.4.45.

CVSS Base Scores

version 3.1