CVE-2026-87803

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-10. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An authorization bypass vulnerability exists in the Countly Server DBViewer due to flawed sub-pipeline detection in the aggregation stage sanitizer. The /o/db aggregation endpoint parses user-controlled aggregation JSON and passes it through a stage sanitizer that determines whether a nested array is a sub-pipeline by checking if every element contains a key present in a hardcoded KNOWN_STAGE_OPERATORS set. If any element contains an unrecognized stage key, such as the undocumented MongoDB-internal $_internalInhibitOptimization, the sanitizer misclassifies the entire branch as a generic array and skips stage-level stripping for all sibling stages. This allows a non-admin user with DBViewer read permission to inject forbidden operators like $lookup inside $facet sub-pipelines, performing cross-collection joins into restricted collections. This leads to unauthorized read access to sensitive data including password-reset tokens (prid), enabling account takeover.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.3%
EPSS %ILE
21st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (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.

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 10, 2026

Last Modified

September 10, 2026

Advisory Details (1)

Auto-updated Sep 10, 2026
Patch available. Sources: github_pr.
GitHub pull request Patch Available

refactor(dbviewer): validate aggregation operators against an allow-list

Patch available: Countly/countly-server 25.03.53-LTS (PR #7868 merged 2026-08-25)

https://github.com/Countly/countly-server/pull/7868

Vendor Advisories for CVE-2026-87803(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 30× in last 7d / 112× 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.

Showing the most recent 100 of 126 refreshes 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 26 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-87803?
CVE-2026-87803 is a high-severity vulnerability; its CVE record was published on September 10, 2026. An authorization bypass vulnerability exists in the Countly Server DBViewer due to flawed sub-pipeline detection in the aggregation stage sanitizer. The /o/db aggregation endpoint parses user-controlled aggregation JSON and passes it through a stage sanitizer that determines whether a nested array…
When was the CVE record for CVE-2026-87803 published?
The CVE record for CVE-2026-87803 was published on September 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-87803 actively exploited?
CVE-2026-87803 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87803?
CVE-2026-87803 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-87803?
A fix for CVE-2026-87803 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-87803 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-87803

Explore →

Is Your Infrastructure Affected by CVE-2026-87803?

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

Book a Demo →Browse All CVEs