# CVE-2026-0962: Out-of-bounds Write in Wireshark

> An out-of-bounds write in the SOME/IP-SD dissector allows attackers to crash Wireshark, causing a denial of service.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Jan 2026
- **Updated:** 27 Mar 2026
- **Also known as:** AZL-74543, DEBIAN-CVE-2026-0962, GHSA-fxww-56j7-2rh4, UBUNTU-CVE-2026-0962

## What is CVE-2026-0962?

CVE-2026-0962 is a medium-severity memory corruption vulnerability in Wireshark Wireshark, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SOME/IP-SD protocol dissector crash in Wireshark 4.6.0 to 4.6.2 and 4.4.0 to 4.4.12 allows denial of service

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-0962?

It affects 1 product.


Products: Wireshark Wireshark.

## How do I fix CVE-2026-0962?

Upgrade to a fixed version.

## Is CVE-2026-0962 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0962 exists.

## Other vulnerabilities in Wireshark Wireshark

- [CVE-2011-0444](https://insights.sbomify.com/CVE-2011-0444/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2994](https://insights.sbomify.com/CVE-2010-2994/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2995](https://insights.sbomify.com/CVE-2010-2995/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1266](https://insights.sbomify.com/CVE-2009-1266/): Other in n/a (critical 10.0)
- [CVE-2009-1210](https://insights.sbomify.com/CVE-2009-1210/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0962 and fix it if it is affected.

What it is: CVE-2026-0962 is a medium-severity memory corruption vulnerability in Wireshark Wireshark, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0962 exists.

Affected product: Wireshark Wireshark. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0962/ (Markdown: https://insights.sbomify.com/CVE-2026-0962/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0962
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0962
- OSV: https://osv.dev/vulnerability/CVE-2026-0962

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0962/
Summaries are generated and may contain mistakes; the official description above is the record.