# CVE-2025-9817: NULL Pointer Dereference in Wireshark > A NULL pointer dereference in the SSH dissector allows attackers to cause a denial of service in Wireshark. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 3 Sep 2025 - **Updated:** 27 Mar 2026 - **Also known as:** ALSA-2026:1714, AZL-66770, DEBIAN-CVE-2025-9817, GHSA-3mqq-9w3m-xpj8, OESA-2025-2263, OESA-2025-2264, OESA-2025-2265, OESA-2025-2266, OESA-2025-2267, RHSA-2026:1714, RHSA-2026:2763, RLSA-2026:1714, SUSE-SU-2025:03294-1, UBUNTU-CVE-2025-9817, openSUSE-SU-2025:15522-1 ## What is CVE-2025-9817? CVE-2025-9817 is a high-severity vulnerability in Wireshark Wireshark, published on 3 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description SSH dissector crash in Wireshark 4.4.0 to 4.4.8 allows denial of service Weakness: CWE-476 (NULL Pointer Dereference) ## Which versions are affected by CVE-2025-9817? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `wireshark` | AlmaLinux:10 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark-cli` | AlmaLinux:10 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark-devel` | AlmaLinux:10 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark` | Red Hat:enterprise_linux:10.1 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark-cli` | Red Hat:enterprise_linux:10.1 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark-cli-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark-devel` | Red Hat:enterprise_linux:10.1 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:4.4.2-3.el10_0.2 | | `wireshark-cli` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:4.4.2-3.el10_0.2 | | `wireshark-cli-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:4.4.2-3.el10_0.2 | | `wireshark-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:4.4.2-3.el10_0.2 | | `wireshark-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:4.4.2-3.el10_0.2 | | `wireshark-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:4.4.2-3.el10_0.2 | | `wireshark` | Rocky Linux:10 | All versions | 1:4.4.2-4.el10_1.2 | | `wireshark` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 4.2.13-150600.18.26.1 | | `wireshark` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 4.2.13-150600.18.26.1 | | `wireshark` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | All versions | 4.2.13-150600.18.26.1 | | `wireshark` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP7 | All versions | 4.2.13-150600.18.26.1 | | `wireshark` | openSUSE:Leap 15.6 | All versions | 4.2.13-150600.18.26.1 | | `wireshark` | openSUSE:Tumbleweed | All versions | 4.4.9-2.1 | Products: Wireshark Wireshark. ## How do I fix CVE-2025-9817? Upgrade to a fixed version. ## Is CVE-2025-9817 being exploited? There is no known exploitation of CVE-2025-9817 in the wild and no public exploit code. ## 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-2025-9817 and fix it if it is affected. What it is: CVE-2025-9817 is a high-severity vulnerability in Wireshark Wireshark, published on 3 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-9817 in the wild and no public exploit code. 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-2025-9817/ (Markdown: https://insights.sbomify.com/CVE-2025-9817/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9817 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9817 - OSV: https://osv.dev/vulnerability/CVE-2025-9817 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-9817/ Summaries are generated and may contain mistakes; the official description above is the record.