---
id: CVE-2026-64611
title: >-
  Libcupsfilters: cups-filters: libcupsfilters: cpu exhaustion via infinite loop
  in cfieee1284normalizemakemodel()
summary: >-
  A flaw was found in libcupsfilters. The cfIEEE1284NormalizeMakeModel()
  function enters an infinite loop when processing a printer-advertised
  IEEE-1284 device ID with an empty model field, causing sustained CPU
  consumption. A network-adja…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cvssSource: cna
cwe:
  - CWE-835
vendor: Red Hat
product: libcupsfilters
affected:
  - libcupsfilters (all versions)
  - cups-filters
  - cups-filters
  - cups-filters
  - cups-filters
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-07-23T20:07:10.793765Z'
published: '2026-07-23'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T22:08:07.782Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-64611'
references:
  - url: 'https://access.redhat.com/errata/RHSA-2026:56965'
    label: 'RHSA-2026:56965'
  - url: 'https://access.redhat.com/security/cve/CVE-2026-64611'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2502799'
    label: RHBZ#2502799
  - url: >-
      https://github.com/OpenPrinting/libcupsfilters/security/advisories/GHSA-rcq7-rv5g-j3r4
tags:
  - cve.org
epss: 0.0063
epssPercentile: 0.50428
ingestedAt: '2026-11-05T23:41:31.958Z'
---

## Overview

A flaw was found in libcupsfilters. The cfIEEE1284NormalizeMakeModel() function enters an infinite loop when processing a printer-advertised IEEE-1284 device ID with an empty model field, causing sustained CPU consumption. A network-adjacent attacker could exploit this by broadcasting a specially crafted printer advertisement, leading to denial of service.

## Affected

- `libcupsfilters (all versions)`
- `cups-filters`
- `cups-filters`
- `cups-filters`
- `cups-filters`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

### Workarounds

If automatic network printer discovery is not strictly necessary for your environment, stopping the service completely eliminates the vulnerable attack surface.If you must use cups-browsed for legitimate operational reasons, you should prevent untrusted networks from feeding data to the daemon.