Advisory record · GHSA-xxh2-68g9-8jqr

ormar is vulnerable to SQL Injection through aggregate functions min() and max()

CVSS 9.8 CriticalCriticalEPSS 0.010 · 63rd percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ormarPyPI>=0.9.9, <0.23.00.23.0
Identifiers
GHSA-xxh2-68g9-8jqr · CVE-2026-26198 · PYSEC-2026-439
Weakness (CWE)
CWE-89
Published
29 Jun 2026
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The ormar package, versions 0.9.9 up to but not including 0.23.0, is vulnerable to SQL injection through the min() and max() aggregate functions, where a column name supplied as input is passed into raw SQL. An unauthenticated attacker who can reach an application endpoint that passes user input to these functions can run arbitrary SQL and read data from the database, including tables not tied to the queried model. Upgrade ormar to version 0.23.0 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.010, the 63rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:04 UTC First seen by agentprime
  2. 31 Oct 2026, 15:04 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.