Skip to main content
Menu
CVEs

NULL Pointer Dereference in Wireshark

CVE-2026-130461Published , updated

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.6.10, 4.4.20
Who is exposed
Not reported

Summary

A NULL pointer dereference in the IEEE 1609.2 protocol dissector of Wireshark, from Wireshark Foundation, can crash the program and cause a denial of service. An attacker can trigger it remotely, without logging in, but a user must take an action, such as opening a crafted capture or packet, for the attack to work.

Written by a model

Original description

IEEE 1609.2 protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

What to do

Upgrade to a fixed version: 4.6.10, 4.4.20.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130461 (NULL Pointer Dereference in Wireshark), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130461 (entry last updated 2026-11-20):
Affected:
- Wireshark Foundation Wireshark: from 4.6.0, fixed in 4.6.10; from 4.4.0, fixed in 4.4.20
Fixed versions: 4.6.10, 4.4.20.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130461 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130461 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wireshark.org/security/wnpa-sec-2026-119.html
- https://gitlab.com/wireshark/wireshark/-/work_items/21640
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130461
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130461"}.

Affected versions

cve.now Index

14Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkwireshark.org · security/wnpa-sec-2026-119.html
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130461
RecordNVD · CVE-2026-130461
Other links 1
Linkgitlab.com · wireshark/wireshark/-/work_items/21640

Questions about CVE-2026-130461

Is CVE-2026-130461 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-130461?

Wireshark: from 4.6.0 before 4.6.10; from 4.4.0 before 4.4.20.

Source: cve.now feed data

How do I fix CVE-2026-130461?

Upgrade to a fixed version: 4.6.10, 4.4.20.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.