CVE-2025-61385: pg8000 · SQL Injection
Affects pg8000Source CVE Database V5
Not known to be exploited · CVSS 9.6 Critical.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIpg8000pkg:pypi/pg8000Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately audit all Python applications using pg8000 to identify usage of the pg8000.native.literal function with list inputs.
- Implement strict input validation and sanitization to prevent maliciously crafted lists from reaching the vulnerable function.
- Restrict database user permissions to the minimum necessary, employing the principle of least privilege to limit potential damage from SQL injection.
- Monitor application logs and database queries for unusual or unexpected SQL commands that could indicate exploitation attempts.
- Employ Web Application Firewalls (WAFs) or database activity monitoring tools capable of detecting and blocking SQL injection patterns.
- Stay alert for official patches or updates from the pg8000 maintainers and apply them promptly once available.
- Educate users and developers about the risks of social engineering that could trigger user interaction-based exploits.
- Consider temporary mitigation by isolating vulnerable services or disabling features that invoke the vulnerable function until a patch is released.
Description
SQL injection vulnerability in tlocke pg8000 1.31.4 allows remote attackers to execute arbitrary SQL commands via a specially crafted Python list input to function pg8000.native.literal.