Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-26198: Ormar is a async mini ORM for Python

63
This week
CRITICAL 9.8REMOTEUPGRADE

CVE-2026-26198 is a critical-severity flaw (CVSS 9.8) affecting ormar. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 tha

Why this priority

  • Critical severity
  • Public exploit reference
  • CISA SSVC: automatable with total technical impact
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.0% (top 37%)
CISA exploited listNo
WeaknessCWE-89
Published2026-02-24
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: collerek

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

collerek ormar UPGRADE
Affected: >= 0.9.9 and < 0.23.0
Fixed in: 0.23.0
Safe to downgrade to: a release before 0.9.9
1. Check installed version
pip show ormar
2. UPGRADE to 0.23.0
pip install --upgrade "ormar>=0.23.0"
3. If no update is available yet, DOWNGRADE to a release before 0.9.9
pip index versions ormar pip install "ormar<0.9.9"
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Python (pip) · ormar · FIXED · 0.23.0 · vulnerable: >= 0.9.9, <= 0.22.0 · source
pip install --upgrade "ormar>=0.23.0" pip show ormar
Fedora 46 · opensips · FIXED · 4.0.3-1.fc46 · FEDORA-2026-6700a0026c · source
sudo dnf upgrade --advisory=FEDORA-2026-6700a0026c
Fedora ELN · ibus-typing-booster · FIXED · 2.31.3-1.eln159 · FEDORA-2026-c895c68d60 · source
sudo dnf upgrade --advisory=FEDORA-2026-c895c68d60
Debian 12 · ormar · NO FIX YET

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-26198?

ormar: upgrade to 0.23.0. Exact commands for each OS are on this page.

Is CVE-2026-26198 being exploited?

CVE-2026-26198 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-26198 affect?

CVE-2026-26198 affects ormar. Severity is critical (CVSS 9.8). 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 o

How urgent is CVE-2026-26198?

Priority 63/100. Critical severity; Public exploit reference; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action

Software pages

Python vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.