Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

GHSA-9j2c-x8qm-qmjq

MEDIUMFix: tortoise/tortoise-orm@91c3640

GHSA-9j2c-x8qm-qmjq is a medium-severity (CVSS 6.3) SQL Injection vulnerability in tortoise-orm. O3 Security confirms whether GHSA-9j2c-x8qm-qmjq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

SQL injection in Tortoise ORM

Also known asCVE-2020-11010PYSEC-2020-144
Published
Apr 20, 2020
Updated
Mar 13, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Mar 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐍tortoise-orm🐍tortoise-orm

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Various forms of SQL injection has been found, for MySQL and when filtering or doing mass-updates on char/text fields. SQLite & PostgreSQL was only affected when filtering with contains, starts_with or ends_with filters (and their case-insensitive counterparts)

Patches

Please upgrade to 0.15.23+ or 0.16.6+

For more information

If you have any questions or comments about this advisory:

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPItortoise-ormall versions0.15.23
🐍PyPItortoise-orm0.16.0&&< 0.16.60.16.6

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tortoise-orm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update tortoise-orm to 0.15.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9j2c-x8qm-qmjq is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-9j2c-x8qm-qmjq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9j2c-x8qm-qmjq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Various forms of SQL injection has been found, for MySQL and when filtering or doing mass-updates on char/text fields. SQLite & PostgreSQL was only affected when filtering with ``contains``, ``starts_with`` or ``ends_with`` filters (and their case-insensitive counterparts) ### Patches Please upgrade to 0.15.23+ or 0.16.6+ ### For more information If you have any questions or comments about this advisory: * Open an issue in [Github](https://github.com/tortoise/tortoise-orm/issues) * Chat to us on [Gitter](https://gitter.im/tortoise/community)
O3 Security · Impact-Aware SCA

Is GHSA-9j2c-x8qm-qmjq in your dependencies?

O3 detects GHSA-9j2c-x8qm-qmjq across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-9j2c-x8qm-qmjq: SQL injection in… | O3 Security