How severe is GHSA-xv6x-43gq-4hfj?

No CVSS score has been assigned to GHSA-xv6x-43gq-4hfj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xv6x-43gq-4hfj?

GHSA-xv6x-43gq-4hfj affects the following packages: pygresql (PyPI), pygresql (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-xv6x-43gq-4hfj?

No patched version of pygresql has shipped for GHSA-xv6x-43gq-4hfj 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 GHSA-xv6x-43gq-4hfj 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 GHSA-xv6x-43gq-4hfj 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 GHSA-xv6x-43gq-4hfj?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xv6x-43gq-4hfj can be triaged on real exposure rather than presence alone.

Is GHSA-xv6x-43gq-4hfj actively exploited in the wild?

No public exploit code has been indexed for GHSA-xv6x-43gq-4hfj 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 GHSA-xv6x-43gq-4hfj?

GHSA-xv6x-43gq-4hfj 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 GHSA-xv6x-43gq-4hfj published, and has it been updated?

GHSA-xv6x-43gq-4hfj was published on May 2, 2022 and was last updated on June 8, 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

GHSA-xv6x-43gq-4hfj — pygresql

Fix: PyGreSQL/PyGreSQL@8e19320

GHSA-xv6x-43gq-4hfj 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 asCVE-2009-2940PYSEC-2009-18

Published

May 2, 2022

Updated

Jun 8, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Sep 22, 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

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

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 GHSA-xv6x-43gq-4hfj 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 GHSA-xv6x-43gq-4hfj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-xv6x-43gq-4hfj. 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

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 GHSA-xv6x-43gq-4hfj in your dependencies?

O3 Security finds GHSA-xv6x-43gq-4hfj 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