CVE-2025-68471 | Avahi has a reachable assertion in lookup_start

Exp

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In 0.9-rc2 and earlier, avahi-daemon can be crashed by sending 2 unsolicited announcements with CNAME resource records 2 seconds apart.

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

CVE-2025-68471 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.03%). 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-2025-68471

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-2025-68471

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-01-13 — 0.03% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-68471

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2025-68471

OS Trackers for CVE-2025-68471

vendor priority summary link
alpine medium CVE-2025-68471: 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 2, open 52. https://security.alpinelinux.org/vuln/CVE-2025-68471
debian not yet assigned CVE-2025-68471 not yet assigned priority: Debian including 1 source packages (avahi), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-68471
redhat medium — https://access.redhat.com/security/cve/CVE-2025-68471
suse medium CVE-2025-68471 severity moderate: SUSE including 356 source package names (2.1.3-6.129:avahi-0.8-7.1, 2.1.3-6.129:libavahi-client3-0.8-7.1, …), 762 product×package rows across 164 product lines (Container suse/manager/5.0/x86_64/server, Container suse/multi-linux-manager/5.1/x86_64/server, … (164 product lines)): Fixed 510, Known Affected 231, First Fixed 21. https://www.suse.com/security/cve/CVE-2025-68471/
ubuntu medium CVE-2025-68471 medium priority: Ubuntu including 1 source packages (avahi), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): released 7, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2025-68471

Affected software / configurations for CVE-2025-68471

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:*:*:*:*:*:*

References for CVE-2025-68471

cvelogic Threat Intelligence