Interpretation Conflict Affecting python313-uv package, versions <0.7.18-160000.5.1


Severity

Recommended
medium

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.31% (23rd 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-SLES1600-PYTHON313UV-17253985
  • published9 Jun 2026
  • disclosed1 Jun 2026

Introduced: 1 Jun 2026

CVE-2026-32766  (opens in a new tab)
CWE-436  (opens in a new tab)

How to fix?

Upgrade SLES:16.0.0 python313-uv to version 0.7.18-160000.5.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python313-uv package and not the python313-uv package as distributed by SLES. See How to fix? for SLES:16.0.0 relevant fixed versions and status.

astral-tokio-tar is a tar archive reading/writing library for async Rust. In versions 0.5.6 and earlier, malformed PAX extensions were silently skipped when parsing tar archives. This silent skipping (rather than rejection) of invalid PAX extensions could be used as a building block for a parser differential, for example by silently skipping a malformed GNU “long link” extension so that a subsequent parser would misinterpret the extension. In practice, exploiting this behavior in astral-tokio-tar requires a secondary misbehaving tar parser, i.e. one that insufficiently validates malformed PAX extensions and interprets them rather than skipping or erroring on them. This vulnerability is considered low-severity as it requires a separate vulnerability against any unrelated tar parser. This issue has been fixed in version 0.6.0.

CVSS Base Scores

version 3.1