How severe is CVE-2009-2940?

CVE-2009-2940 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2009-2940 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2009-2940?

CVE-2009-2940 primarily affects Pygresql. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2009-2940?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2009-2940 published?

CVE-2009-2940 was published on 2009-10-22 and last updated on 2026-06-16.

CVE-2009-2940

CVE-2009-2940 is a high-severity vulnerability in Pygresql with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 3% (84th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Pygresql
Published: 2009-10-22
Last modified: 2026-06-16

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.

Frequently asked questions

What is CVE-2009-2940?: 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.
How severe is CVE-2009-2940?: CVE-2009-2940 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2009-2940 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-2940?: CVE-2009-2940 primarily affects Pygresql. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2009-2940?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2009-2940 published?: CVE-2009-2940 was published on 2009-10-22 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:pygresql:pygresql:3.8.1:*:*:*:*:*:*:*
cpe:2.3:a:pygresql:pygresql:4.0:*:*:*:*:*:*:*

Threat intelligence

Threat-intel indicators referencing this CVE:

49.229.102.187 (ipv4-addr)
41.63.62.103 (ipv4-addr)
203.192.232.180 (ipv4-addr)
177.53.215.134 (ipv4-addr)
149.86.233.213 (ipv4-addr)
141.109.168.26 (ipv4-addr)
141.109.168.107 (ipv4-addr)
125.212.235.194 (ipv4-addr)