CVE-2025-68276VulnerabilityPublished 28 Apr 2026Updated 5 Oct 2026

Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

Not known to be exploited.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

Description

This update includes the following RPMs: avahi: * avahi-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-autoipd-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-compat-howl-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-compat-howl-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-compat-libdns_sd-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-compat-libdns_sd-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-dnsconfd-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-glib-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-glib-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-gobject-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-gobject-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-libs-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-qt3-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-qt3-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-qt4-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-qt4-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-qt5-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-qt5-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-sharp-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-tools-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-ui-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-ui-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-ui-gtk3-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-ui-sharp-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-ui-sharp-devel-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-ui-tools-0.9~rc4-0.1.hum1 (aarch64, x86_64) * avahi-0.9~rc4-0.1.hum1.src (src) Security Fix(es): avahi: * CVE-2025-68276 * CVE-2025-68468 * CVE-2025-68471 * CVE-2026-24401 * CVE-2026-34933

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
Implementation · Input Validation
Perform input validation on user data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-674Uncontrolled Recursion (opens in a new tab)
Class weakness
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Implementation
Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.
Implementation
Increase the stack size.
Attack patterns
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1288Improper Validation of Consistency within Input (opens in a new tab)
Base weakness
The product receives a complex input with multiple elements or fields that must be consistent with each other, but it does not validate or incorrectly validates that the input is actually consistent.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Description

WeaknessesCWE-617, CWE-674, CWE-1288

Technical details

References

Community reviews

Related threats