CVE-2026-84993

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

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

MikroORM is a TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Prior to 6.6.16 and 7.1.7, the shared SQL layer validates the field key of an orderBy clause but does not validate its direction value before AbstractSqlPlatform.getOrderByExpression concatenates it into an ORDER BY clause. Applications that bind attacker-controlled request data to the direction in em.find(), em.findOne(), em.findAndCount(), QueryBuilder.orderBy(), or QueryBuilderHelper.getQueryOrderFromObject() can permit a raw SQL fragment that performs blind or boolean extraction of data available to the database account. The BaseMySqlPlatform and MsSqlPlatform fallthrough paths have the same behavior, affecting SQLite, PostgreSQL, MySQL, MariaDB, MSSQL, libSQL, and Oracle drivers, while MongoDB is not affected. This issue is fixed in versions 6.6.16 and 7.1.7.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (7)

Auto-updated Sep 16, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v7.1.7

Patch available: mikro-orm/mikro-orm v7.1.7

https://github.com/mikro-orm/mikro-orm/releases/tag/v7.1.7
github_release Patch Available

v6.6.16

Patch available: mikro-orm/mikro-orm v6.6.16

https://github.com/mikro-orm/mikro-orm/releases/tag/v6.6.16
github_commit Patch Available

commit 89e5546bf8e1 (mikro-orm/mikro-orm)

Patch available: mikro-orm/mikro-orm v6.6.16 (contains commit 89e5546bf8e1)

https://github.com/mikro-orm/mikro-orm/commit/89e5546bf8e10f8465682016a3bdf622ff55d8c5
github_commit Patch Available

commit 3aba926fd071 (mikro-orm/mikro-orm)

Patch available: mikro-orm/mikro-orm v7.1.7 (contains commit 3aba926fd071)

https://github.com/mikro-orm/mikro-orm/commit/3aba926fd07156f5e1ebf06294fd77ee1215bad5
github_pr Patch Available

fix(sql): validate order by direction against known values

Patch available: mikro-orm/mikro-orm v6.6.16 (PR #7997 merged 2026-07-17)

https://github.com/mikro-orm/mikro-orm/pull/7997
github_pr Patch Available

fix(sql): validate order by direction against known values

Patch available: mikro-orm/mikro-orm v7.1.7 (PR #7996 merged 2026-07-17)

https://github.com/mikro-orm/mikro-orm/pull/7996
github Patch Available

SQL injection via unvalidated order direction in orderBy · Advisory · mikro-orm/mikro-orm · GitHub

https://github.com/mikro-orm/mikro-orm/security/advisories/GHSA-7j79-7q93-6v69

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 20× 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-25 05:10 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-24 03:52 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-23 02:28 UTCEG score recompute
  6. 2026-09-22 16:01 UTCEPSS rescore
  7. 2026-09-22 01:10 UTCEG score recompute
  8. 2026-09-21 21:09 UTCEPSS rescore
  9. 2026-09-20 23:51 UTCEG score recompute
  10. 2026-09-20 20:16 UTCEPSS rescore
  11. 2026-09-19 22:32 UTCEG score recompute
  12. 2026-09-18 21:14 UTCEG score recompute
  13. 2026-09-18 19:28 UTCEPSS rescore
  14. 2026-09-17 19:43 UTCEG score recompute
  15. 2026-09-17 19:32 UTCEPSS rescore
  16. 2026-09-16 18:24 UTCEG score recompute
  17. 2026-09-16 17:50 UTCEG score recompute
  18. 2026-09-16 17:30 UTCEG score recompute
  19. 2026-09-16 16:36 UTCEG score recompute
  20. 2026-09-16 16:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84993?
CVE-2026-84993 is a medium vulnerability published on September 16, 2026. MikroORM is a TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Prior to 6.6.16 and 7.1.7, the shared SQL layer validates the field key of an orderBy clause but does not validate its direction value before AbstractSqlPlatform.getOrderByExpression concatenates…
When was CVE-2026-84993 disclosed?
CVE-2026-84993 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84993 actively exploited?
CVE-2026-84993 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.4% of all scored CVEs.
What is the CVSS score of CVE-2026-84993?
CVE-2026-84993 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-84993?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84993, 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-84993

Explore →

Is Your Infrastructure Affected by CVE-2026-84993?

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

Book a Demo →Browse All CVEs