CVE-2026-26198

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 43% 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, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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

Ormar is a async mini ORM for Python. In versions 0.9.9 through 0.22.0, when performing aggregate queries, Ormar ORM constructs SQL expressions by passing user-supplied column names directly into sqlalchemy.text() without any validation or sanitization. The min() and max() methods in the QuerySet class accept arbitrary string input as the column parameter. While sum() and avg() are partially protected by an is_numeric type check that rejects non-existent fields, min() and max() skip this validation entirely. As a result, an attacker-controlled string is embedded as raw SQL inside the aggregate function call. Any unauthorized user can exploit this vulnerability to read the entire database contents, including tables unrelated to the queried model, by injecting a subquery as the column parameter. Version 0.23.0 contains a patch.

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

Published

February 24, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

SQL Injection in aggregate functions min() and max() · Advisory · ormar-orm/ormar · GitHub

https://github.com/collerek/ormar/security/advisories/GHSA-xxh2-68g9-8jqr
github_release Patch Available

Fix critical vulnerability, drop Python 3.9, bugfixes

Patch available: collerek/ormar 0.23.0

https://github.com/collerek/ormar/releases/tag/0.23.0
github_commit Patch Available

commit a03bae14fe01 (collerek/ormar)

Patch available: collerek/ormar 0.23.0 (contains commit a03bae14fe01)

https://github.com/collerek/ormar/commit/a03bae14fe01358d3eaf7e319fcd5db2e4956b16

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ormar0.12.0-3 ... 0.24.0-2 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ormar0.11.2-1 ... 0.22.0-1 (11 versions)0.23.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
ormar0.10.0 ... 0.9.9 (40 versions)0.23.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 27× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:07 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-31 17:04 UTCOSV refresh
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 34 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 09:09 UTCEG score recompute
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 01:09 UTCEG score recompute
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-12 00:58 UTCEG score recompute
  14. 2026-08-11 13:42 UTCEPSS rescore
  15. 2026-08-11 06:39 UTCEG score recompute
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-09 19:52 UTCEG score recompute
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-09 08:46 UTCEG score recompute
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-07 20:54 UTCEG score recompute
  22. 2026-08-06 13:46 UTCEPSS rescore
  23. 2026-08-06 03:09 UTCEG score recompute
  24. 2026-08-05 19:17 UTCEPSS rescore
  25. 2026-08-04 15:10 UTCEPSS rescore
  26. 2026-08-04 06:00 UTCEG score recompute
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 19:44 UTCEG score recompute
  29. 2026-08-02 02:26 UTCEPSS rescore
  30. 2026-08-01 04:16 UTCEPSS rescore
  31. 2026-07-30 16:27 UTCEPSS rescore
  32. 2026-07-30 01:30 UTCEPSS rescore
  33. 2026-07-28 15:36 UTCEPSS rescore
  34. 2026-07-27 13:34 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-26198?
CVE-2026-26198 is a high vulnerability published on February 24, 2026. Ormar is a async mini ORM for Python. In versions 0.9.9 through 0.22.0, when performing aggregate queries, Ormar ORM constructs SQL expressions by passing user-supplied column names directly into sqlalchemy.text() without any validation or sanitization. The min() and max() methods in the QuerySet…
When was CVE-2026-26198 disclosed?
CVE-2026-26198 was first published in the National Vulnerability Database on February 24, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26198 actively exploited?
CVE-2026-26198 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 41.4% of all scored CVEs.
What is the CVSS score of CVE-2026-26198?
CVE-2026-26198 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-26198?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26198, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26198

Explore →

Is Your Infrastructure Affected by CVE-2026-26198?

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

Start Free Scan →Browse All CVEs