CVE-2026-26198
Critical SQL injection in Ormar min/max aggregate allows full DB read.
Is CVE-2026-26198 being exploited?
Not confirmed. CVE-2026-26198 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.92% probability of exploitation in the next 30 days.
How severe is CVE-2026-26198?
CVE-2026-26198 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-26198?
Yes. A fix has been recorded for CVE-2026-26198. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-26198 affect?
CVE-2026-26198 affects Ormar ORM (Python), v0.9.9 - v0.22.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-26198?
Upgrade to 0.23.0+; audit aggregate queries
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled column in min/max aggregates injects raw SQL; can disclose entire database.
Patch when possible
- affected>= 0.9.9 and < 0.23.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.