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