Bug 2397715 - CVE-2025-59825 uv: astral-tokio-tar path traversal [epel-10]
Summary: CVE-2025-59825 uv: astral-tokio-tar path traversal [epel-10]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: uv
Version: epel10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Ben Beasley
QA Contact:
URL:
Whiteboard: {"flaws": ["bfb2f8d2-b201-483b-b061-0...
Depends On:
Blocks: CVE-2025-59825
TreeView+ depends on / blocked
 
Reported: 2025-09-23 21:57 UTC by Jon Moroney
Modified: 2025-10-03 00:45 UTC (History)
4 users (show)

Fixed In Version: uv-0.8.11-4.el10_2 uv-0.8.11-4.el10_1 uv-0.6.17-2.el10_0
Clone Of:
Environment:
Last Closed: 2025-10-03 00:29:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jon Moroney 2025-09-23 21:57:28 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams

Comment 1 Fedora Update System 2025-09-24 08:41:58 UTC
FEDORA-EPEL-2025-37d065cdf4 (rust-astral-tokio-tar-0.5.5-1.el10_2 and uv-0.8.11-4.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-37d065cdf4

Comment 2 Fedora Update System 2025-09-24 08:42:28 UTC
FEDORA-EPEL-2025-9b9bfff5fa (rust-astral-tokio-tar-0.5.5-1.el10_1 and uv-0.8.11-4.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-9b9bfff5fa

Comment 3 Fedora Update System 2025-09-24 13:00:36 UTC
FEDORA-EPEL-2025-04455338f9 (rust-astral-tokio-tar-0.5.5-1.el10_0, rust-flate2-1.1.2-1.el10_0, and 2 more) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-04455338f9

Comment 4 Fedora Update System 2025-09-25 01:18:00 UTC
FEDORA-EPEL-2025-37d065cdf4 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-37d065cdf4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2025-09-25 01:41:43 UTC
FEDORA-EPEL-2025-9b9bfff5fa has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-9b9bfff5fa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2025-09-25 01:46:19 UTC
FEDORA-EPEL-2025-04455338f9 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-04455338f9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2025-10-03 00:29:00 UTC
FEDORA-EPEL-2025-37d065cdf4 (rust-astral-tokio-tar-0.5.5-1.el10_2 and uv-0.8.11-4.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-10-03 00:37:35 UTC
FEDORA-EPEL-2025-9b9bfff5fa (rust-astral-tokio-tar-0.5.5-1.el10_1 and uv-0.8.11-4.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-10-03 00:45:54 UTC
FEDORA-EPEL-2025-04455338f9 (rust-astral-tokio-tar-0.5.5-1.el10_0, rust-flate2-1.1.2-1.el10_0, and 2 more) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.