CriticalGHSA-887w-45rq-vxgfCVE-2019-7164PYSEC-2019-123

SQLAlchemy vulnerable to SQL Injection via order_by parameter

Published 16 Apr 2019 · Updated 9 Jun 2026

Is your project on an affected sqlalchemy?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.3.0b3
Fixed in
1.3.0b3
Update to the fixed version for your release line, for example:pip install 'sqlalchemy>=1.3.0b3'

Details

SQLAlchemy before 1.3.0b3 allows SQL Injection via the order_by parameter. The fix (commit 30307c4) was applied only to the main branch and was never backported to the 1.2.x release line; all 1.2.x versions remain vulnerable.

Is GHSA-887w-45rq-vxgf in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected sqlalchemy, and gives you the command that fixes it.

More advisories for sqlalchemy

  • CriticalCVE-2012-0805SQLAlchemy vulnerable to SQL injection · 14 May 2022
  • CriticalCVE-2019-7548SQLAlchemy is vulnerable to SQL Injection via group_by parameter · 16 Apr 2019
sqlalchemy security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.