Wireshark-dev: [Wireshark-dev] Wireshark 4.4.6 is now available

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 16 Apr 2025 11:09:07 -0700
I'm proud to announce the release of Wireshark 4.4.6.


 What is Wireshark?

  Wireshark is the world’s most popular network protocol analyzer. It is
  used for troubleshooting, analysis, development and education.

  Wireshark is hosted by the Wireshark Foundation, a nonprofit which
  promotes protocol analysis education. Wireshark and the foundation
  depend on your contributions in order to do their work! If you or your
  organization would like to contribute or become a sponsor, please
  visit wiresharkfoundation.org[1].

 What’s New

  Bug Fixes

   The following bugs have been fixed:

     • Bug in EtherCAT dissector with ECS order. Issue 13718[2].

     • Conversation dialog columns return to default width on each new
       packet in live capture. Issue 15978[3].

     • Tests fail in LTO-enabled builds in Ubuntu/Debian. Issue
       18216[4].

     • Incorrect conditions in BFCP dissector. Issue 18717[5].

     • Static build fails on Ubuntu 24.04 because the c-ares library
       isn’t found. Issue 20343[6].

     • Flutter’s Image Picker Generated JPEG Files Detected as Malformed
       Packet. Issue 20355[7].

     • QUIC dissector breaks when src and dst change. Issue 20371[8].

     • s390x: build fail on Ubuntu PPA nighty build. Issue 20372[9].

     • Trailing octet after IPv4 packet end is not detected or displayed
       in raw bytes. Issue 20423[10].

     • [packet-ax25-nol3.c] Only call APRS dissector on UI Frames. Issue
       20429[11].

     • Wireshark hangs when refreshing interfaces with the debug console
       preference set to "always" and a file open (Windows) Issue
       20434[12].

     • BGP EVPN - Type-8 route not correctly read after addition of Max.
       Response Time field. Issue 20459[13].

     • Wireshark does not correctly decode LIN "go to sleep" in TECMP
       and CMP. Issue 20463[14].

     • MQTT-SN: WILLTOPIC message not decoded correctly (missing some
       flags) Issue 20476[15].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   ADB, ASAM CMP, AX.25, BACapp, BFCP, BGP, CP2179, DCERPC WKSSVC,
   DCT2000, DECT-NWK, DHCP, DOF, EAPOL-MKA, ECAT, ErlDP, Ethertype,
   F1AP, GSM BSSMAP, GSM DTAP, HomePlug AV, ICMP, IEEE 802.11, ITS, LDP,
   MQTT-SN, NAS-EPS, NR RRC, OER, PCEP, PNIO, PPP, QUAKE, QUIC, Raw,
   Signal PDU, TCP, TECMP, TLS, and USB DFU

  New and Updated Capture File Support

   3GPP and pcapng

  Updated File Format Decoding Support

   There is no updated file format support in this release.

 Prior Versions

  Wireshark 4.4.5 included the following changes. See the release
  notes[16] for details:

    • GRPC: protobuf_json only displays the truncated string value.
      Issue 20392[17].

    • Wireshark crashes when clicking on a column title/header. Issue
      20403[18].

  Wireshark 4.4.4 included the following changes. See the release
  notes[19] for details:

    • wnpa-sec-2025-01[20] Bundle Protocol and CBOR dissector
      {crash,infinite loop,memory leak}. Issue 20373[21].

    • Crash when sorting columns during capture with display filter
      active. Issue 20263[22].

    • OSS-Fuzz 384757274: Invalid-bool-value in dissect_tcp. Issue
      20300[23].

    • Test failure in 4.4.2/4.4.3: test_sharkd_req_follow_http2. Issue
      20330[24].

    • Regression in extcap interface toolbar. Issue 20354[25].

    • Clicking outside columns in TCP tab of Statistics → Conversations
      window causes crash. Issue 20357[26].

    • FTBFS with Ubuntu development (25.04) release. Issue 20359[27].

    • DNS enable_qname_stats crash Wireshark when QDCOUNT == 0. Issue
      20367[28].

    • Windows: Android extcap plugin fails with "Broken socket
      connection" if there are no new packets for 2sec. Issue 20386[29].

    • TECMP: Calculation of lifecycle start in Status message is wrong.
      Issue 20387[30].

    • MQTT v5.0 properties total length presentation is incorrect. Issue
      20389[31].

    • TShark doesn’t resolve addresses in custom "hosts" files. Issue
      20391[32].

    • Incorrect JA4 fingerprint with empty ciphers. Issue 20394[33].

  Wireshark 4.4.3 included the following changes. See the release
  notes[34] for details:

    • Potential mis-match in GSM MAP dissector for uncertainty radius
      and its filter key. Issue 20247[35].

    • Macro eNodeB ID and Extended Macro eNodeB ID not decoded by User
      Location Information. Issue 20276[36].

    • The NFSv2 Dissector appears to be swapping Character Special File
      and Directory in mode decoding. Issue 20290[37].

    • CMake discovers Strawberry Perl’s zlib DLL when it shouldn’t.
      Issue 20304[38].

    • VOIP Calls call flow displaying hours. Issue 20311[39].

    • Fuzz job issue: fuzz-2024-12-26-7898.pcap. Issue 20313[40].

    • sFlow: Incorrect length passed to header sample dissector. Issue
      20320[41].

    • wsutil: Should link against -lm due to missing fabs() when built
      with -fno-builtin. Issue 20326[42].

  Wireshark 4.4.2 included the following changes. See the release
  notes[43] for details:

    • wnpa-sec-2024-14[44] FiveCo RAP dissector infinite loop. Issue
      20176[45].

    • wnpa-sec-2024-15[46] ECMP dissector crash. Issue 20214[47].

    • CIP I/O is not detected by "enip" filter anymore. Issue 19517[48].

    • Fuzz job issue: fuzz-2024-09-03-7550.pcap. Issue 20041[49].

    • OSS-Fuzz 71476: wireshark:fuzzshark_ip_proto-udp:
      Index-out-of-bounds in DOFObjectID_Create_Unmarshal. Issue
      20065[50].

    • JA4_c hashes an empty field to e3b0c44298fc when it should be
      000000000000. Issue 20066[51].

    • Opening Wireshark 4.4.0 on macOS 15.0 disconnects iPhone
      Mirroring. Issue 20082[52].

    • PTP analysis loses track of message associations in case of
      sequence number resets. Issue 20099[53].

    • USB CCID: response packet in case SetParameters command is
      unsupported is flagged as malformed. Issue 20107[54].

    • dumpcap crashes when run from TShark with a capture filter. Issue
      20108[55].

    • SRT dissector: The StreamID (SID) in the handshake extension is
      displayed without regarding the control characters and with NUL as
      terminating. Issue 20113[56].

    • Ghost error message on POP3 packets. Issue 20124[57].

    • Building against c-ares 1.34 fails. Issue 20125[58].

    • D-Bus is not optional anymore. Issue 20126[59].

    • macOS Intel DMGs aren’t fully notarized. Issue 20129[60].

    • Incorrect name for MLD Capabilities and Operations Present flag in
      dissection of MLD Capabilities for MLO wifi-7 capture. Issue
      20134[61].

    • CQL Malformed Packet v4 S → C Type RESULT: Prepared[Malformed
      Packet] Issue 20142[62].

    • Wi-Fi: 256 Block Ack (BA) is not parsed properly. Issue 20156[63].

    • BACnet ReadPropertyMultiple request Maximum allowed recursion
      depth reached. Issue 20159[64].

    • Statistics→I/O Graph crashes when using simple moving average.
      Issue 20163[65].

    • HTTP2 body decompression fails on DATA with a single padded frame.
      Issue 20167[66].

    • Compiler warning for ui/tap-rtp-common.c (ignoring return value)
      Issue 20169[67].

    • SIP dissector bug due to "be-route" param in VIA header. Issue
      20173[68].

    • Coredump after trying to open 'Follow TCP stream' Issue 20174[69].

    • Protobuf JSON mapping error. Issue 20182[70].

    • Display filter "!stp.pvst.origvlan in { vlan.id }" causes a crash
      (Version 4.4.1) Issue 20183[71].

    • Extcap plugins shipped with Wireshark Portable are not found in
      version 4.4.1. Issue 20184[72].

    • IEEE 802.11be: Wrong regulatory info in HE Operation IE in Beacon
      frame. Issue 20187[73].

    • Wireshark 4.4.1 does not decode RTCP packets. Issue 20188[74].

    • Qt: Display filter sub-menu can only be opened on the triangle,
      not the full name. Issue 20190[75].

    • Qt: Changing the display filter does not update the Conversations
      or Endpoints dialogs. Issue 20191[76].

    • MODBUS Dissector bug. Issue 20192[77].

    • Modbus dissector bug - Field Occurence and Layer Operator
      modbus.bitval field. Issue 20193[78].

    • Wireshark crashes when a field is dragged from packet details
      towards the find input. Issue 20204[79].

    • Lua DissectorTable("") : set ("10,11") unexpected behavior in
      locales with comma as decimal separator. Issue 20216[80].

  The TCP dissector no longer falls back to using the client port as a
  criterion for selecting a payload dissector when the server port does
  not select a payload dissector (except for port 20, active FTP). This
  behavior can be changed using the "Client port dissectors" preference.

  Display filters now correctly handle floating point conversion errors.

  The Lua API now has better support for comma-separated ranges in
  different locales.

  Wireshark 4.4.1 included the following changes. See the release
  notes[81] for details:

    • wnpa-sec-2024-12[82] ITS dissector crash. Issue 20026[83].

    • wnpa-sec-2024-13[84] AppleTalk and RELOAD Framing dissector
      crashes. Issue 20114[85].

    • Refresh interface during live-capture leads to corrupt interface
      handling. Issue 11176[86].

    • Media type "application/octet-stream" registered for both Thread
      and UASIP. Issue 14729[87].

    • Extcap toolbar stops working when new interface is added. Issue
      19854[88].

    • Decoding error ITS CPM version 2.1.1. Issue 19886[89].

    • Build error in 4.3.0: sync_pipe_run_command_actual error: argument
      2 is null but the corresponding size argument 3 value is 512004
      [-Werror=nonnull] Issue 19930[90].

    • html2text.py doesn’t handle the `<sup>` tag. Issue 20020[91].

    • Incorrect NetFlow v8 TOS AS aggregation dissection. Issue
      20021[92].

    • The Windows packages don’t ship with the IP address plugin. Issue
      20030[93].

    • O_PATH is Linux-and-FreeBSD-specific. Issue 20031[94].

    • Wireshark 4.4.0 doesn’t install USBcap USBcapCMD.exe in the
      correct directory. Issue 20040[95].

    • OER dissector is not considering the preamble if ASN.1 SEQUENCE
      definition includes extension marker but no OPTIONAL items. Issue
      20044[96].

    • Bluetooth classic L2CAP incorrect dissection with connectionless
      reception channel. Issue 20047[97].

    • Profile auto switch filters : Grayed Display Filter Expression
      dialog box when opened from Configuration Profiles dialog box.
      Issue 20049[98].

    • Wireshark 4.4.0 / macOS 14.6.1 wifi if monitor mode. Issue
      20051[99].

    • TECMP Data Type passes too much data to sub dissectors. Issue
      20052[100].

    • Wireshark and tshark 4.4.0 ignore extcap options specified on the
      command line. Issue 20054[101].

    • Cannot open release notes due to incorrect path with duplicated
      directory components. Issue 20055[102].

    • Unable to open "Release Notes" from the "Help" menu. Issue
      20056[103].

    • No capture interfaces if Wireshark is started from command line
      with certain paths. Issue 20057[104].

    • Wireshark 4.4.0 extcap path change breaks third party extcap
      installers. Issue 20069[105].

    • Fuzz job UTF-8 encoding issue: fuzz-2024-09-10-7618.pcap. Issue
      20071[106].

    • Unable to create larger files than 99 size units. Issue
      20079[107].

    • Opening Wireshark 4.4.0 on macOS 15.0 disconnects iPhone
      Mirroring. Issue 20082[108].

    • PRP trailer not shown for L2 IEC 61850 GOOSE packets in 4.4.0 (was
      working in 4.2.7) Issue 20088[109].

    • GUI lags because NetworkManager keeps turning 802.11 monitor mode
      off. Issue 20090[110].

    • Error while getting Bluetooth application process id by <shell:ps
      -A | grep com.*android.bluetooth> Issue 20100[111].

    • Fuzz job assertion: randpkt-2024-10-05-7200.pcap. Issue
      20110[112].

  Wireshark 4.4.0 included the following changes. See the release
  notes[113] for details:

  Many improvements and fixes to the graphing dialogs, including I/O
  Graphs, Flow Graph / VoIP Calls, and TCP Stream Graphs.

  Wireshark now supports automatic profile switching. You can associate
  a display filter with a configuration profile, and when you open a
  capture file that matches the filter, Wireshark will automatically
  switch to that profile.

  Support for Lua 5.3 and 5.4 has been added, and support for Lua 5.1
  and 5.2 has been removed. The Windows and macOS installers now ship
  with Lua 5.4.6.

  Improved display filter support for value strings (optional string
  representations for numeric fields).

  Display filter functions can be implemented as plugins, similar to
  protocol dissectors and file parsers.

  Display filters can be translated to pcap filters using "Edit › Copy ›
  Display filter as pcap filter" if each display filter field has a
  corresponding pcap filter equivalent.

  Custom columns can be defined using any valid field expression, such
  as display filter functions, packet slices, arithmetic calculations,
  logical tests, raw byte addressing, and protocol layer modifiers.

  Custom output fields for `tshark -e` can also be defined using any
  valid field expression.

  Wireshark can be built with the zlib-ng instead of zlib for compressed
  file support. Zlib-ng is substantially faster than zlib. The official
  Windows and macOS packages include this feature.

 Getting Wireshark

  Wireshark source code and installation packages are available from
  https://www.wireshark.org/download.html.

  Vendor-supplied Packages

   Most Linux and Unix vendors supply their own Wireshark packages. You
   can usually install or upgrade Wireshark using the package management
   system specific to that platform. A list of third-party packages can
   be found on the download page[114] on the Wireshark web site.

 File Locations

  Wireshark and TShark look in several different locations for
  preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These
  locations vary from platform to platform. You can use "Help › About
  Wireshark › Folders" or `tshark -G folders` to find the default
  locations on your system.

 Getting Help

  The User’s Guide, manual pages and various other documentation can be
  found at https://www.wireshark.org/docs/

  Community support is available on Wireshark’s Q&A site[115] and on the
  wireshark-users mailing list. Subscription information and archives
  for all of Wireshark’s mailing lists can be found on the mailing list
  site[116].

  Bugs and feature requests can be reported on the issue tracker[117].

  You can learn protocol analysis and meet Wireshark’s developers at
  SharkFest[118].

 How You Can Help

  The Wireshark Foundation helps as many people as possible understand
  their networks as much as possible. You can find out more and donate
  at wiresharkfoundation.org[119].

 Frequently Asked Questions

  A complete FAQ is available on the Wireshark web site[120].

 References

   1. https://wiresharkfoundation.org
   2. https://gitlab.com/wireshark/wireshark/-/issues/13718
   3. https://gitlab.com/wireshark/wireshark/-/issues/15978
   4. https://gitlab.com/wireshark/wireshark/-/issues/18216
   5. https://gitlab.com/wireshark/wireshark/-/issues/18717
   6. https://gitlab.com/wireshark/wireshark/-/issues/20343
   7. https://gitlab.com/wireshark/wireshark/-/issues/20355
   8. https://gitlab.com/wireshark/wireshark/-/issues/20371
   9. https://gitlab.com/wireshark/wireshark/-/issues/20372
  10. https://gitlab.com/wireshark/wireshark/-/issues/20423
  11. https://gitlab.com/wireshark/wireshark/-/issues/20429
  12. https://gitlab.com/wireshark/wireshark/-/issues/20434
  13. https://gitlab.com/wireshark/wireshark/-/issues/20459
  14. https://gitlab.com/wireshark/wireshark/-/issues/20463
  15. https://gitlab.com/wireshark/wireshark/-/issues/20476
  16. https://www.wireshark.org/docs/relnotes/wireshark-4.4.5.html
  17. https://gitlab.com/wireshark/wireshark/-/issues/20392
  18. https://gitlab.com/wireshark/wireshark/-/issues/20403
  19. https://www.wireshark.org/docs/relnotes/wireshark-4.4.4.html
  20. https://www.wireshark.org/security/wnpa-sec-2025-01
  21. https://gitlab.com/wireshark/wireshark/-/issues/20373
  22. https://gitlab.com/wireshark/wireshark/-/issues/20263
  23. https://gitlab.com/wireshark/wireshark/-/issues/20300
  24. https://gitlab.com/wireshark/wireshark/-/issues/20330
  25. https://gitlab.com/wireshark/wireshark/-/issues/20354
  26. https://gitlab.com/wireshark/wireshark/-/issues/20357
  27. https://gitlab.com/wireshark/wireshark/-/issues/20359
  28. https://gitlab.com/wireshark/wireshark/-/issues/20367
  29. https://gitlab.com/wireshark/wireshark/-/issues/20386
  30. https://gitlab.com/wireshark/wireshark/-/issues/20387
  31. https://gitlab.com/wireshark/wireshark/-/issues/20389
  32. https://gitlab.com/wireshark/wireshark/-/issues/20391
  33. https://gitlab.com/wireshark/wireshark/-/issues/20394
  34. https://www.wireshark.org/docs/relnotes/wireshark-4.4.3.html
  35. https://gitlab.com/wireshark/wireshark/-/issues/20247
  36. https://gitlab.com/wireshark/wireshark/-/issues/20276
  37. https://gitlab.com/wireshark/wireshark/-/issues/20290
  38. https://gitlab.com/wireshark/wireshark/-/issues/20304
  39. https://gitlab.com/wireshark/wireshark/-/issues/20311
  40. https://gitlab.com/wireshark/wireshark/-/issues/20313
  41. https://gitlab.com/wireshark/wireshark/-/issues/20320
  42. https://gitlab.com/wireshark/wireshark/-/issues/20326
  43. https://www.wireshark.org/docs/relnotes/wireshark-4.4.2.html
  44. https://www.wireshark.org/security/wnpa-sec-2024-14
  45. https://gitlab.com/wireshark/wireshark/-/issues/20176
  46. https://www.wireshark.org/security/wnpa-sec-2024-15
  47. https://gitlab.com/wireshark/wireshark/-/issues/20214
  48. https://gitlab.com/wireshark/wireshark/-/issues/19517
  49. https://gitlab.com/wireshark/wireshark/-/issues/20041
  50. https://gitlab.com/wireshark/wireshark/-/issues/20065
  51. https://gitlab.com/wireshark/wireshark/-/issues/20066
  52. https://gitlab.com/wireshark/wireshark/-/issues/20082
  53. https://gitlab.com/wireshark/wireshark/-/issues/20099
  54. https://gitlab.com/wireshark/wireshark/-/issues/20107
  55. https://gitlab.com/wireshark/wireshark/-/issues/20108
  56. https://gitlab.com/wireshark/wireshark/-/issues/20113
  57. https://gitlab.com/wireshark/wireshark/-/issues/20124
  58. https://gitlab.com/wireshark/wireshark/-/issues/20125
  59. https://gitlab.com/wireshark/wireshark/-/issues/20126
  60. https://gitlab.com/wireshark/wireshark/-/issues/20129
  61. https://gitlab.com/wireshark/wireshark/-/issues/20134
  62. https://gitlab.com/wireshark/wireshark/-/issues/20142
  63. https://gitlab.com/wireshark/wireshark/-/issues/20156
  64. https://gitlab.com/wireshark/wireshark/-/issues/20159
  65. https://gitlab.com/wireshark/wireshark/-/issues/20163
  66. https://gitlab.com/wireshark/wireshark/-/issues/20167
  67. https://gitlab.com/wireshark/wireshark/-/issues/20169
  68. https://gitlab.com/wireshark/wireshark/-/issues/20173
  69. https://gitlab.com/wireshark/wireshark/-/issues/20174
  70. https://gitlab.com/wireshark/wireshark/-/issues/20182
  71. https://gitlab.com/wireshark/wireshark/-/issues/20183
  72. https://gitlab.com/wireshark/wireshark/-/issues/20184
  73. https://gitlab.com/wireshark/wireshark/-/issues/20187
  74. https://gitlab.com/wireshark/wireshark/-/issues/20188
  75. https://gitlab.com/wireshark/wireshark/-/issues/20190
  76. https://gitlab.com/wireshark/wireshark/-/issues/20191
  77. https://gitlab.com/wireshark/wireshark/-/issues/20192
  78. https://gitlab.com/wireshark/wireshark/-/issues/20193
  79. https://gitlab.com/wireshark/wireshark/-/issues/20204
  80. https://gitlab.com/wireshark/wireshark/-/issues/20216
  81. https://www.wireshark.org/docs/relnotes/wireshark-4.4.1.html
  82. https://www.wireshark.org/security/wnpa-sec-2024-12
  83. https://gitlab.com/wireshark/wireshark/-/issues/20026
  84. https://www.wireshark.org/security/wnpa-sec-2024-13
  85. https://gitlab.com/wireshark/wireshark/-/issues/20114
  86. https://gitlab.com/wireshark/wireshark/-/issues/11176
  87. https://gitlab.com/wireshark/wireshark/-/issues/14729
  88. https://gitlab.com/wireshark/wireshark/-/issues/19854
  89. https://gitlab.com/wireshark/wireshark/-/issues/19886
  90. https://gitlab.com/wireshark/wireshark/-/issues/19930
  91. https://gitlab.com/wireshark/wireshark/-/issues/20020
  92. https://gitlab.com/wireshark/wireshark/-/issues/20021
  93. https://gitlab.com/wireshark/wireshark/-/issues/20030
  94. https://gitlab.com/wireshark/wireshark/-/issues/20031
  95. https://gitlab.com/wireshark/wireshark/-/issues/20040
  96. https://gitlab.com/wireshark/wireshark/-/issues/20044
  97. https://gitlab.com/wireshark/wireshark/-/issues/20047
  98. https://gitlab.com/wireshark/wireshark/-/issues/20049
  99. https://gitlab.com/wireshark/wireshark/-/issues/20051
  100. https://gitlab.com/wireshark/wireshark/-/issues/20052
  101. https://gitlab.com/wireshark/wireshark/-/issues/20054
  102. https://gitlab.com/wireshark/wireshark/-/issues/20055
  103. https://gitlab.com/wireshark/wireshark/-/issues/20056
  104. https://gitlab.com/wireshark/wireshark/-/issues/20057
  105. https://gitlab.com/wireshark/wireshark/-/issues/20069
  106. https://gitlab.com/wireshark/wireshark/-/issues/20071
  107. https://gitlab.com/wireshark/wireshark/-/issues/20079
  108. https://gitlab.com/wireshark/wireshark/-/issues/20082
  109. https://gitlab.com/wireshark/wireshark/-/issues/20088
  110. https://gitlab.com/wireshark/wireshark/-/issues/20090
  111. https://gitlab.com/wireshark/wireshark/-/issues/20100
  112. https://gitlab.com/wireshark/wireshark/-/issues/20110
  113. https://www.wireshark.org/docs/relnotes/wireshark-4.4.0.html
  114. https://www.wireshark.org/download.html
  115. https://ask.wireshark.org/
  116. https://lists.wireshark.org/lists/
  117. https://gitlab.com/wireshark/wireshark/-/issues
  118. https://sharkfest.wireshark.org
  119. https://wiresharkfoundation.org
  120. https://www.wireshark.org/faq.html


Digests

wireshark-4.4.6.tar.xz: 46802228 bytes
SHA256(wireshark-4.4.6.tar.xz)=4fffcee3d18d1daac12f780c2e8da511824dffb3b0fd6446b53ab7516538edcd
SHA1(wireshark-4.4.6.tar.xz)=bab4fbc7b394f120644e8f1931156d10d7037f56

Wireshark-4.4.6-x64.exe: 87330024 bytes
SHA256(Wireshark-4.4.6-x64.exe)=d1925b045300c34ea8082b7ec0d79aeae31edf01eb9fdd9b69e069ece785ca93
SHA1(Wireshark-4.4.6-x64.exe)=cd8b9e5dffe7235b69e7ab17422a567a33667466

Wireshark-4.4.6-arm64.exe: 68796800 bytes
SHA256(Wireshark-4.4.6-arm64.exe)=50f080cc9a8a58b0b6ea881749b90f0cb3308360c346b5249ae89324581c31b7
SHA1(Wireshark-4.4.6-arm64.exe)=ff7990ba4e73b8a565ccf7802fa87218986c0f9a

Wireshark-4.4.6-x64.msi: 63913984 bytes
SHA256(Wireshark-4.4.6-x64.msi)=5b13c415d412704fe6ac66b961378e4baf03060729fb0fd757c03e57dcb1b9fa
SHA1(Wireshark-4.4.6-x64.msi)=b10dc96b5a6f7b64e2fa1bf5ac4493efcfb53a23

WiresharkPortable64_4.4.6.paf.exe: 64481568 bytes
SHA256(WiresharkPortable64_4.4.6.paf.exe)=4cb8db4999e1b4100a665f09c3da3aa3c12f4361c3ad89a70db6014b77a24505
SHA1(WiresharkPortable64_4.4.6.paf.exe)=90b40faa5e7dadcbddda247339f4ca6ce78a2190

Wireshark 4.4.6 Arm 64.dmg: 65465899 bytes
SHA256(Wireshark 4.4.6 Arm 64.dmg)=37a664d6e4708266553c7b6b734b214b90385b1fd58a6bf1a173eb73284cb4dd
SHA1(Wireshark 4.4.6 Arm 64.dmg)=a38c0e1b73ddc7a68993e6bf2649e5c427726147

Wireshark 4.4.6 Intel 64.dmg: 69187477 bytes
SHA256(Wireshark 4.4.6 Intel 64.dmg)=b68394def6666d6922d82e37ec8fca456bb17a10b9b678e479b6002d58fc43de
SHA1(Wireshark 4.4.6 Intel 64.dmg)=8a9491df1d520e44bda95b3384533d13d7e7b4c3

You can validate these hashes using the following commands (among others):

    Windows: certutil -hashfile Wireshark-win64-x.y.z.exe SHA256
    Linux (GNU Coreutils): sha256sum wireshark-x.y.z.tar.xz
    macOS: shasum -a 256 "Wireshark x.y.z Arm 64.dmg"
    Other: openssl sha256 wireshark-x.y.z.tar.xz