# CVE-2026-64611: Libcupsfilters: cups-filters: libcupsfilters: cpu exhaustion via infinite loop in cfieee1284normalizemakemodel()

> A network-adjacent attacker can cause CPU exhaustion and denial of service by broadcasting a crafted printer advertisement with an empty model field.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2026
- **Updated:** 19 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-64611, GHSA-m7r8-8qc5-j4jf, UBUNTU-CVE-2026-64611

## What is CVE-2026-64611?

CVE-2026-64611 is a high-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2026-64611?


## How do I fix CVE-2026-64611?

Apply the vendor's patch.

## Is CVE-2026-64611 being exploited?

There is no known exploitation of CVE-2026-64611 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64611 and fix it if it is affected.

What it is: CVE-2026-64611 is a high-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64611 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64611/ (Markdown: https://insights.sbomify.com/CVE-2026-64611/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64611
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64611
- OSV: https://osv.dev/vulnerability/CVE-2026-64611

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64611/
Summaries are generated and may contain mistakes; the official description above is the record.