How severe is CVE-2009-2940?

No CVSS score has been assigned to CVE-2009-2940 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2009-2940?

CVE-2009-2940 affects the following packages: pygresql (PyPI), pygresql (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2009-2940?

A fix is available for CVE-2009-2940; check the affected-versions list above or the advisory for the patched release of pygresql, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2009-2940 in my PyPI dependencies?

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

How do I mitigate CVE-2009-2940 if there is no patch (or I can't update yet)?

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.

Is CVE-2009-2940 actively exploited in the wild?

No public exploit code has been indexed for CVE-2009-2940 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2009-2940?

CVE-2009-2940 has an EPSS (Exploit Prediction Scoring System) score of 2.7%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2009-2940 published, and has it been updated?

CVE-2009-2940 was published on October 22, 2009 and was last updated on May 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2009-2940 — pygresql

Fix: PyGreSQL/PyGreSQL@8e19320

CVE-2009-2940 is a security vulnerability in pygresql. A fix is available for pygresql — see the affected versions and patch details below.

PyGreSQL Might Be Vulnerable to Encoding-Based SQL Injection

Also known asGHSA-xv6x-43gq-4hfjPYSEC-2009-18

Published

Oct 22, 2009

Updated

May 20, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐍pygresql🐍pygresql

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

PyGreSQL 3.8 did not use PostgreSQL’s safe string and bytea functions in its own escaping functions. As a result, applications written to use PyGreSQL’s escaping functions are vulnerable to SQL injections when processing certain multi-byte character sequences. Because the safe functions require a database connection, to maintain backwards compatibility, pg.escape_string() and pg.escape_bytea() are still available, but applications will have to be adjusted to use the new pyobj.escape_string() and pyobj.escape_bytea() functions. For example, code containing:

import pg
connection = pg.connect(...)
escaped = pg.escape_string(untrusted_input)

should be adjusted to use:

import pg
connection = pg.connect(...)
escaped = connection.escape_string(untrusted_input)

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pygresql`	all versions	No fix
🐍PyPI	`pygresql`	≥ 4.0&&< 4.1	4.1`pip install --upgrade 'pygresql==4.1'`

Affected Products

1 product · 2 configurations

Application

pygresqlpygresql

2 versions

3.8.14.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pygresql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2009-2940; check the affected-versions list above or the advisory for the patched release of pygresql, then make sure no transitive dependency still pins the vulnerable range.
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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Ubuntu

USN-870-1Ubuntu

Frequently Asked Questions

PyGreSQL 3.8 did not use PostgreSQL’s safe `string` and `bytea` functions in its own escaping functions. As a result, applications written to use PyGreSQL’s escaping functions are vulnerable to SQL injections when processing certain multi-byte character sequences. Because the safe functions require a database connection, to maintain backwards compatibility, `pg.escape_string()` and `pg.escape_bytea()` are still available, but applications will have to be adjusted to use the new `pyobj.escape_string()` and `pyobj.escape_bytea()` functions. For example, code containing: ```python import pg conn

O3 Security · Impact-Aware SCA

Is CVE-2009-2940 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works