Two case-insensitive comparisons on request-derived usernames outside the main authorization path in CUPS's scheduler (printer ACL validation and private-attribute filtering) could allow bypass of username-based access controls in certain configurations.
CVE-2026-87876
This low-severity CVE scores 3.0 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.0
- EG Score
- 3.0(medium)
- EG Risk
- 30(Track)EG Risk 30/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 computedSeverity30% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
September 9, 2026
Last Modified
September 10, 2026
References (5)
- linkhttps://access.redhat.com/security/cve/CVE-2026-87876
- linkhttps://bugzilla.redhat.com/show_bug.cgi?id=2530991
- linkhttps://github.com/OpenPrinting/cups/commit/88e67c00c130a45f3a1edf36686f7a0b2982fef8
- linkhttps://github.com/OpenPrinting/cups/commit/f56844dbe4a54a9f8e1aeb3b913fbee614156bdb
- linkhttps://github.com/OpenPrinting/cups/security/advisories/GHSA-r8jp-q6fh-g5r2
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 11× in last 7d / 21× 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-09-19 04:14 UTCEG score recompute
- 2026-09-19 04:14 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 08:54 UTCEG score recompute
- 2026-09-16 08:54 UTCVendor advisory
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-13 16:48 UTCEPSS rescore
- 2026-09-13 12:50 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 17:30 UTCEG score recompute
- 2026-09-10 00:32 UTCEG score recompute
- 2026-09-09 23:25 UTCEG score recompute
- 2026-09-09 19:29 UTCEG score recompute
- 2026-09-09 18:21 UTCEG score recompute
- 2026-09-09 17:28 UTCEG score recompute
- 2026-09-09 16:28 UTCEG score recompute
- 2026-09-09 16:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-87876?
When was CVE-2026-87876 disclosed?
Is CVE-2026-87876 actively exploited?
What is the CVSS score of CVE-2026-87876?
How do I remediate CVE-2026-87876?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-87876
Is Your Infrastructure Affected by CVE-2026-87876?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.