CVE-2021-3468

What it is

A flaw was found in avahi in versions 0.6 up to 0.8. The event used to signal the termination of the client connection on the avahi Unix socket is not correctly handled in the client_work function, allowing a local attacker to trigger an infinite loop. The highest threat from this vulnerability is to the availability of the avahi service, which becomes unresponsive after this flaw is triggered.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2021-06-02 16:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 04:05 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 5.5 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2021-06-02 16:15 UTC

Last modified

2026-06-17 04:05 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-835

Record status

Modified

Affected

• Avahi ≤ 0.8
• Debian Linux 9.0

Attack profile CVSS 3.1 · 5.5

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2021-3468.md and follow it. Check whether this project is affected by CVE-2021-3468. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge