TypeORM: SQL Injection in UpdateQueryBuilder/SoftDeleteQueryBuilder orderBy (MySQL/MariaDB)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact Blind SQL injection vulnerability in UpdateQueryBuilder and SoftDeleteQueryBuilder affecting MySQL and MariaDB users. UpdateQueryBuilder and SoftDeleteQueryBuilder (including their addOrderBy variants) do not validate the order parameter against an allowlist of permitted values (ASC/DESC). The caller-supplied value is stored verbatim and concatenated directly into the generated SQL string without quoting or parameterization. SelectQueryBuilder.orderBy performs this validation correctly; the affected builders do not. If any code path passes user-controlled input to orderBy/addOrderBy on an update or soft-delete query, an attacker can inject arbitrary SQL via the sort direction — even when the column name itself is hardcoded. Demonstrated impact includes: - Data exfiltration via time-based blind extraction (e.g. using SLEEP() to infer secret values bit by bit) - Row targeting manipulation in queries using LIMIT patterns - Denial of service via SLEEP()-based query exhaustion CVSS…

Published by the source

19 Jun 2026, 19:18 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:56 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9ggv-8w38-r7pm

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9ggv-8w38-r7pm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-9ggv-8w38-r7pm

Advisory: TypeORM: SQL Injection in UpdateQueryBuilder/SoftDeleteQueryBuilder orderBy (MySQL/MariaDB)
IDs: GHSA-9ggv-8w38-r7pm
Record: https://patchnext.com/advisories/ghsa-9ggv-8w38-r7pm (revision 2, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typeorm 0.3.29. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm typeorm: affected >= 0.1.12, <= 0.3.28; fixed in 0.3.29

## Suggested inspection (read-only)
- `npm ls typeorm --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typeorm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9ggv-8w38-r7pm (OSV record GHSA-9ggv-8w38-r7pm lists affected ranges: npm typeorm >=0.1.12 <0.3.29 (fixed))
- Verified: https://github.com/advisories/GHSA-9ggv-8w38-r7pm (GitHub-reviewed advisory GHSA-9ggv-8w38-r7pm lists affected ranges: npm typeorm >=0.1.12 <=0.3.28)

Commands are suggestions: review each one before running it.