CVE-2026-93758

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

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

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

An insecure direct object reference in the nested attributes handling of the Mongoid object-document mapper may allow a user with basic application privileges to reference a record identifier that is not their own. Processing such a request can cause that record to be looked up without the usual ownership or scoping restrictions, then updated and linked to the requesting user's own record. This may result in unintended disclosure and unauthorized modification of data belonging to other users of the application.

CVSS v3
8.1
EG Score
8.1(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
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
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-5992

Vendor Advisories for CVE-2026-93758(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 12× in last 7d / 12× 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-20 23:11 UTCEG score recompute
  2. 2026-09-20 23:11 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 10:09 UTCGHSA enrichment
  5. 2026-09-19 21:09 UTCEG score recompute
  6. 2026-09-19 21:08 UTCGHSA enrichment
  7. 2026-09-19 08:07 UTCGHSA enrichment
  8. 2026-09-18 19:07 UTCEG score recompute
  9. 2026-09-18 19:07 UTCGHSA enrichment
  10. 2026-09-18 17:25 UTCEG score recompute
  11. 2026-09-18 17:05 UTCEG score recompute
  12. 2026-09-18 17:04 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-93758?
CVE-2026-93758 is a high vulnerability published on September 18, 2026. An insecure direct object reference in the nested attributes handling of the Mongoid object-document mapper may allow a user with basic application privileges to reference a record identifier that is not their own. Processing such a request can cause that record to be looked up without the usual…
When was CVE-2026-93758 disclosed?
CVE-2026-93758 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.
Is CVE-2026-93758 actively exploited?
CVE-2026-93758 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.7% of all scored CVEs.
What is the CVSS score of CVE-2026-93758?
CVE-2026-93758 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-93758?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-93758, 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-93758

Explore →

Is Your Infrastructure Affected by CVE-2026-93758?

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

Start Free Scan →Browse All CVEs