CVE-2025-68276 | Avahi has a reachable assertion in avahi_wide_area_scan_cache

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, an unprivileged local users can crash avahi-daemon (with wide-area disabled) by creating record browsers with the AVAHI_LOOKUP_USE_WIDE_AREA flag set via D-Bus. This can be done by either calling the RecordBrowserNew method directly or creating hostname/address/service resolvers/browsers that create those browsers internally themselves.

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-68276 is rated Low Risk (22.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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

Exploit prediction scoring system (EPSS) score for CVE-2025-68276

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.01% —

Full EPSS history (1 record total)

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

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

OS Trackers for CVE-2025-68276

vendor priority summary link
alpine medium CVE-2025-68276: 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-68276
debian not yet assigned CVE-2025-68276 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-68276
redhat medium — https://access.redhat.com/security/cve/CVE-2025-68276
suse medium CVE-2025-68276 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-68276/
ubuntu medium CVE-2025-68276 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-68276

Affected software / configurations for CVE-2025-68276

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-68276

cvelogic Threat Intelligence