Alpine Linux CUPS CVE-2026-55467

Cannot be specified from the available data - the entry gives no vulnerability description, affected configuration, protocol, or feature. To exploit CUPS flaws generally the attacker must be able to reach the CUPS service (local socket by default, or the network IPP listener / cups-browsed port 631 only if printer sharing or browsing is enabled), but whether THIS issue requires network reachability, a non-default sharing configuration, local access, or user interaction is not stated in the provided data and must be confirmed from the upstream CVE/OpenPrinting advisory.

Risk cannot be meaningfully quantified from the data provided. The only input is an Alpine Linux package-tracker entry stating that CUPS (Common UNIX Printing System) was fixed in 2.4.20-r0; there is no CVSS score, no CVSS vector, no CWE, no EPSS value, no KEV listing, no SSVC decision data, and no POC reference. Exploitation status is therefore 'no public exploit identified at time of analysis'. Because the vulnerability class (e.g. remote RCE in the IPP/cups-browsed listener versus a local privilege or info-leak bug) is unknown, it is impossible to distinguish a genuinely high-priority network-exploitable flaw from a low-impact local issue. CUPS has a notable recent history of serious network-reachable vulnerabilities (the 2024 cups-browsed/libcupsfilters chain), so this entry should NOT be dismissed, but equally must not be presented as critical absent the actual advisory. Action: treat as a standard distro package update and retrieve the upstream CVE record / OpenPrinting advisory and the Alpine security tracker entry to obtain the CVSS vector, CWE, and affected-component detail before prioritizing. All severity signals are currently MISSING, not low.

The specific attack path is undetermined because no vulnerability description beyond 'cups fixed in 2.4.20-r0' is available. If this follows the common CUPS pattern, an attacker reachable to the printing service could send a crafted IPP/network request or malicious printer data to trigger the flaw, but this is unconfirmed. No public proof-of-concept is referenced in the provided data.