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?

No patched version of pygresql has shipped for CVE-2009-2940 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

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)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2009-2940?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2009-2940 can be triaged on real exposure rather than presence alone.

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 85th 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

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 Sep 21, 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 CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

The pygresql module 3.8.1 and 4.0 for Python does not properly support the PQescapeStringConn function, which might allow remote attackers to leverage escaping issues involving multibyte character encodings.

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'`

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
No patched version of pygresql has shipped for CVE-2009-2940 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2009-2940 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2009-2940. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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

O3 Security · Impact-Aware SCA

Is CVE-2009-2940 in your dependencies?

O3 Security finds CVE-2009-2940 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works