NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

pgx SQL Injection via Line Comment CreationGHSA-m7wr-2xf7-cm9p

HIGHFix: jackc/pgx@f94eb0e

GHSA-m7wr-2xf7-cm9p is a high-severity (CVSS 8.1) SQL Injection vulnerability in github.com/jackc/pgx. A fix is available for github.com/jackc/pgx — see the affected versions and patch details below.

Also known asCVE-2024-27289GO-2024-2605
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m7wr-2xf7-cm9p.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk
0.09%0.51%0.93%1.35%0.6%0.8%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹github.com/jackc/pgx🐹github.com/jackc/pgx/v4

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

Description

Impact

SQL injection can occur when all of the following conditions are met:

  1. The non-default simple protocol is used.
  2. A placeholder for a numeric value must be immediately preceded by a minus.
  3. There must be a second placeholder for a string value after the first placeholder; both must be on the same line.
  4. Both parameter values must be user-controlled.

e.g.

Simple mode must be enabled:

// connection string includes "prefer_simple_protocol=true"
// or
// directly enabled in code
config.ConnConfig.PreferSimpleProtocol = true

Parameterized query:

SELECT * FROM example WHERE result=-$1 OR name=$2;

Parameter values:

$1 => -42 $2 => "foo\n 1 AND 1=0 UNION SELECT * FROM secrets; --"

Resulting query after preparation:

SELECT * FROM example WHERE result=--42 OR name= 'foo
1 AND 1=0 UNION SELECT * FROM secrets; --';

Patches

The problem is resolved in v4.18.2.

Workarounds

Do not use the simple protocol or do not place a minus directly before a placeholder.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/jackc/pgxall versions4.18.2go get github.com/jackc/pgx@v4.18.2
🐹Gogithub.com/jackc/pgx/v4all versions4.18.2go get github.com/jackc/pgx/v4@v4.18.2

Affected Products

1 product · 1 configurations
Application
pgxjackc
< 4.18.2
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update github.com/jackc/pgx to 4.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m7wr-2xf7-cm9p is resolved across your whole dependency graph.

  3. 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.

Red HatModerate
Workaround published by Red Hat
A possible mitigation is to not use the simple protocol or do not place a minus directly before a placeholder.
Source: Red Hat security advisory for GHSA-m7wr-2xf7-cm9p (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Advanced Cluster Security 4.3advanced-cluster-security/rhacs-central-db-rhel8:4.3.5-3RHSA-2024:1321
Red Hat OpenShift Container Platform 4.16openshift4/ose-agent-installer-csr-approver-rhel9:v4.16.0-202410031007.p0.g342902b.assembly.stream.el9RHSA-2024:7944
Red Hat OpenShift Container Platform 4.17openshift4/ose-agent-installer-csr-approver-rhel9:v4.17.0-202410031034.p0.gfbc55c6.assembly.stream.el9RHSA-2024:7922

Frequently Asked Questions

### Impact SQL injection can occur when all of the following conditions are met: 1. The non-default simple protocol is used. 2. A placeholder for a numeric value must be immediately preceded by a minus. 3. There must be a second placeholder for a string value after the first placeholder; both must be on the same line. 4. Both parameter values must be user-controlled. e.g. Simple mode must be enabled: ```go // connection string includes "prefer_simple_protocol=true" // or // directly enabled in code config.ConnConfig.PreferSimpleProtocol = true ``` Parameterized query: ```sql SELECT * F
O3 Security · Impact-Aware SCA

Is GHSA-m7wr-2xf7-cm9p in your dependencies?

Find it across Go, including transitive dependencies.

pgx SQL Injection via Line Comment Creation (High 8.1)