CVE-2025-29744 — pg-promise
MEDIUMCVE-2025-29744 is a medium-severity (CVSS 5.4) SQL Injection vulnerability in pg-promise. A fix is available for pg-promise — see the affected versions and patch details below.
pg-promise SQL Injection vulnerability
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-29744.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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.
pg-promisenpmDescription
pg-promise before 11.5.5 is vulnerable to SQL Injection due to improper handling of negative numbers.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | pg-promise | all versions | 11.5.5npm install pg-promise@11.5.5 |
Affected Products
pg-promisevitaly-tDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pg-promise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pg-promise to 11.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-29744 is resolved across your whole dependency graph.
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
Is CVE-2025-29744 in your dependencies?
Find it across npm, including transitive dependencies.