Wireshark 5.0.0 release candidate marks first major version in four years

The Wireshark project has published 5.0.0rc1, the first release candidate for its next major version. This marks the first major version increment since Wireshark 4.0 arrived in 2022, signaling substantial accumulated changes to the widely deployed open-source packet analyzer. Release candidates typically precede final releases by weeks, giving distribution packagers, security researchers, and network administrators time to validate the build against their workflows.

Wireshark serves as the de facto standard tool for network troubleshooting, protocol development, and security analysis across Linux, BSD, macOS, and Windows environments. A major version release generally carries backward-compatibility considerations for capture file formats, display filter syntax, scripting interfaces, and plugin APIs that downstream tools and automated workflows depend upon.

What to expect in Wireshark 5.0.0

• Release cadence: This is the first release candidate (rc1) in the 5.0.0 series, indicating the feature freeze phase has begun and final stabilization is underway.
• Version significance: The jump from 4.x to 5.0.0 represents the first major version increase in approximately four years, following Wireshark 4.0.0's release in 2022.
• Testing window: Release candidates are published specifically to allow downstream testing by distribution maintainers, enterprise security teams, and tool integrators before the final release.
• Scope unknown: The source does not enumerate specific feature additions, API changes, or protocol dissector updates included in this major version bump.

Why it matters

Wireshark's major releases affect every Linux distribution that ships the tool in default repositories, as well as security operations centers and network engineering teams who depend on stable display filter behavior and capture file compatibility. Distribution packagers should begin build testing against their toolchain configurations now, as major version transitions often introduce build system changes or deprecated dependencies that require packaging adjustments before the final release.