More information about this security flaw is available in the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=2328554 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.
I was able to reproduce this in uv 0.5.2 and earlier. It appears to be fixed or mitigated in uv 0.5.3 and later. I have asked upstream to comment on whether they believe the issue is entirely dealt with, or whether there is further work to be done, in “Please comment on CVE-2024-53899 and virtualenv activation scripts,” https://github.com/astral-sh/uv/issues/9424. In any case, uv 0.4.30 as currently shipped in Fedora 41 *is* affected by this issue. I will investigate whether a mitigation can be backported, or whether it makes sense to quickly ship an update to 0.5.3 or later to stable releases instead.
FEDORA-2024-8568f9cd5e (uv-0.5.4-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-8568f9cd5e
FEDORA-2024-8568f9cd5e has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-8568f9cd5e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8568f9cd5e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-8568f9cd5e (uv-0.5.5-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.