CVE-2026-87875

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-75085 (ENISA EUVD)Source: ENISA EUVD

4.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

The cupsUTF32ToUTF8() function in CUPS's cups/transcode.c lacks a source-length bound and can read past the end of the source buffer, resulting in a heap out-of-bounds read. This is reachable via SNMP supply-description parsing in backend/snmp-supplies.c with attacker-controlled content.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/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)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
33rd
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 (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.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-11-05). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

September 9, 2026

Last Modified

November 6, 2026

Advisory Details (2)

Auto-updated Sep 9, 2026
Patch available. Sources: redhat, github.
GitHub advisoryMentions a patch (unverified)

Heap out-of-bounds read in cupsUTF32ToUTF8() via missing source-length bound — reachable from SNMP supply-description parsing (backend/snmp-supplies.c) · Advisory · OpenPrinting/cups · GitHub

https://github.com/OpenPrinting/cups/security/advisories/GHSA-559w-7676-3xrq
Red Hat

2530994 – (CVE-2026-87875) CVE-2026-87875 cups: OpenPrinting CUPS: Heap out-of-bounds read in cupsUTF32ToUTF8() via missing source-length bound

https://bugzilla.redhat.com/show_bug.cgi?id=2530994

Vendor Advisories for CVE-2026-87875(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 / EcosystemFix (by version range) / PatchReleasedSource
redhatcups-main-2.4.19-4.1.hum12026-09-11redhat

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
cups2.4.10-1 ... 2.4.7-3 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
cups2.4.10-3 ... 2.4.20-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
cups2.4.10-3 ... 2.4.20-1 (8 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 37× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 145 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 45 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-11-06 02:27 UTCEchelonGraph re-scored
  10. 2026-11-06 02:27 UTCVendor advisory
  11. 2026-11-06 01:23 UTCEchelonGraph re-scored
  12. 2026-11-06 01:23 UTCVendor advisory
  13. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-10-29 12:55 UTCOSV refresh
  22. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 75 more
  1. 2026-10-25 13:53 UTCEchelonGraph re-scored
  2. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-21 21:34 UTCEchelonGraph re-scored
  6. 2026-10-21 21:34 UTCVendor advisory
  7. 2026-10-21 20:26 UTCEchelonGraph re-scored
  8. 2026-10-21 20:26 UTCVendor advisory
  9. 2026-10-21 18:26 UTCEchelonGraph re-scored
  10. 2026-10-21 18:26 UTCVendor advisory
  11. 2026-10-21 18:01 UTCEchelonGraph re-scored
  12. 2026-10-21 18:01 UTCVendor advisory
  13. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-18 03:03 UTCEchelonGraph re-scored
  18. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-10-12 14:49 UTCEchelonGraph re-scored
  25. 2026-10-11 19:16 UTCEchelonGraph re-scored
  26. 2026-10-11 16:33 UTCEchelonGraph re-scored
  27. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  28. 2026-10-11 13:49 UTCEchelonGraph re-scored
  29. 2026-10-11 10:19 UTCEchelonGraph re-scored
  30. 2026-10-11 10:19 UTCVendor advisory
  31. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  32. 2026-10-10 08:40 UTCEchelonGraph re-scored
  33. 2026-10-10 08:40 UTCVendor advisory
  34. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  35. 2026-10-09 08:23 UTCEchelonGraph re-scored
  36. 2026-10-09 08:23 UTCVendor advisory
  37. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  38. 2026-10-08 08:06 UTCEchelonGraph re-scored
  39. 2026-10-08 08:06 UTCVendor advisory
  40. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  41. 2026-10-07 07:49 UTCEchelonGraph re-scored
  42. 2026-10-07 07:49 UTCVendor advisory
  43. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  44. 2026-10-06 07:32 UTCEchelonGraph re-scored
  45. 2026-10-06 07:32 UTCVendor advisory
  46. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  47. 2026-10-05 07:15 UTCEchelonGraph re-scored
  48. 2026-10-05 07:15 UTCVendor advisory
  49. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  50. 2026-10-04 06:58 UTCEchelonGraph re-scored
  51. 2026-10-04 06:58 UTCVendor advisory
  52. 2026-10-03 06:42 UTCEchelonGraph re-scored
  53. 2026-10-03 06:42 UTCVendor advisory
  54. 2026-10-02 06:26 UTCEchelonGraph re-scored
  55. 2026-10-02 06:26 UTCVendor advisory
  56. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  57. 2026-10-01 06:09 UTCEchelonGraph re-scored
  58. 2026-10-01 06:09 UTCVendor advisory
  59. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  60. 2026-09-30 05:53 UTCEchelonGraph re-scored
  61. 2026-09-30 05:53 UTCVendor advisory
  62. 2026-09-29 05:35 UTCEchelonGraph re-scored
  63. 2026-09-29 05:35 UTCVendor advisory
  64. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  65. 2026-09-28 05:18 UTCEchelonGraph re-scored
  66. 2026-09-28 05:18 UTCVendor advisory
  67. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  68. 2026-09-27 05:02 UTCEchelonGraph re-scored
  69. 2026-09-27 05:02 UTCVendor advisory
  70. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  71. 2026-09-26 04:11 UTCEchelonGraph re-scored
  72. 2026-09-26 04:11 UTCVendor advisory
  73. 2026-09-25 03:55 UTCEchelonGraph re-scored
  74. 2026-09-25 03:55 UTCVendor advisory
  75. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 22nd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-87875?
CVE-2026-87875 is a medium-severity vulnerability; its CVE record was published on September 9, 2026. The cupsUTF32ToUTF8() function in CUPS's cups/transcode.c lacks a source-length bound and can read past the end of the source buffer, resulting in a heap out-of-bounds read. This is reachable via SNMP supply-description parsing in backend/snmp-supplies.c with attacker-controlled content.
When was CVE-2026-87875 made public?
CVE-2026-87875 was made public on September 9, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on September 9, 2026. EchelonGraph's copy of the record carries a last-modified date of November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-87875 actively exploited?
CVE-2026-87875 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87875?
CVE-2026-87875 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-87875?
A fix for CVE-2026-87875 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-87875 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-87875

Explore →

Is Your Infrastructure Affected by CVE-2026-87875?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs