CVE-2026-87875

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: Elevated riskExposed 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/100CISA SSVC

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 computed
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 9, 2026

Last Modified

September 12, 2026

Advisory Details (2)

Auto-updated Sep 9, 2026
🔬 Proof of concept available. Patch available. Sources: redhat, github.
github Patch Available🟡 PoC Available

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
redhat

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(1)

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 (27 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
cups2.4.10-3 ... 2.4.18-1 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
cups2.4.10-3 ... 2.4.18-1 (7 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 18× in last 7d / 74× 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.

  1. 2026-10-05 07:15 UTCEG score recompute
  2. 2026-10-05 07:15 UTCVendor advisory
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 06:58 UTCEG score recompute
  5. 2026-10-04 06:58 UTCVendor advisory
  6. 2026-10-03 06:42 UTCEG score recompute
  7. 2026-10-03 06:42 UTCVendor advisory
  8. 2026-10-02 06:26 UTCEG score recompute
  9. 2026-10-02 06:26 UTCVendor advisory
  10. 2026-10-01 19:51 UTCEPSS rescore
  11. 2026-10-01 06:09 UTCEG score recompute
  12. 2026-10-01 06:09 UTCVendor advisory
  13. 2026-09-30 15:04 UTCEPSS rescore
  14. 2026-09-30 05:53 UTCEG score recompute
  15. 2026-09-30 05:53 UTCVendor advisory
  16. 2026-09-29 05:35 UTCEG score recompute
  17. 2026-09-29 05:35 UTCVendor advisory
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 05:18 UTCEG score recompute
  20. 2026-09-28 05:18 UTCVendor advisory
  21. 2026-09-27 13:48 UTCEPSS rescore
  22. 2026-09-27 05:02 UTCEG score recompute
  23. 2026-09-27 05:02 UTCVendor advisory
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-26 04:11 UTCEG score recompute
Show 49 more
  1. 2026-09-26 04:11 UTCVendor advisory
  2. 2026-09-25 03:55 UTCEG score recompute
  3. 2026-09-25 03:55 UTCVendor advisory
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 03:39 UTCEG score recompute
  6. 2026-09-24 03:39 UTCVendor advisory
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-23 03:22 UTCEG score recompute
  9. 2026-09-23 03:22 UTCVendor advisory
  10. 2026-09-22 16:01 UTCEPSS rescore
  11. 2026-09-22 03:06 UTCEG score recompute
  12. 2026-09-22 03:06 UTCVendor advisory
  13. 2026-09-21 21:09 UTCEPSS rescore
  14. 2026-09-21 02:49 UTCEG score recompute
  15. 2026-09-21 02:49 UTCVendor advisory
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-20 02:32 UTCEG score recompute
  18. 2026-09-20 02:32 UTCVendor advisory
  19. 2026-09-19 02:15 UTCEG score recompute
  20. 2026-09-19 02:15 UTCVendor advisory
  21. 2026-09-18 19:28 UTCEPSS rescore
  22. 2026-09-18 01:59 UTCEG score recompute
  23. 2026-09-18 01:59 UTCVendor advisory
  24. 2026-09-17 19:32 UTCEPSS rescore
  25. 2026-09-17 01:42 UTCEG score recompute
  26. 2026-09-17 01:42 UTCVendor advisory
  27. 2026-09-16 14:09 UTCEPSS rescore
  28. 2026-09-16 05:15 UTCEPSS rescore
  29. 2026-09-16 01:26 UTCEG score recompute
  30. 2026-09-16 01:26 UTCVendor advisory
  31. 2026-09-15 03:12 UTCEPSS rescore
  32. 2026-09-15 01:10 UTCVendor advisory
  33. 2026-09-14 00:53 UTCEG score recompute
  34. 2026-09-14 00:53 UTCVendor advisory
  35. 2026-09-13 00:37 UTCEG score recompute
  36. 2026-09-13 00:37 UTCVendor advisory
  37. 2026-09-12 00:18 UTCEG score recompute
  38. 2026-09-11 23:59 UTCEG score recompute
  39. 2026-09-11 14:53 UTCEPSS rescore
  40. 2026-09-11 14:53 UTCEPSS rescore
  41. 2026-09-11 10:42 UTCEG score recompute
  42. 2026-09-10 10:25 UTCEG score recompute
  43. 2026-09-09 23:31 UTCEG score recompute
  44. 2026-09-09 22:32 UTCEG score recompute
  45. 2026-09-09 18:28 UTCEG score recompute
  46. 2026-09-09 18:00 UTCEG score recompute
  47. 2026-09-09 17:28 UTCEG score recompute
  48. 2026-09-09 16:28 UTCEG score recompute
  49. 2026-09-09 16:25 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-87875?
CVE-2026-87875 is a medium vulnerability 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 disclosed?
CVE-2026-87875 was first published on September 9, 2026, with the most recent update on September 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (30th 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