Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

TypeORM vulnerable to MAID and Prototype PollutionGHSA-pf2j-9qmp-jqr2

CRITICAL

GHSA-pf2j-9qmp-jqr2 is a critical-severity (CVSS 9.8) CWE-471 vulnerability in typeorm. 1 public exploit reference exists, so weaponization risk is real. A fix is available for typeorm — see the affected versions and patch details below.

Also known asCVE-2020-8158
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk
0.00%0.89%1.78%2.67%0.3%2.1%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-pf2j-9qmp-jqr2 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
typeormnpm
3.2Mdownloads / week

Description

Prototype pollution vulnerability in the TypeORM package < 0.2.25 may allow attackers to add or modify Object properties leading to further denial of service or SQL injection attacks.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmtypeormall versions0.2.25npm install typeorm@0.2.25

Affected Products

1 product · 1 configurations
Application
typeormtypeorm
< 0.2.25
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Prototype pollution vulnerability in the TypeORM package < 0.2.25 may al…

hackerone.comNVDSep 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typeorm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update typeorm to 0.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pf2j-9qmp-jqr2 is resolved across your whole dependency graph.

  3. Workarounds

    Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

Prototype pollution vulnerability in the TypeORM package < 0.2.25 may allow attackers to add or modify Object properties leading to further denial of service or SQL injection attacks.
O3 Security · Impact-Aware SCA

Is GHSA-pf2j-9qmp-jqr2 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
TypeORM vulnerable to MAID and Prototype Pollution