Wireshark-announce: [Wireshark-announce] Wireshark 4.4.13 is now available

Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 14 Jan 2026 12:00:23 -0800
I'm proud to announce the release of Wireshark 4.4.13.


 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 vulnerabilities have been fixed:

     • wnpa-sec-2026-01[2] BLF file parser crash. Issue 20880[3].

     • wnpa-sec-2026-02[4] IEEE 802.11 dissector crash. Issue 20939[5].

     • wnpa-sec-2026-03[6] SOME/IP-SD dissector crash. Issue 20945[7].

   The following bugs have been fixed:

     • Bug in decoding 5G NAS message - Extended CAG information list
       IE. Issue 20946[8].

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   DCT2000, H.248, H.265, IDN, IEEE 802.11, NAS-5GS, QUIC, SOME/IP-SD,
   and Thrift

  New and Updated Capture File Support

   BLF, NetScreen, and Viavi Observer

  New and Updated File Format Decoding Support

   There is no updated file format support in this release.

 Prior Versions

  Wireshark 4.4.12 included the following changes. See the release
  notes[9] for details:

    • wnpa-sec-2025-07[10] HTTP3 dissector crash. Issue 20860[11].
      CVE-2025-13945[12].

    • wnpa-sec-2025-08[13] MEGACO dissector infinite loop. Issue
      20884[14]. CVE-2025-13945[15].

    • ws_base32_decode should be named *_encode ? Issue 20754[16].

    • Stack buffer overflow in wiretap/ber.c (ber_open) Issue 20878[17].

    • Fuzz job crash: fuzz-2025-11-30-12266121180.pcap. Issue 20883[18].

    • Missing data in pinfo→cinfo in HomePlug message CM_ATTEN_CHAR.IND.
      Issue 20893[19].

  Wireshark 4.4.11 included the following changes. See the release
  notes[20] for details:

    • wnpa-sec-2025-06[21] Kafka dissector crash. Issue 20823[22].

    • L2CAP dissector doesn’t understand retransmission mode. Issue
      2241[23].

    • DNS HIP dissector labels PK algorithm as HIT length. Issue
      20768[24].

    • TLS Abbreviated Handshake Using New Session Ticket. Issue
      20802[25].

    • Apply As Filter for field with FT_NONE and BASE_NONE for a single
      byte does not use the hex value. Issue 20818[26].

    • TCP dissector creates invalid packet diagram. Issue 20820[27].

    • Support UTF-16 strings in the IsoBus dissector for the string
      operations. Issue 20845[28].

    • Fuzz job issue: fuzz-2025-11-12-12064814316.pcap. Issue 20852[29].

  Wireshark 4.4.10 included the following changes. See the release
  notes[30] for details:

    • Using wslog parameters in command line applications leads to
      freeing invalid memory. Issue 20500[31].

    • On macOS a lower resolution Wireshark icon is displayed in the App
      Switcher and Launchpad. sbug20544[32].

    • Fuzz job crash: fuzz-2025-08-06-10932469456.pcap. Issue 20666[33].

    • Encoding on NAS5GS- NASDL Transport Message-Multiple Container
      contains inconsistencies. wsbuglink:20679].

    • Bad resolver in Delegated Credential (RFC 9345) of TLS 1.3
      CertificateRequest message. wsbuglink:20728].

    • Fuzz job UTF-8 encoding issue: fuzz-2025-10-03-11586692659.pcap.
      Issue 20744[34].

  Wireshark 4.4.9 included the following changes. See the release
  notes[35] for details:

    • RDM Product Detail List ID Disect incorrect. Issue 20612[36].

    • SCCP LUDT segmentation decoding fails. Issue 20647[37].

    • Ciscodump fails to start capture on Cisco IOS. Issue 20655[38].

    • [BACnet] WritePropertyMultiple closing context tag 1 not showing.
      Issue 20665[39].

    • Bug in LZ77 decoder; reads a 16-bit length when it should read a
      32-bit length. Issue 20671[40].

  Wireshark 4.4.8 included the following changes. See the release
  notes[41] for details:

    • Renegotiated DTLS session is not being decrypted. Issue 20362[42].

    • Wireshark is completely stuck in initialization because
      androiddump recv() is blocked. Issue 20526[43].

    • Fuzz job UTF-8 encoding issue: fuzz-2025-06-20-7318.pcap. Issue
      20585[44].

    • Crash when showing packet in new window after reloading Lua
      plugins with a certain gui.column.format preference. Issue
      20588[45].

    • Bug in UDS dissector with Service ReadDataByPeriodicIdentifier
      Response. Issue 20589[46].

    • Packet diagram doesn’t show non-standard field value
      representations. Issue 20590[47].

    • Packet diagram shows representation twice when field type is
      FT_NONE. Issue 20601[48].

    • application/x-www-form-urlencoded key parsed incorrectly following
      a name-value byte sequence with no '=' Issue 20615[49].

    • DNP3 time stamp was unable to work after epoch time(year 2038)
      Issue 20618[50].

  Wireshark 4.4.7 included the following changes. See the release
  notes[51] for details:

    • wnpa-sec-2025-02[52] Dissection engine crash. Issue 20509[53].
      CVE-2025-5601[54].

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

    • Dissector bug, Protocol CIGI. Issue 20496[56].

    • Green power packets are not dissected when proto_version ==
      ZBEE_VERSION_GREEN_POWER. Issue 20497[57].

    • Packet diagrams misalign or drop bitfields. Issue 20507[58].

    • Corruption when setting heuristic dissector table UI name from
      Lua. Issue 20523[59].

    • LDAP dissector incorrectly displays filters with singleton "&"
      Issue 20527[60].

    • WebSocket per-message compression extentions: fail to decompress
      server messages (from the 2nd) due to parameter handling. Issue
      20531[61].

    • The LL_PERIODIC_SYNC_WR_IND packet is not properly dissected
      (packet-btle.c) Issue 20554[62].

  Wireshark 4.4.6 included the following changes. See the release
  notes[63] for details:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    • wnpa-sec-2024-15[108] ECMP dissector crash. Issue 20214[109].

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    • MODBUS Dissector bug. Issue 20192[139].

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

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

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

  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[143] for details:

    • wnpa-sec-2024-12[144] ITS dissector crash. Issue 20026[145].

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

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

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

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

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

    • 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[152].

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  Wireshark 4.4.0 included the following changes. See the release
  notes[175] 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[176] 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[177] 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[178].

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

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

  Official Wireshark training and certification are available from the
  Wireshark Foundation[181].

 Getting Certified

  You can become a Wireshark Certified Analyst! Learn more at
  https://www.wireshark.org/certifications

 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[182].

 Frequently Asked Questions

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

 References

   1. https://wiresharkfoundation.org
   2. https://www.wireshark.org/security/wnpa-sec-2026-01
   3. https://gitlab.com/wireshark/wireshark/-/issues/20880
   4. https://www.wireshark.org/security/wnpa-sec-2026-02
   5. https://gitlab.com/wireshark/wireshark/-/issues/20939
   6. https://www.wireshark.org/security/wnpa-sec-2026-03
   7. https://gitlab.com/wireshark/wireshark/-/issues/20945
   8. https://gitlab.com/wireshark/wireshark/-/issues/20946
   9. https://www.wireshark.org/docs/relnotes/wireshark-4.4.12.html
  10. https://www.wireshark.org/security/wnpa-sec-2025-07
  11. https://gitlab.com/wireshark/wireshark/-/issues/20860
  12. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-13945
  13. https://www.wireshark.org/security/wnpa-sec-2025-08
  14. https://gitlab.com/wireshark/wireshark/-/issues/20884
  15. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-13945
  16. https://gitlab.com/wireshark/wireshark/-/issues/20754
  17. https://gitlab.com/wireshark/wireshark/-/issues/20878
  18. https://gitlab.com/wireshark/wireshark/-/issues/20883
  19. https://gitlab.com/wireshark/wireshark/-/issues/20893
  20. https://www.wireshark.org/docs/relnotes/wireshark-4.4.11.html
  21. https://www.wireshark.org/security/wnpa-sec-2025-06
  22. https://gitlab.com/wireshark/wireshark/-/issues/20823
  23. https://gitlab.com/wireshark/wireshark/-/issues/2241
  24. https://gitlab.com/wireshark/wireshark/-/issues/20768
  25. https://gitlab.com/wireshark/wireshark/-/issues/20802
  26. https://gitlab.com/wireshark/wireshark/-/issues/20818
  27. https://gitlab.com/wireshark/wireshark/-/issues/20820
  28. https://gitlab.com/wireshark/wireshark/-/issues/20845
  29. https://gitlab.com/wireshark/wireshark/-/issues/20852
  30. https://www.wireshark.org/docs/relnotes/wireshark-4.4.10.html
  31. https://gitlab.com/wireshark/wireshark/-/issues/20500
  32. https://gitlab.com/wireshark/wireshark/-/issues/20500
  33. https://gitlab.com/wireshark/wireshark/-/issues/20666
  34. https://gitlab.com/wireshark/wireshark/-/issues/20744
  35. https://www.wireshark.org/docs/relnotes/wireshark-4.4.9.html
  36. https://gitlab.com/wireshark/wireshark/-/issues/20612
  37. https://gitlab.com/wireshark/wireshark/-/issues/20647
  38. https://gitlab.com/wireshark/wireshark/-/issues/20655
  39. https://gitlab.com/wireshark/wireshark/-/issues/20665
  40. https://gitlab.com/wireshark/wireshark/-/issues/20671
  41. https://www.wireshark.org/docs/relnotes/wireshark-4.4.8.html
  42. https://gitlab.com/wireshark/wireshark/-/issues/20362
  43. https://gitlab.com/wireshark/wireshark/-/issues/20526
  44. https://gitlab.com/wireshark/wireshark/-/issues/20585
  45. https://gitlab.com/wireshark/wireshark/-/issues/20588
  46. https://gitlab.com/wireshark/wireshark/-/issues/20589
  47. https://gitlab.com/wireshark/wireshark/-/issues/20590
  48. https://gitlab.com/wireshark/wireshark/-/issues/20601
  49. https://gitlab.com/wireshark/wireshark/-/issues/20615
  50. https://gitlab.com/wireshark/wireshark/-/issues/20618
  51. https://www.wireshark.org/docs/relnotes/wireshark-4.4.7.html
  52. https://www.wireshark.org/security/wnpa-sec-2025-02
  53. https://gitlab.com/wireshark/wireshark/-/issues/20509
  54. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-5601
  55. https://gitlab.com/wireshark/wireshark/-/issues/20463
  56. https://gitlab.com/wireshark/wireshark/-/issues/20496
  57. https://gitlab.com/wireshark/wireshark/-/issues/20497
  58. https://gitlab.com/wireshark/wireshark/-/issues/20507
  59. https://gitlab.com/wireshark/wireshark/-/issues/20523
  60. https://gitlab.com/wireshark/wireshark/-/issues/20527
  61. https://gitlab.com/wireshark/wireshark/-/issues/20531
  62. https://gitlab.com/wireshark/wireshark/-/issues/20554
  63. https://www.wireshark.org/docs/relnotes/wireshark-4.4.6.html
  64. https://gitlab.com/wireshark/wireshark/-/issues/13718
  65. https://gitlab.com/wireshark/wireshark/-/issues/15978
  66. https://gitlab.com/wireshark/wireshark/-/issues/18216
  67. https://gitlab.com/wireshark/wireshark/-/issues/18717
  68. https://gitlab.com/wireshark/wireshark/-/issues/20343
  69. https://gitlab.com/wireshark/wireshark/-/issues/20355
  70. https://gitlab.com/wireshark/wireshark/-/issues/20371
  71. https://gitlab.com/wireshark/wireshark/-/issues/20372
  72. https://gitlab.com/wireshark/wireshark/-/issues/20423
  73. https://gitlab.com/wireshark/wireshark/-/issues/20429
  74. https://gitlab.com/wireshark/wireshark/-/issues/20434
  75. https://gitlab.com/wireshark/wireshark/-/issues/20459
  76. https://gitlab.com/wireshark/wireshark/-/issues/20463
  77. https://gitlab.com/wireshark/wireshark/-/issues/20476
  78. https://www.wireshark.org/docs/relnotes/wireshark-4.4.5.html
  79. https://gitlab.com/wireshark/wireshark/-/issues/20392
  80. https://gitlab.com/wireshark/wireshark/-/issues/20403
  81. https://www.wireshark.org/docs/relnotes/wireshark-4.4.4.html
  82. https://www.wireshark.org/security/wnpa-sec-2025-01
  83. https://gitlab.com/wireshark/wireshark/-/issues/20373
  84. https://gitlab.com/wireshark/wireshark/-/issues/20263
  85. https://gitlab.com/wireshark/wireshark/-/issues/20300
  86. https://gitlab.com/wireshark/wireshark/-/issues/20330
  87. https://gitlab.com/wireshark/wireshark/-/issues/20354
  88. https://gitlab.com/wireshark/wireshark/-/issues/20357
  89. https://gitlab.com/wireshark/wireshark/-/issues/20359
  90. https://gitlab.com/wireshark/wireshark/-/issues/20367
  91. https://gitlab.com/wireshark/wireshark/-/issues/20386
  92. https://gitlab.com/wireshark/wireshark/-/issues/20387
  93. https://gitlab.com/wireshark/wireshark/-/issues/20389
  94. https://gitlab.com/wireshark/wireshark/-/issues/20391
  95. https://gitlab.com/wireshark/wireshark/-/issues/20394
  96. https://www.wireshark.org/docs/relnotes/wireshark-4.4.3.html
  97. https://gitlab.com/wireshark/wireshark/-/issues/20247
  98. https://gitlab.com/wireshark/wireshark/-/issues/20276
  99. https://gitlab.com/wireshark/wireshark/-/issues/20290
  100. https://gitlab.com/wireshark/wireshark/-/issues/20304
  101. https://gitlab.com/wireshark/wireshark/-/issues/20311
  102. https://gitlab.com/wireshark/wireshark/-/issues/20313
  103. https://gitlab.com/wireshark/wireshark/-/issues/20320
  104. https://gitlab.com/wireshark/wireshark/-/issues/20326
  105. https://www.wireshark.org/docs/relnotes/wireshark-4.4.2.html
  106. https://www.wireshark.org/security/wnpa-sec-2024-14
  107. https://gitlab.com/wireshark/wireshark/-/issues/20176
  108. https://www.wireshark.org/security/wnpa-sec-2024-15
  109. https://gitlab.com/wireshark/wireshark/-/issues/20214
  110. https://gitlab.com/wireshark/wireshark/-/issues/19517
  111. https://gitlab.com/wireshark/wireshark/-/issues/20041
  112. https://gitlab.com/wireshark/wireshark/-/issues/20065
  113. https://gitlab.com/wireshark/wireshark/-/issues/20066
  114. https://gitlab.com/wireshark/wireshark/-/issues/20082
  115. https://gitlab.com/wireshark/wireshark/-/issues/20099
  116. https://gitlab.com/wireshark/wireshark/-/issues/20107
  117. https://gitlab.com/wireshark/wireshark/-/issues/20108
  118. https://gitlab.com/wireshark/wireshark/-/issues/20113
  119. https://gitlab.com/wireshark/wireshark/-/issues/20124
  120. https://gitlab.com/wireshark/wireshark/-/issues/20125
  121. https://gitlab.com/wireshark/wireshark/-/issues/20126
  122. https://gitlab.com/wireshark/wireshark/-/issues/20129
  123. https://gitlab.com/wireshark/wireshark/-/issues/20134
  124. https://gitlab.com/wireshark/wireshark/-/issues/20142
  125. https://gitlab.com/wireshark/wireshark/-/issues/20156
  126. https://gitlab.com/wireshark/wireshark/-/issues/20159
  127. https://gitlab.com/wireshark/wireshark/-/issues/20163
  128. https://gitlab.com/wireshark/wireshark/-/issues/20167
  129. https://gitlab.com/wireshark/wireshark/-/issues/20169
  130. https://gitlab.com/wireshark/wireshark/-/issues/20173
  131. https://gitlab.com/wireshark/wireshark/-/issues/20174
  132. https://gitlab.com/wireshark/wireshark/-/issues/20182
  133. https://gitlab.com/wireshark/wireshark/-/issues/20183
  134. https://gitlab.com/wireshark/wireshark/-/issues/20184
  135. https://gitlab.com/wireshark/wireshark/-/issues/20187
  136. https://gitlab.com/wireshark/wireshark/-/issues/20188
  137. https://gitlab.com/wireshark/wireshark/-/issues/20190
  138. https://gitlab.com/wireshark/wireshark/-/issues/20191
  139. https://gitlab.com/wireshark/wireshark/-/issues/20192
  140. https://gitlab.com/wireshark/wireshark/-/issues/20193
  141. https://gitlab.com/wireshark/wireshark/-/issues/20204
  142. https://gitlab.com/wireshark/wireshark/-/issues/20216
  143. https://www.wireshark.org/docs/relnotes/wireshark-4.4.1.html
  144. https://www.wireshark.org/security/wnpa-sec-2024-12
  145. https://gitlab.com/wireshark/wireshark/-/issues/20026
  146. https://www.wireshark.org/security/wnpa-sec-2024-13
  147. https://gitlab.com/wireshark/wireshark/-/issues/20114
  148. https://gitlab.com/wireshark/wireshark/-/issues/11176
  149. https://gitlab.com/wireshark/wireshark/-/issues/14729
  150. https://gitlab.com/wireshark/wireshark/-/issues/19854
  151. https://gitlab.com/wireshark/wireshark/-/issues/19886
  152. https://gitlab.com/wireshark/wireshark/-/issues/19930
  153. https://gitlab.com/wireshark/wireshark/-/issues/20020
  154. https://gitlab.com/wireshark/wireshark/-/issues/20021
  155. https://gitlab.com/wireshark/wireshark/-/issues/20030
  156. https://gitlab.com/wireshark/wireshark/-/issues/20031
  157. https://gitlab.com/wireshark/wireshark/-/issues/20040
  158. https://gitlab.com/wireshark/wireshark/-/issues/20044
  159. https://gitlab.com/wireshark/wireshark/-/issues/20047
  160. https://gitlab.com/wireshark/wireshark/-/issues/20049
  161. https://gitlab.com/wireshark/wireshark/-/issues/20051
  162. https://gitlab.com/wireshark/wireshark/-/issues/20052
  163. https://gitlab.com/wireshark/wireshark/-/issues/20054
  164. https://gitlab.com/wireshark/wireshark/-/issues/20055
  165. https://gitlab.com/wireshark/wireshark/-/issues/20056
  166. https://gitlab.com/wireshark/wireshark/-/issues/20057
  167. https://gitlab.com/wireshark/wireshark/-/issues/20069
  168. https://gitlab.com/wireshark/wireshark/-/issues/20071
  169. https://gitlab.com/wireshark/wireshark/-/issues/20079
  170. https://gitlab.com/wireshark/wireshark/-/issues/20082
  171. https://gitlab.com/wireshark/wireshark/-/issues/20088
  172. https://gitlab.com/wireshark/wireshark/-/issues/20090
  173. https://gitlab.com/wireshark/wireshark/-/issues/20100
  174. https://gitlab.com/wireshark/wireshark/-/issues/20110
  175. https://www.wireshark.org/docs/relnotes/wireshark-4.4.0.html
  176. https://www.wireshark.org/download.html
  177. https://ask.wireshark.org/
  178. https://lists.wireshark.org/lists/
  179. https://gitlab.com/wireshark/wireshark/-/issues
  180. https://sharkfest.wireshark.org
  181. https://www.wireshark.org/certifications
  182. https://wiresharkfoundation.org
  183. https://www.wireshark.org/faq.html


Digests

wireshark-4.6.3.tar.xz: 50636640 bytes
SHA256(wireshark-4.6.3.tar.xz)=9fa6a745df8540899dc9d433e4634d6755371ff87bd722ce04c7d7b0132d9af3
SHA1(wireshark-4.6.3.tar.xz)=48946917e956315938af4f21d0813b8a19512f6b

Wireshark-4.6.3-x64.exe: 96653880 bytes
SHA256(Wireshark-4.6.3-x64.exe)=09db2e7365b8dc56bc293b5e2849d9d06ebd8411f5a5e72e528964fbb051f283
SHA1(Wireshark-4.6.3-x64.exe)=cec27b460433761367e22b6695ecbde736adc9d9

Wireshark-4.6.3-arm64.exe: 75367848 bytes
SHA256(Wireshark-4.6.3-arm64.exe)=c9578cef62c7614824679c6025c10a033ddb2e56347ef4f6c1a7fce6f4e28563
SHA1(Wireshark-4.6.3-arm64.exe)=abbac496d128a2313cfe54ba4f30a971383cd0d2

Wireshark-4.6.3-x64.msi: 73793536 bytes
SHA256(Wireshark-4.6.3-x64.msi)=59b5ac08efc1bd595064b942d33c0ae63e4343db063fd388ce69bdd42285f542
SHA1(Wireshark-4.6.3-x64.msi)=eca843571ca6ca3570798a659f42ceb0dac3847b

WiresharkPortable64_4.6.3.paf.exe: 95753504 bytes
SHA256(WiresharkPortable64_4.6.3.paf.exe)=ee62f97a0f91ae998fa8a34bef640ee0a5bd8582324d59a33c1bdf3b5d833e07
SHA1(WiresharkPortable64_4.6.3.paf.exe)=e76bfe3ead03e8597532db2e6be9a2fb858d18b4

Wireshark 4.6.3.dmg: 141516002 bytes
SHA256(Wireshark 4.6.3.dmg)=788fef0f62fc58d2523270256694efc30e79f3584d4895eb066ca333daa88fe9
SHA1(Wireshark 4.6.3.dmg)=233ca01482e9fbe6770b173c83e67d825c72e195

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

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

Attachment: OpenPGP_0x82244A78E6FEAEEA.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature