CVE-2026-41889

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

pgx is a PostgreSQL driver and toolkit for Go. Prior to version 5.9.2, SQL injection can occur when the non-default simple protocol is used, a dollar quoted string literal is used in the SQL query, that string literal contains text that would be would be interpreted as a placeholder outside of a string literal, and the value of that placeholder is controllable by the attacker. This issue has been patched in version 5.9.2.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 21, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github.
github Patch Available

SQL Injection via placeholder confusion with dollar quoted string literals · Advisory · jackc/pgx · GitHub

https://github.com/jackc/pgx/security/advisories/GHSA-j88v-2chj-qfwx
github_commit Patch Available

commit 60644f84918a (jackc/pgx)

Patch available: jackc/pgx v5.11.0 (contains commit 60644f84918a)

https://github.com/jackc/pgx/commit/60644f84918a8af66d14a4b0d865d4edafd955da
generic

Release v5.9.2 · jackc/pgx · GitHub

https://github.com/jackc/pgx/releases/tag/v5.9.2

Vendor Advisories for CVE-2026-41889(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatadvanced-cluster-security/rhacs-main-rhel8:17854209592026-07-30redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17854132102026-07-30redhat
redhatcosign-main-3.1.1-0.1.hum12026-06-10redhat
redhatcaddy-main-2.11.3-0.1.hum12026-05-12redhat
redhatgo-fdo-server-main-1.0.1-0.2.hum12026-05-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 2 ecosystems)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/jackc/pgx———
github.com/jackc/pgx/v4———
github.com/jackc/pgx/v5—5.9.2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-jackc-pgx-v55.8.0-1, 5.9.2-1——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 294 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 14:23 UTCOSV refresh
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-23 18:59 UTCEG score recompute
  25. 2026-08-23 18:59 UTCVendor advisory
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 11:30 UTCEG score recompute
  8. 2026-08-17 11:30 UTCVendor advisory
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 08:49 UTCVendor advisory
  11. 2026-08-16 04:33 UTCEG score recompute
  12. 2026-08-16 04:33 UTCVendor advisory
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 23:49 UTCVendor advisory
  16. 2026-08-14 19:40 UTCVendor advisory
  17. 2026-08-14 15:32 UTCVendor advisory
  18. 2026-08-14 11:23 UTCVendor advisory
  19. 2026-08-14 07:15 UTCVendor advisory
  20. 2026-08-14 03:07 UTCEG score recompute
  21. 2026-08-14 03:07 UTCVendor advisory
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 10:08 UTCVendor advisory
  24. 2026-08-13 05:59 UTCVendor advisory
  25. 2026-08-13 00:59 UTCVendor advisory
  26. 2026-08-12 20:51 UTCVendor advisory
  27. 2026-08-12 16:42 UTCEG score recompute
  28. 2026-08-12 16:42 UTCVendor advisory
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-12 00:29 UTCVendor advisory
  31. 2026-08-11 20:08 UTCVendor advisory
  32. 2026-08-11 15:50 UTCEG score recompute
  33. 2026-08-11 15:50 UTCVendor advisory
  34. 2026-08-11 13:43 UTCEPSS rescore
  35. 2026-08-11 10:15 UTCVendor advisory
  36. 2026-08-11 05:24 UTCVendor advisory
  37. 2026-08-11 01:16 UTCEG score recompute
  38. 2026-08-11 01:16 UTCVendor advisory
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-10 11:46 UTCVendor advisory
  41. 2026-08-10 07:37 UTCVendor advisory
  42. 2026-08-10 03:27 UTCVendor advisory
  43. 2026-08-09 23:18 UTCVendor advisory
  44. 2026-08-09 19:10 UTCVendor advisory
  45. 2026-08-09 15:02 UTCEG score recompute
  46. 2026-08-09 15:02 UTCVendor advisory
  47. 2026-08-09 13:46 UTCEPSS rescore
  48. 2026-08-09 10:53 UTCVendor advisory
  49. 2026-08-09 06:31 UTCVendor advisory
  50. 2026-08-09 02:23 UTCEG score recompute
  51. 2026-08-09 02:23 UTCVendor advisory
  52. 2026-08-08 16:37 UTCEPSS rescore
  53. 2026-08-08 13:20 UTCVendor advisory
  54. 2026-08-08 09:10 UTCVendor advisory
  55. 2026-08-08 05:01 UTCVendor advisory
  56. 2026-08-08 00:53 UTCVendor advisory
  57. 2026-08-07 20:44 UTCVendor advisory
  58. 2026-08-07 16:36 UTCEG score recompute
  59. 2026-08-07 16:36 UTCVendor advisory
  60. 2026-08-07 12:27 UTCVendor advisory
  61. 2026-08-07 08:18 UTCVendor advisory
  62. 2026-08-07 01:42 UTCVendor advisory
  63. 2026-08-06 20:59 UTCVendor advisory
  64. 2026-08-06 16:51 UTCEG score recompute
  65. 2026-08-06 16:51 UTCVendor advisory
  66. 2026-08-06 13:46 UTCEPSS rescore
  67. 2026-08-06 10:34 UTCVendor advisory
  68. 2026-08-06 06:23 UTCVendor advisory
  69. 2026-08-06 02:15 UTCVendor advisory
  70. 2026-08-05 22:07 UTCEG score recompute
  71. 2026-08-05 22:07 UTCVendor advisory
  72. 2026-08-05 19:17 UTCEPSS rescore
  73. 2026-08-04 15:10 UTCEPSS rescore
  74. 2026-08-04 10:38 UTCEPSS rescore
  75. 2026-08-04 03:51 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41889?
CVE-2026-41889 is a critical vulnerability published on May 8, 2026. pgx is a PostgreSQL driver and toolkit for Go. Prior to version 5.9.2, SQL injection can occur when the non-default simple protocol is used, a dollar quoted string literal is used in the SQL query, that string literal contains text that would be would be interpreted as a placeholder outside of a…
When was CVE-2026-41889 disclosed?
CVE-2026-41889 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41889 actively exploited?
CVE-2026-41889 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.7% of all scored CVEs.
What is the CVSS score of CVE-2026-41889?
CVE-2026-41889 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-41889?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41889, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41889

Explore →

Is Your Infrastructure Affected by CVE-2026-41889?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs