CVE-2026-93760

HIGHPre-NVD 8.28.2
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Mongoid does not restrict which query operators may come from caller-supplied filter data when an application hands that data to its query-building methods. In an application that forwards externally supplied filter parameters in this way, a party with no credentials may influence how the database evaluates the query. This may result in unintended disclosure of stored field values and in reduced database performance.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
41(Track)
EG Risk 41/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 computed
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
EPSS %ILE
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

SAML Login - MongoDB Jira - MongoDB Jira

https://jira.mongodb.org/browse/MONGOID-5994

Vendor Advisories for CVE-2026-93760(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 6× in last 7d / 6× 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-09-19 08:12 UTCGHSA enrichment
  2. 2026-09-18 19:07 UTCEG score recompute
  3. 2026-09-18 19:07 UTCGHSA enrichment
  4. 2026-09-18 18:27 UTCEG score recompute
  5. 2026-09-18 17:29 UTCEG score recompute
  6. 2026-09-18 17:29 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-93760?
CVE-2026-93760 is a high vulnerability published on September 18, 2026. Mongoid does not restrict which query operators may come from caller-supplied filter data when an application hands that data to its query-building methods. In an application that forwards externally supplied filter parameters in this way, a party with no credentials may influence how the database…
When was CVE-2026-93760 disclosed?
CVE-2026-93760 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-93760?
CVE-2026-93760 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-93760?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-93760, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-93760?

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