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.
See https://www.cve.org/CVERecord?id=CVE-2026-32766. This is fixed in astral-tokio-tar 0.6.0, https://src.fedoraproject.org/rpms/rust-astral-tokio-tar/pull-request/3, which must be shipped together with uv 0.10.12 (released yesterday). I expect to be able to make updates for the EPEL10 leading branch within the next few days, possibly as soon as today. I do *not* plan to fix this in EPEL10.2 and EPEL10.1 release branches, because (unlike in Fedora stable branches) there is no blanket Update Policy exception for updating Rust crate libraries across SemVer boundaries, and it’s not worth the time and effort I would have to invest in petitioning for an individual exception to cover this case.
FEDORA-EPEL-2026-ea6f432357 (maturin-1.9.6-4.el10_3, rust-astral-tokio-tar-0.6.0-1.el10_3, and 3 more) has been submitted as an update to Fedora EPEL 10.3. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-ea6f432357
FEDORA-EPEL-2026-ea6f432357 has been pushed to the Fedora EPEL 10.3 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-ea6f432357 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.