CVE-2026-34933 | Avahi: Reachable assertion in `transport_flags_from_domain()` via conflicting publish flags crashes avahi-daemon

Exp

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. Prior to version 0.9-rc4, any unprivileged local user can crash avahi-daemon by sending a single D-Bus method call with conflicting publish flags. This issue has been patched in version 0.9-rc4.

Published: 2026-04-03 Last update: 2026-04-13 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-34933 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-34933

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-34933

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-04 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-34933

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2026-34933

OS Trackers for CVE-2026-34933

vendor priority summary link
alpine — CVE-2026-34933: 1 source package rows (avahi); 54 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 1, open 53. https://security.alpinelinux.org/vuln/CVE-2026-34933
debian not yet assigned CVE-2026-34933 not yet assigned priority: Debian including 1 source packages (avahi), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2026-34933
redhat medium — https://access.redhat.com/security/cve/CVE-2026-34933
suse medium — https://www.suse.com/security/cve/CVE-2026-34933/
ubuntu medium CVE-2026-34933 medium priority: Ubuntu including 1 source packages (avahi), 9 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): released 9. https://ubuntu.com/security/CVE-2026-34933

Affected software / configurations for CVE-2026-34933

Vendor Product Version Raw CPE
avahi avahi < 0.9 cpe:2.3:a:avahi:avahi:*:*:*:*:*:*:*:*
avahi avahi 0.9 cpe:2.3:a:avahi:avahi:0.9:rc1:*:*:*:*:*:*
avahi avahi 0.9 cpe:2.3:a:avahi:avahi:0.9:rc2:*:*:*:*:*:*
avahi avahi 0.9 cpe:2.3:a:avahi:avahi:0.9:rc3:*:*:*:*:*:*

References for CVE-2026-34933

cvelogic Threat Intelligence