What is CVE-2025-61385?

CVE-2025-61385 is a high-severity SQL injection vulnerability in pg8000 (pip), affecting versions <= 1.31.4. It is fixed in 1.31.5. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

Which versions of pg8000 are affected by CVE-2025-61385?

pg8000 (pip) versions <= 1.31.4 is affected.

Is there a fix for CVE-2025-61385?

Yes. CVE-2025-61385 is fixed in 1.31.5. Upgrade to this version or later.

Is CVE-2025-61385 exploitable, and should I be worried?

Whether CVE-2025-61385 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-61385 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-61385 in pg8000

Q: Which versions of pg8000 are affected by CVE-2025-61385?

pg8000 (pip) versions <= 1.31.4 is affected.

Q: Is there a fix for CVE-2025-61385?

Yes. CVE-2025-61385 is fixed in 1.31.5. Upgrade to this version or later.

Q: Is CVE-2025-61385 exploitable, and should I be worried?

Whether CVE-2025-61385 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-61385 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-61385?

Upgrade pg8000 to 1.31.5 or later.

CVE-2025-61385

CVE-2025-61385 is a high-severity SQL injection vulnerability in pg8000 (pip), affecting versions <= 1.31.4. It is fixed in 1.31.5.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

pg8000 SQL injection vulnerability via a specially crafted Python list input

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.

Impact

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Affected versions

pg8000 (<= 1.31.4)

Security releases

pg8000 → 1.31.5 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade pg8000 to 1.31.5 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-61385? CVE-2025-61385 is a high-severity SQL injection vulnerability in pg8000 (pip), affecting versions <= 1.31.4. It is fixed in 1.31.5. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
Which versions of pg8000 are affected by CVE-2025-61385? pg8000 (pip) versions <= 1.31.4 is affected.
Is there a fix for CVE-2025-61385? Yes. CVE-2025-61385 is fixed in 1.31.5. Upgrade to this version or later.
Is CVE-2025-61385 exploitable, and should I be worried? Whether CVE-2025-61385 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-61385 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-61385? Upgrade pg8000 to 1.31.5 or later.