More information about this security flaw is available in the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=2295203 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.
FEDORA-2024-0ba1c1a435 (yt-dlp-2024.07.02-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-0ba1c1a435
FEDORA-2024-a4392c5143 (yt-dlp-2024.07.02-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-a4392c5143
https://bodhi.fedoraproject.org/updates/FEDORA-2024-bf00848f44 https://bodhi.fedoraproject.org/updates/FEDORA-2024-0ba1c1a435 https://bodhi.fedoraproject.org/updates/FEDORA-2024-a4392c5143
FEDORA-2024-0ba1c1a435 (yt-dlp-2024.07.02-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-c07c365ba7 has been pushed to the Fedora 39 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-c07c365ba7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c07c365ba7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-72fb215fcd has been pushed to the Fedora 39 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-72fb215fcd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-72fb215fcd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-72fb215fcd (yt-dlp-2024.07.09-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.