OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. Prior to 2.4.20, copy_banner() in scheduler/ipp.c uses the attacker-controlled IPP attributes-natural-language value as a directory component beneath DataDir/banners when processing a job-sheets banner. The job-sheets value must first match a registered banner basename, and the traversed path must contain a matching reachable basename; selecting an arbitrary target as demonstrated additionally requires pre-positioned path state such as a symlink with that basename. Subject to the scheduler's filesystem and sandbox access, path separators in the language value can escape the intended banner directory, make the root scheduler open the reachable file, and copy its bytes into a job-sheet spool object that a configured backend can deliver to an attacker-observable endpoint. This issue is fixed in version 2.4.20.
CVE-2026-61702
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-102208 (ENISA EUVD)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 55EG Risk 55/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 36th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 15, 2026
Last Modified
October 28, 2026
Advisory Details (4)
Auto-updated Oct 15, 2026v2.4.20
Patch available: OpenPrinting/cups v2.4.20
https://github.com/OpenPrinting/cups/releases/tag/v2.4.20commit 665042823461 (OpenPrinting/cups)
Fix landed in OpenPrinting/cups commit 665042823461 — awaiting tagged release
https://github.com/OpenPrinting/cups/commit/6650428234616a97d3298e0e2d4419c62c1339d2commit 08a8a277ce2a (OpenPrinting/cups)
Patch available: OpenPrinting/cups v2.4.20 (contains commit 08a8a277ce2a)
https://github.com/OpenPrinting/cups/commit/08a8a277ce2a8948a1af33552247a1ac53b72df3CVE-2026-61702: root-side banner file disclosure · Advisory · OpenPrinting/cups · GitHub
https://github.com/OpenPrinting/cups/security/advisories/GHSA-gq9p-4w7m-2f5gVendor Advisories for CVE-2026-61702(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | cups-main-2.4.19-4.6.hum1 | 2026-10-17 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 29× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-28 21:28 UTCEG score recompute
- 2026-10-28 21:28 UTCVendor advisory
- 2026-10-28 20:26 UTCEG score recompute
- 2026-10-28 20:25 UTCEG score recompute
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-28 15:55 UTCOSV refresh
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 14:14 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-20 19:26 UTCEG score recompute
- 2026-10-20 19:26 UTCVendor advisory
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-18 03:25 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 37th percentile
Show 4 moreShow fewer
- 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-15 18:29 UTCEG score recompute
- 2026-10-15 17:23 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
- 2026-10-15 17:22 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
3 shownredhat:RHSA-2026:84421
Frequently asked(5)
What is CVE-2026-61702?
When was the CVE record for CVE-2026-61702 published?
Is CVE-2026-61702 actively exploited?
What is the CVSS score of CVE-2026-61702?
How do I remediate CVE-2026-61702?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61702
Is Your Infrastructure Affected by CVE-2026-61702?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.