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.
CVE-2026-64611
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-23. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 23, 20262502799 – (CVE-2026-64611) CVE-2026-64611 libcupsfilters: cups-filters: libcupsfilters: CPU exhaustion via infinite loop in cfIEEE1284NormalizeMakeModel()
https://bugzilla.redhat.com/show_bug.cgi?id=2502799Vendor Advisories for CVE-2026-64611(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 05:47 UTCGHSA enrichment
- 2026-07-27 17:10 UTCEG score recompute
- 2026-07-27 17:10 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 04:33 UTCGHSA enrichment
- 2026-07-26 15:54 UTCEG score recompute
- 2026-07-26 15:54 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:16 UTCEG score recompute
- 2026-07-26 03:16 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 11:00 UTCEG score recompute
- 2026-07-23 10:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-835
Frequently asked(5)
What is CVE-2026-64611?
When was CVE-2026-64611 disclosed?
Is CVE-2026-64611 actively exploited?
What is the CVSS score of CVE-2026-64611?
How do I remediate CVE-2026-64611?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-64611
Is Your Infrastructure Affected by CVE-2026-64611?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.