Wireshark-announce: [Wireshark-announce] Wireshark 4.4.12 is now available
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Fri, 5 Dec 2025 12:20:07 -0800
I'm proud to announce the release of Wireshark 4.4.12.
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-2025-07[2] HTTP3 dissector crash. Issue 20860[3].
CVE-2025-13945[4].
• wnpa-sec-2025-08[5] MEGACO dissector infinite loop. Issue
20884[6]. CVE-2025-13945[7].
The following bugs have been fixed:
• ws_base32_decode should be named *_encode ? Issue 20754[8].
• Stack buffer overflow in wiretap/ber.c (ber_open) Issue 20878[9].
• Fuzz job crash: fuzz-2025-11-30-12266121180.pcap. Issue
20883[10].
• Missing data in pinfo→cinfo in HomePlug message
CM_ATTEN_CHAR.IND. Issue 20893[11].
New Protocol Support
There are no new protocols in this release.
Updated Protocol Support
Fc00, HomePlug AV, MEGACO, and SMTP
New and Updated Capture File Support
There is no new or updated capture file support in this release.
New and Updated File Format Decoding Support
There is no updated file format support in this release.
Prior Versions
Wireshark 4.4.11 included the following changes. See the release
notes[12] for details:
• wnpa-sec-2025-06[13] Kafka dissector crash. Issue 20823[14].
• L2CAP dissector doesn’t understand retransmission mode. Issue
2241[15].
• DNS HIP dissector labels PK algorithm as HIT length. Issue
20768[16].
• TLS Abbreviated Handshake Using New Session Ticket. Issue
20802[17].
• Apply As Filter for field with FT_NONE and BASE_NONE for a single
byte does not use the hex value. Issue 20818[18].
• TCP dissector creates invalid packet diagram. Issue 20820[19].
• Support UTF-16 strings in the IsoBus dissector for the string
operations. Issue 20845[20].
• Fuzz job issue: fuzz-2025-11-12-12064814316.pcap. Issue 20852[21].
Wireshark 4.4.10 included the following changes. See the release
notes[22] for details:
• Using wslog parameters in command line applications leads to
freeing invalid memory. Issue 20500[23].
• On macOS a lower resolution Wireshark icon is displayed in the App
Switcher and Launchpad. sbug20544[24].
• Fuzz job crash: fuzz-2025-08-06-10932469456.pcap. Issue 20666[25].
• 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[26].
Wireshark 4.4.9 included the following changes. See the release
notes[27] for details:
• RDM Product Detail List ID Disect incorrect. Issue 20612[28].
• SCCP LUDT segmentation decoding fails. Issue 20647[29].
• Ciscodump fails to start capture on Cisco IOS. Issue 20655[30].
• [BACnet] WritePropertyMultiple closing context tag 1 not showing.
Issue 20665[31].
• Bug in LZ77 decoder; reads a 16-bit length when it should read a
32-bit length. Issue 20671[32].
Wireshark 4.4.8 included the following changes. See the release
notes[33] for details:
• Renegotiated DTLS session is not being decrypted. Issue 20362[34].
• Wireshark is completely stuck in initialization because
androiddump recv() is blocked. Issue 20526[35].
• Fuzz job UTF-8 encoding issue: fuzz-2025-06-20-7318.pcap. Issue
20585[36].
• Crash when showing packet in new window after reloading Lua
plugins with a certain gui.column.format preference. Issue
20588[37].
• Bug in UDS dissector with Service ReadDataByPeriodicIdentifier
Response. Issue 20589[38].
• Packet diagram doesn’t show non-standard field value
representations. Issue 20590[39].
• Packet diagram shows representation twice when field type is
FT_NONE. Issue 20601[40].
• application/x-www-form-urlencoded key parsed incorrectly following
a name-value byte sequence with no '=' Issue 20615[41].
• DNP3 time stamp was unable to work after epoch time(year 2038)
Issue 20618[42].
Wireshark 4.4.7 included the following changes. See the release
notes[43] for details:
• wnpa-sec-2025-02[44] Dissection engine crash. Issue 20509[45].
CVE-2025-5601[46].
• Wireshark does not correctly decode LIN "go to sleep" in TECMP and
CMP. Issue 20463[47].
• Dissector bug, Protocol CIGI. Issue 20496[48].
• Green power packets are not dissected when proto_version ==
ZBEE_VERSION_GREEN_POWER. Issue 20497[49].
• Packet diagrams misalign or drop bitfields. Issue 20507[50].
• Corruption when setting heuristic dissector table UI name from
Lua. Issue 20523[51].
• LDAP dissector incorrectly displays filters with singleton "&"
Issue 20527[52].
• WebSocket per-message compression extentions: fail to decompress
server messages (from the 2nd) due to parameter handling. Issue
20531[53].
• The LL_PERIODIC_SYNC_WR_IND packet is not properly dissected
(packet-btle.c) Issue 20554[54].
Wireshark 4.4.6 included the following changes. See the release
notes[55] for details:
• Bug in EtherCAT dissector with ECS order. Issue 13718[56].
• Conversation dialog columns return to default width on each new
packet in live capture. Issue 15978[57].
• Tests fail in LTO-enabled builds in Ubuntu/Debian. Issue
18216[58].
• Incorrect conditions in BFCP dissector. Issue 18717[59].
• Static build fails on Ubuntu 24.04 because the c-ares library
isn’t found. Issue 20343[60].
• Flutter’s Image Picker Generated JPEG Files Detected as Malformed
Packet. Issue 20355[61].
• QUIC dissector breaks when src and dst change. Issue 20371[62].
• s390x: build fail on Ubuntu PPA nighty build. Issue 20372[63].
• Trailing octet after IPv4 packet end is not detected or displayed
in raw bytes. Issue 20423[64].
• [packet-ax25-nol3.c] Only call APRS dissector on UI Frames. Issue
20429[65].
• Wireshark hangs when refreshing interfaces with the debug console
preference set to "always" and a file open (Windows) Issue
20434[66].
• BGP EVPN - Type-8 route not correctly read after addition of Max.
Response Time field. Issue 20459[67].
• Wireshark does not correctly decode LIN "go to sleep" in TECMP and
CMP. Issue 20463[68].
• MQTT-SN: WILLTOPIC message not decoded correctly (missing some
flags) Issue 20476[69].
Wireshark 4.4.5 included the following changes. See the release
notes[70] for details:
• GRPC: protobuf_json only displays the truncated string value.
Issue 20392[71].
• Wireshark crashes when clicking on a column title/header. Issue
20403[72].
Wireshark 4.4.4 included the following changes. See the release
notes[73] for details:
• wnpa-sec-2025-01[74] Bundle Protocol and CBOR dissector
{crash,infinite loop,memory leak}. Issue 20373[75].
• Crash when sorting columns during capture with display filter
active. Issue 20263[76].
• OSS-Fuzz 384757274: Invalid-bool-value in dissect_tcp. Issue
20300[77].
• Test failure in 4.4.2/4.4.3: test_sharkd_req_follow_http2. Issue
20330[78].
• Regression in extcap interface toolbar. Issue 20354[79].
• Clicking outside columns in TCP tab of Statistics → Conversations
window causes crash. Issue 20357[80].
• FTBFS with Ubuntu development (25.04) release. Issue 20359[81].
• DNS enable_qname_stats crash Wireshark when QDCOUNT == 0. Issue
20367[82].
• Windows: Android extcap plugin fails with "Broken socket
connection" if there are no new packets for 2sec. Issue 20386[83].
• TECMP: Calculation of lifecycle start in Status message is wrong.
Issue 20387[84].
• MQTT v5.0 properties total length presentation is incorrect. Issue
20389[85].
• TShark doesn’t resolve addresses in custom "hosts" files. Issue
20391[86].
• Incorrect JA4 fingerprint with empty ciphers. Issue 20394[87].
Wireshark 4.4.3 included the following changes. See the release
notes[88] for details:
• Potential mis-match in GSM MAP dissector for uncertainty radius
and its filter key. Issue 20247[89].
• Macro eNodeB ID and Extended Macro eNodeB ID not decoded by User
Location Information. Issue 20276[90].
• The NFSv2 Dissector appears to be swapping Character Special File
and Directory in mode decoding. Issue 20290[91].
• CMake discovers Strawberry Perl’s zlib DLL when it shouldn’t.
Issue 20304[92].
• VOIP Calls call flow displaying hours. Issue 20311[93].
• Fuzz job issue: fuzz-2024-12-26-7898.pcap. Issue 20313[94].
• sFlow: Incorrect length passed to header sample dissector. Issue
20320[95].
• wsutil: Should link against -lm due to missing fabs() when built
with -fno-builtin. Issue 20326[96].
Wireshark 4.4.2 included the following changes. See the release
notes[97] for details:
• wnpa-sec-2024-14[98] FiveCo RAP dissector infinite loop. Issue
20176[99].
• wnpa-sec-2024-15[100] ECMP dissector crash. Issue 20214[101].
• CIP I/O is not detected by "enip" filter anymore. Issue
19517[102].
• Fuzz job issue: fuzz-2024-09-03-7550.pcap. Issue 20041[103].
• OSS-Fuzz 71476: wireshark:fuzzshark_ip_proto-udp:
Index-out-of-bounds in DOFObjectID_Create_Unmarshal. Issue
20065[104].
• JA4_c hashes an empty field to e3b0c44298fc when it should be
000000000000. Issue 20066[105].
• Opening Wireshark 4.4.0 on macOS 15.0 disconnects iPhone
Mirroring. Issue 20082[106].
• PTP analysis loses track of message associations in case of
sequence number resets. Issue 20099[107].
• USB CCID: response packet in case SetParameters command is
unsupported is flagged as malformed. Issue 20107[108].
• dumpcap crashes when run from TShark with a capture filter. Issue
20108[109].
• SRT dissector: The StreamID (SID) in the handshake extension is
displayed without regarding the control characters and with NUL as
terminating. Issue 20113[110].
• Ghost error message on POP3 packets. Issue 20124[111].
• Building against c-ares 1.34 fails. Issue 20125[112].
• D-Bus is not optional anymore. Issue 20126[113].
• macOS Intel DMGs aren’t fully notarized. Issue 20129[114].
• Incorrect name for MLD Capabilities and Operations Present flag in
dissection of MLD Capabilities for MLO wifi-7 capture. Issue
20134[115].
• CQL Malformed Packet v4 S → C Type RESULT: Prepared[Malformed
Packet] Issue 20142[116].
• Wi-Fi: 256 Block Ack (BA) is not parsed properly. Issue
20156[117].
• BACnet ReadPropertyMultiple request Maximum allowed recursion
depth reached. Issue 20159[118].
• Statistics→I/O Graph crashes when using simple moving average.
Issue 20163[119].
• HTTP2 body decompression fails on DATA with a single padded frame.
Issue 20167[120].
• Compiler warning for ui/tap-rtp-common.c (ignoring return value)
Issue 20169[121].
• SIP dissector bug due to "be-route" param in VIA header. Issue
20173[122].
• Coredump after trying to open 'Follow TCP stream' Issue
20174[123].
• Protobuf JSON mapping error. Issue 20182[124].
• Display filter "!stp.pvst.origvlan in { vlan.id }" causes a crash
(Version 4.4.1) Issue 20183[125].
• Extcap plugins shipped with Wireshark Portable are not found in
version 4.4.1. Issue 20184[126].
• IEEE 802.11be: Wrong regulatory info in HE Operation IE in Beacon
frame. Issue 20187[127].
• Wireshark 4.4.1 does not decode RTCP packets. Issue 20188[128].
• Qt: Display filter sub-menu can only be opened on the triangle,
not the full name. Issue 20190[129].
• Qt: Changing the display filter does not update the Conversations
or Endpoints dialogs. Issue 20191[130].
• MODBUS Dissector bug. Issue 20192[131].
• Modbus dissector bug - Field Occurence and Layer Operator
modbus.bitval field. Issue 20193[132].
• Wireshark crashes when a field is dragged from packet details
towards the find input. Issue 20204[133].
• Lua DissectorTable("") : set ("10,11") unexpected behavior in
locales with comma as decimal separator. Issue 20216[134].
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[135] for details:
• wnpa-sec-2024-12[136] ITS dissector crash. Issue 20026[137].
• wnpa-sec-2024-13[138] AppleTalk and RELOAD Framing dissector
crashes. Issue 20114[139].
• Refresh interface during live-capture leads to corrupt interface
handling. Issue 11176[140].
• Media type "application/octet-stream" registered for both Thread
and UASIP. Issue 14729[141].
• Extcap toolbar stops working when new interface is added. Issue
19854[142].
• Decoding error ITS CPM version 2.1.1. Issue 19886[143].
• 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[144].
• html2text.py doesn’t handle the `<sup>` tag. Issue 20020[145].
• Incorrect NetFlow v8 TOS AS aggregation dissection. Issue
20021[146].
• The Windows packages don’t ship with the IP address plugin. Issue
20030[147].
• O_PATH is Linux-and-FreeBSD-specific. Issue 20031[148].
• Wireshark 4.4.0 doesn’t install USBcap USBcapCMD.exe in the
correct directory. Issue 20040[149].
• OER dissector is not considering the preamble if ASN.1 SEQUENCE
definition includes extension marker but no OPTIONAL items. Issue
20044[150].
• Bluetooth classic L2CAP incorrect dissection with connectionless
reception channel. Issue 20047[151].
• Profile auto switch filters : Grayed Display Filter Expression
dialog box when opened from Configuration Profiles dialog box.
Issue 20049[152].
• Wireshark 4.4.0 / macOS 14.6.1 wifi if monitor mode. Issue
20051[153].
• TECMP Data Type passes too much data to sub dissectors. Issue
20052[154].
• Wireshark and tshark 4.4.0 ignore extcap options specified on the
command line. Issue 20054[155].
• Cannot open release notes due to incorrect path with duplicated
directory components. Issue 20055[156].
• Unable to open "Release Notes" from the "Help" menu. Issue
20056[157].
• No capture interfaces if Wireshark is started from command line
with certain paths. Issue 20057[158].
• Wireshark 4.4.0 extcap path change breaks third party extcap
installers. Issue 20069[159].
• Fuzz job UTF-8 encoding issue: fuzz-2024-09-10-7618.pcap. Issue
20071[160].
• Unable to create larger files than 99 size units. Issue
20079[161].
• Opening Wireshark 4.4.0 on macOS 15.0 disconnects iPhone
Mirroring. Issue 20082[162].
• PRP trailer not shown for L2 IEC 61850 GOOSE packets in 4.4.0 (was
working in 4.2.7) Issue 20088[163].
• GUI lags because NetworkManager keeps turning 802.11 monitor mode
off. Issue 20090[164].
• Error while getting Bluetooth application process id by <shell:ps
-A | grep com.*android.bluetooth> Issue 20100[165].
• Fuzz job assertion: randpkt-2024-10-05-7200.pcap. Issue
20110[166].
Wireshark 4.4.0 included the following changes. See the release
notes[167] 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[168] 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[169] 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[170].
Bugs and feature requests can be reported on the issue tracker[171].
You can learn protocol analysis and meet Wireshark’s developers at
SharkFest[172].
Official Wireshark training and certification are available from the
Wireshark Foundation[173].
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[174].
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site[175].
References
1. https://wiresharkfoundation.org
2. https://www.wireshark.org/security/wnpa-sec-2025-07
3. https://gitlab.com/wireshark/wireshark/-/issues/20860
4. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-13945
5. https://www.wireshark.org/security/wnpa-sec-2025-08
6. https://gitlab.com/wireshark/wireshark/-/issues/20884
7. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-13945
8. https://gitlab.com/wireshark/wireshark/-/issues/20754
9. https://gitlab.com/wireshark/wireshark/-/issues/20878
10. https://gitlab.com/wireshark/wireshark/-/issues/20883
11. https://gitlab.com/wireshark/wireshark/-/issues/20893
12. https://www.wireshark.org/docs/relnotes/wireshark-4.4.11.html
13. https://www.wireshark.org/security/wnpa-sec-2025-06
14. https://gitlab.com/wireshark/wireshark/-/issues/20823
15. https://gitlab.com/wireshark/wireshark/-/issues/2241
16. https://gitlab.com/wireshark/wireshark/-/issues/20768
17. https://gitlab.com/wireshark/wireshark/-/issues/20802
18. https://gitlab.com/wireshark/wireshark/-/issues/20818
19. https://gitlab.com/wireshark/wireshark/-/issues/20820
20. https://gitlab.com/wireshark/wireshark/-/issues/20845
21. https://gitlab.com/wireshark/wireshark/-/issues/20852
22. https://www.wireshark.org/docs/relnotes/wireshark-4.4.10.html
23. https://gitlab.com/wireshark/wireshark/-/issues/20500
24. https://gitlab.com/wireshark/wireshark/-/issues/20500
25. https://gitlab.com/wireshark/wireshark/-/issues/20666
26. https://gitlab.com/wireshark/wireshark/-/issues/20744
27. https://www.wireshark.org/docs/relnotes/wireshark-4.4.9.html
28. https://gitlab.com/wireshark/wireshark/-/issues/20612
29. https://gitlab.com/wireshark/wireshark/-/issues/20647
30. https://gitlab.com/wireshark/wireshark/-/issues/20655
31. https://gitlab.com/wireshark/wireshark/-/issues/20665
32. https://gitlab.com/wireshark/wireshark/-/issues/20671
33. https://www.wireshark.org/docs/relnotes/wireshark-4.4.8.html
34. https://gitlab.com/wireshark/wireshark/-/issues/20362
35. https://gitlab.com/wireshark/wireshark/-/issues/20526
36. https://gitlab.com/wireshark/wireshark/-/issues/20585
37. https://gitlab.com/wireshark/wireshark/-/issues/20588
38. https://gitlab.com/wireshark/wireshark/-/issues/20589
39. https://gitlab.com/wireshark/wireshark/-/issues/20590
40. https://gitlab.com/wireshark/wireshark/-/issues/20601
41. https://gitlab.com/wireshark/wireshark/-/issues/20615
42. https://gitlab.com/wireshark/wireshark/-/issues/20618
43. https://www.wireshark.org/docs/relnotes/wireshark-4.4.7.html
44. https://www.wireshark.org/security/wnpa-sec-2025-02
45. https://gitlab.com/wireshark/wireshark/-/issues/20509
46. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-5601
47. https://gitlab.com/wireshark/wireshark/-/issues/20463
48. https://gitlab.com/wireshark/wireshark/-/issues/20496
49. https://gitlab.com/wireshark/wireshark/-/issues/20497
50. https://gitlab.com/wireshark/wireshark/-/issues/20507
51. https://gitlab.com/wireshark/wireshark/-/issues/20523
52. https://gitlab.com/wireshark/wireshark/-/issues/20527
53. https://gitlab.com/wireshark/wireshark/-/issues/20531
54. https://gitlab.com/wireshark/wireshark/-/issues/20554
55. https://www.wireshark.org/docs/relnotes/wireshark-4.4.6.html
56. https://gitlab.com/wireshark/wireshark/-/issues/13718
57. https://gitlab.com/wireshark/wireshark/-/issues/15978
58. https://gitlab.com/wireshark/wireshark/-/issues/18216
59. https://gitlab.com/wireshark/wireshark/-/issues/18717
60. https://gitlab.com/wireshark/wireshark/-/issues/20343
61. https://gitlab.com/wireshark/wireshark/-/issues/20355
62. https://gitlab.com/wireshark/wireshark/-/issues/20371
63. https://gitlab.com/wireshark/wireshark/-/issues/20372
64. https://gitlab.com/wireshark/wireshark/-/issues/20423
65. https://gitlab.com/wireshark/wireshark/-/issues/20429
66. https://gitlab.com/wireshark/wireshark/-/issues/20434
67. https://gitlab.com/wireshark/wireshark/-/issues/20459
68. https://gitlab.com/wireshark/wireshark/-/issues/20463
69. https://gitlab.com/wireshark/wireshark/-/issues/20476
70. https://www.wireshark.org/docs/relnotes/wireshark-4.4.5.html
71. https://gitlab.com/wireshark/wireshark/-/issues/20392
72. https://gitlab.com/wireshark/wireshark/-/issues/20403
73. https://www.wireshark.org/docs/relnotes/wireshark-4.4.4.html
74. https://www.wireshark.org/security/wnpa-sec-2025-01
75. https://gitlab.com/wireshark/wireshark/-/issues/20373
76. https://gitlab.com/wireshark/wireshark/-/issues/20263
77. https://gitlab.com/wireshark/wireshark/-/issues/20300
78. https://gitlab.com/wireshark/wireshark/-/issues/20330
79. https://gitlab.com/wireshark/wireshark/-/issues/20354
80. https://gitlab.com/wireshark/wireshark/-/issues/20357
81. https://gitlab.com/wireshark/wireshark/-/issues/20359
82. https://gitlab.com/wireshark/wireshark/-/issues/20367
83. https://gitlab.com/wireshark/wireshark/-/issues/20386
84. https://gitlab.com/wireshark/wireshark/-/issues/20387
85. https://gitlab.com/wireshark/wireshark/-/issues/20389
86. https://gitlab.com/wireshark/wireshark/-/issues/20391
87. https://gitlab.com/wireshark/wireshark/-/issues/20394
88. https://www.wireshark.org/docs/relnotes/wireshark-4.4.3.html
89. https://gitlab.com/wireshark/wireshark/-/issues/20247
90. https://gitlab.com/wireshark/wireshark/-/issues/20276
91. https://gitlab.com/wireshark/wireshark/-/issues/20290
92. https://gitlab.com/wireshark/wireshark/-/issues/20304
93. https://gitlab.com/wireshark/wireshark/-/issues/20311
94. https://gitlab.com/wireshark/wireshark/-/issues/20313
95. https://gitlab.com/wireshark/wireshark/-/issues/20320
96. https://gitlab.com/wireshark/wireshark/-/issues/20326
97. https://www.wireshark.org/docs/relnotes/wireshark-4.4.2.html
98. https://www.wireshark.org/security/wnpa-sec-2024-14
99. https://gitlab.com/wireshark/wireshark/-/issues/20176
100. https://www.wireshark.org/security/wnpa-sec-2024-15
101. https://gitlab.com/wireshark/wireshark/-/issues/20214
102. https://gitlab.com/wireshark/wireshark/-/issues/19517
103. https://gitlab.com/wireshark/wireshark/-/issues/20041
104. https://gitlab.com/wireshark/wireshark/-/issues/20065
105. https://gitlab.com/wireshark/wireshark/-/issues/20066
106. https://gitlab.com/wireshark/wireshark/-/issues/20082
107. https://gitlab.com/wireshark/wireshark/-/issues/20099
108. https://gitlab.com/wireshark/wireshark/-/issues/20107
109. https://gitlab.com/wireshark/wireshark/-/issues/20108
110. https://gitlab.com/wireshark/wireshark/-/issues/20113
111. https://gitlab.com/wireshark/wireshark/-/issues/20124
112. https://gitlab.com/wireshark/wireshark/-/issues/20125
113. https://gitlab.com/wireshark/wireshark/-/issues/20126
114. https://gitlab.com/wireshark/wireshark/-/issues/20129
115. https://gitlab.com/wireshark/wireshark/-/issues/20134
116. https://gitlab.com/wireshark/wireshark/-/issues/20142
117. https://gitlab.com/wireshark/wireshark/-/issues/20156
118. https://gitlab.com/wireshark/wireshark/-/issues/20159
119. https://gitlab.com/wireshark/wireshark/-/issues/20163
120. https://gitlab.com/wireshark/wireshark/-/issues/20167
121. https://gitlab.com/wireshark/wireshark/-/issues/20169
122. https://gitlab.com/wireshark/wireshark/-/issues/20173
123. https://gitlab.com/wireshark/wireshark/-/issues/20174
124. https://gitlab.com/wireshark/wireshark/-/issues/20182
125. https://gitlab.com/wireshark/wireshark/-/issues/20183
126. https://gitlab.com/wireshark/wireshark/-/issues/20184
127. https://gitlab.com/wireshark/wireshark/-/issues/20187
128. https://gitlab.com/wireshark/wireshark/-/issues/20188
129. https://gitlab.com/wireshark/wireshark/-/issues/20190
130. https://gitlab.com/wireshark/wireshark/-/issues/20191
131. https://gitlab.com/wireshark/wireshark/-/issues/20192
132. https://gitlab.com/wireshark/wireshark/-/issues/20193
133. https://gitlab.com/wireshark/wireshark/-/issues/20204
134. https://gitlab.com/wireshark/wireshark/-/issues/20216
135. https://www.wireshark.org/docs/relnotes/wireshark-4.4.1.html
136. https://www.wireshark.org/security/wnpa-sec-2024-12
137. https://gitlab.com/wireshark/wireshark/-/issues/20026
138. https://www.wireshark.org/security/wnpa-sec-2024-13
139. https://gitlab.com/wireshark/wireshark/-/issues/20114
140. https://gitlab.com/wireshark/wireshark/-/issues/11176
141. https://gitlab.com/wireshark/wireshark/-/issues/14729
142. https://gitlab.com/wireshark/wireshark/-/issues/19854
143. https://gitlab.com/wireshark/wireshark/-/issues/19886
144. https://gitlab.com/wireshark/wireshark/-/issues/19930
145. https://gitlab.com/wireshark/wireshark/-/issues/20020
146. https://gitlab.com/wireshark/wireshark/-/issues/20021
147. https://gitlab.com/wireshark/wireshark/-/issues/20030
148. https://gitlab.com/wireshark/wireshark/-/issues/20031
149. https://gitlab.com/wireshark/wireshark/-/issues/20040
150. https://gitlab.com/wireshark/wireshark/-/issues/20044
151. https://gitlab.com/wireshark/wireshark/-/issues/20047
152. https://gitlab.com/wireshark/wireshark/-/issues/20049
153. https://gitlab.com/wireshark/wireshark/-/issues/20051
154. https://gitlab.com/wireshark/wireshark/-/issues/20052
155. https://gitlab.com/wireshark/wireshark/-/issues/20054
156. https://gitlab.com/wireshark/wireshark/-/issues/20055
157. https://gitlab.com/wireshark/wireshark/-/issues/20056
158. https://gitlab.com/wireshark/wireshark/-/issues/20057
159. https://gitlab.com/wireshark/wireshark/-/issues/20069
160. https://gitlab.com/wireshark/wireshark/-/issues/20071
161. https://gitlab.com/wireshark/wireshark/-/issues/20079
162. https://gitlab.com/wireshark/wireshark/-/issues/20082
163. https://gitlab.com/wireshark/wireshark/-/issues/20088
164. https://gitlab.com/wireshark/wireshark/-/issues/20090
165. https://gitlab.com/wireshark/wireshark/-/issues/20100
166. https://gitlab.com/wireshark/wireshark/-/issues/20110
167. https://www.wireshark.org/docs/relnotes/wireshark-4.4.0.html
168. https://www.wireshark.org/download.html
169. https://ask.wireshark.org/
170. https://lists.wireshark.org/lists/
171. https://gitlab.com/wireshark/wireshark/-/issues
172. https://sharkfest.wireshark.org
173. https://www.wireshark.org/certifications
174. https://wiresharkfoundation.org
175. https://www.wireshark.org/faq.html
Digests
wireshark-4.4.12.tar.xz: 46851012 bytes
SHA256(wireshark-4.4.12.tar.xz)=a83d0b616939f7a8fa4c1acbfd03e8d988a06aeed58c0042081cf0011b5b51fe
SHA1(wireshark-4.4.12.tar.xz)=2d3d0b429790fa07b97442146be71d24f0a5b455
Wireshark-4.4.12-x64.exe: 88301424 bytes
SHA256(Wireshark-4.4.12-x64.exe)=72e2a8b1f24f5e7a0573088be80dde1d3e89c787fa1204bc0b70169157d00bd8
SHA1(Wireshark-4.4.12-x64.exe)=d963bb2c2445d2463e52ddbdd18a724832dc5faa
Wireshark-4.4.12-arm64.exe: 69771592 bytes
SHA256(Wireshark-4.4.12-arm64.exe)=7fda6da11ad909866d962e2d92676776e1d16efeefa6fbe37bae4761073c865f
SHA1(Wireshark-4.4.12-arm64.exe)=49baa288918f4bc063f3d15f6ea368d5efc22953
Wireshark-4.4.12-x64.msi: 64827392 bytes
SHA256(Wireshark-4.4.12-x64.msi)=70afabd9256d12bada740ab4139003c94878016e5feffee7229676cf83d51d51
SHA1(Wireshark-4.4.12-x64.msi)=4a74619395a4c6a2d31514a177fe4c668b7b0697
WiresharkPortable64_4.4.12.paf.exe: 65112184 bytes
SHA256(WiresharkPortable64_4.4.12.paf.exe)=793675a5fbf6eaa24220e0d7f39e404122bde75744c6e6806161d853d52b8e99
SHA1(WiresharkPortable64_4.4.12.paf.exe)=a7414cc7432a2ed70f734ba8b21787d0c50415cb
Wireshark 4.4.12 Arm 64.dmg: 65867681 bytes
SHA256(Wireshark 4.4.12 Arm 64.dmg)=df982ac0d11858af3841392e727a2ce3907975acade760b381198c30c75304d1
SHA1(Wireshark 4.4.12 Arm 64.dmg)=1b18e005afa967c7f460122a5aaa1b3e06284296
Wireshark 4.4.12 Intel 64.dmg: 69596951 bytes
SHA256(Wireshark 4.4.12 Intel 64.dmg)=a9290733fa516f54bc7a4e8380b1a55cefd1f88277424f5f6b8c6832c0322ed6
SHA1(Wireshark 4.4.12 Intel 64.dmg)=244edcd926614c69d18a30f67ed2740ac2cb25ba
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_signature.asc
Description: OpenPGP digital signature
- Prev by Date: [Wireshark-announce] Wireshark 4.6.2 is now available
- Previous by thread: [Wireshark-announce] Wireshark 4.6.2 is now available
- Index(es):