Avahi denial of service via malformed mDNS record names
- Exploited
- No known exploitation
- Fix
- Fixed in 0.9-rc5
- Who is exposed
- Not reported
Summary
Avahi's avahi-daemon on NetBSD crashes when it receives resource records whose names contain bytes at or above 128. An attacker on the same local network can send such records without logging in or any user action, crashing the daemon and causing a denial of service.
Written by a model
Original description
Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In 0.9-rc4 and earlier on NetBSD architectures such as x86_64 where char is signed and the ctype guard-page change is present, avahi_domain_hash can pass a negative value to tolower when a resource-record name contains a byte at or above 128. The invalid ctype input reliably raises SIGSEGV, allowing a remote peer on the local network to crash the Avahi daemon. This issue is fixed with 0.9-rc5.
What to do
Upgrade to a fixed version: 0.9-rc5.
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-58406 (avahi-daemon crashes on receiving resource records where names contain bytes >= 128 (on NetBSD)), 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-58406 (entry last updated 2026-11-20):
Affected:
- avahi avahi: fixed in 0.9-rc5
Fixed versions: 0.9-rc5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-58406 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-58406 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://github.com/avahi/avahi/security/advisories/GHSA-8pmv-23p5-92mw
- https://github.com/avahi/avahi/pull/940
- https://github.com/avahi/avahi/commit/7730ce3f02a6a50f059934670f16ff636711aac4
- https://github.com/avahi/avahi/commit/92b659633ef0019f3202f00c9573cbfcf010630c
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-58406
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-58406"}.Affected versions
- avahi avahifixed in 0.9-rc5
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. 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 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · avahi/avahi · Advisory GHSA-8pmv-23p5-92mw |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-58406 |
| Record | NVD · CVE-2026-58406 |
| Other links 3 | |
| Repository | GitHub · avahi/avahi · Pull request #940 |
| Repository | GitHub · avahi/avahi · Commit 7730ce3f |
| Repository | GitHub · avahi/avahi · Commit 92b65963 |
Questions about CVE-2026-58406
Is CVE-2026-58406 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-58406?
avahi: before 0.9-rc5.
Source: cve.now feed data
How do I fix CVE-2026-58406?
Upgrade to a fixed version: 0.9-rc5.
Source: cve.now feed data
Related
- CVE-2026-24401Avahi has Uncontrolled Recursion in lookup_handle_cname function
- CVE-2025-68471Avahi has a reachable assertion in lookup_start
- CVE-2025-68468Avahi has a reachable assertion in lookup_multicast_callback
- CVE-2023-38473Reachable assertion in avahi_alternative_host_name
- CVE-2023-38472Reachable assertion in avahi_rdata_parse
- CVE-2023-38471Reachable assertion in dbus_set_host_name
No corrections so far. Something wrong on this page? Report an error.