Skip to main content
CVE-2025-61385VulnerabilityPublished Updated

CVE-2025-61385: pg8000 · n/a

Affects pg8000Source CVE Database V5

0

Not known to be exploited · CVSS 9.6 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
PyPIpg8000pkg:pypi/pg8000Other threatsAffected
  • =1.31.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately audit all Python applications using pg8000 to identify usage of the pg8000.native.literal function with list inputs. 2. Implement strict input validation and sanitization to prevent maliciously crafted lists from reaching the vulnerable function. 3. Restrict database user permissions to the minimum necessary, employing the principle of least privilege to limit potential damage from SQL injection. 4. Monitor application logs and database queries for unusual or unexpected SQL commands that could indicate exploitation attempts. 5. Employ Web Application Firewalls (WAFs) or database activity monitoring tools capable of detecting and blocking SQL injection patterns. 6. Stay alert for official patches or updates from the pg8000 maintainers and apply them promptly once available. 7. Educate users and developers about the risks of social engineering that could trigger user interaction-based exploits. 8. 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.

References

Community reviews

Loading reviews…