Skip to main content
Menu
CVEs

Avahi denial of service in D-Bus record browser handling

CVE-2026-59987Published , updated

5.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 0.9-rc5
Who is exposed
Not reported

Summary

Avahi, the software that handles service discovery on a local network, is affected. A local user with low privileges can send a crafted request over D-Bus that crashes the Avahi daemon, 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, org.freedesktop.Avahi.Server.RecordBrowserNew accepts a domain-name value that avahi_is_valid_domain_name considers valid even though avahi_normalize_name_strdup cannot normalize it. The resulting null key reaches the key assertion in dbus_prepare_record_browser_object. A local low-privileged D-Bus client can trigger the mismatch and terminate the Avahi daemon, causing denial of service. The issue is fixed in 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-59987 (Avahi: Reachable assertion in dbus_prepare_record_browser_object), 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-59987 (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-59987 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-59987 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-4v6h-9g73-wm5j
- https://github.com/avahi/avahi/pull/939
- https://github.com/avahi/avahi/commit/cfeef2a28e260c67caac4b88440729c744cb24b6
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-59987
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-59987"}.

Affected versions

cve.now Index

6Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.5/10CVSS 5.5
  • No patch0/5No signal

What would change the score

  • Would score about 61 if added to CISA KEV
  • Would score about 56 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

Timeline

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

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · avahi/avahi · Advisory GHSA-4v6h-9g73-wm5j
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-59987
RecordNVD · CVE-2026-59987
Other links 2
RepositoryGitHub · avahi/avahi · Pull request #939
RepositoryGitHub · avahi/avahi · Commit cfeef2a2

Questions about CVE-2026-59987

Is CVE-2026-59987 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-59987?

avahi: before 0.9-rc5.

Source: cve.now feed data

How do I fix CVE-2026-59987?

Upgrade to a fixed version: 0.9-rc5.

Source: cve.now feed data

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