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
FEDORA-2025-6c78aad721 (mingw-libsoup-2.74.3-14.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-6c78aad721
FEDORA-2025-5a82449616 (mingw-libsoup-2.74.3-14.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-5a82449616
FEDORA-2025-5a82449616 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-5a82449616` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5a82449616 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-6c78aad721 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6c78aad721` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6c78aad721 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-5a82449616 (mingw-libsoup-2.74.3-14.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-6c78aad721 (mingw-libsoup-2.74.3-14.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.