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 72% 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 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)
EPSS
27.6%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 21, 2026

Advisory Details (3)

Auto-updated Jun 20, 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

commit 60644f84918a (jackc/pgx)

Fix landed in jackc/pgx commit 60644f84918a — awaiting tagged release

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(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
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

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/jackc/pgx———
github.com/jackc/pgx/v4———
github.com/jackc/pgx/v5—5.9.2—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 132× 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 237 total refreshes for this CVE.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 08:55 UTCEG score recompute
  12. 2026-06-28 08:55 UTCVendor advisory
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-28 03:58 UTCEG score recompute
  15. 2026-06-28 03:58 UTCVendor advisory
  16. 2026-06-27 13:20 UTCEG score recompute
  17. 2026-06-27 13:20 UTCVendor advisory
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-26 21:19 UTCEG score recompute
  20. 2026-06-26 21:19 UTCVendor advisory
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-24 14:05 UTCEPSS rescore
  24. 2026-06-23 21:33 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 75 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-21 14:56 UTCEPSS rescore
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-19 19:25 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-17 17:53 UTCEPSS rescore
  9. 2026-06-17 05:45 UTCEG score recompute
  10. 2026-06-17 05:45 UTCVendor advisory
  11. 2026-06-17 01:24 UTCEG score recompute
  12. 2026-06-17 01:24 UTCVendor advisory
  13. 2026-06-16 17:52 UTCEPSS rescore
  14. 2026-06-16 08:04 UTCEG score recompute
  15. 2026-06-16 08:04 UTCVendor advisory
  16. 2026-06-15 17:49 UTCEPSS rescore
  17. 2026-06-15 08:03 UTCEG score recompute
  18. 2026-06-15 08:03 UTCVendor advisory
  19. 2026-06-15 03:33 UTCEG score recompute
  20. 2026-06-15 03:33 UTCVendor advisory
  21. 2026-06-14 23:24 UTCEG score recompute
  22. 2026-06-14 23:24 UTCVendor advisory
  23. 2026-06-14 19:16 UTCEG score recompute
  24. 2026-06-14 19:16 UTCVendor advisory
  25. 2026-06-14 15:06 UTCEG score recompute
  26. 2026-06-14 15:06 UTCVendor advisory
  27. 2026-06-14 10:52 UTCEG score recompute
  28. 2026-06-14 10:52 UTCVendor advisory
  29. 2026-06-14 06:44 UTCEG score recompute
  30. 2026-06-14 06:44 UTCVendor advisory
  31. 2026-06-14 02:27 UTCEG score recompute
  32. 2026-06-14 02:27 UTCVendor advisory
  33. 2026-06-13 23:00 UTCEPSS rescore
  34. 2026-06-13 10:09 UTCEG score recompute
  35. 2026-06-13 10:09 UTCVendor advisory
  36. 2026-06-12 23:12 UTCEPSS rescore
  37. 2026-06-12 23:12 UTCEPSS rescore
  38. 2026-06-12 23:07 UTCEG score recompute
  39. 2026-06-12 23:07 UTCVendor advisory
  40. 2026-06-12 18:54 UTCEG score recompute
  41. 2026-06-12 18:54 UTCVendor advisory
  42. 2026-06-12 14:28 UTCEG score recompute
  43. 2026-06-12 14:28 UTCVendor advisory
  44. 2026-06-12 09:43 UTCEG score recompute
  45. 2026-06-12 09:43 UTCVendor advisory
  46. 2026-06-12 05:35 UTCEG score recompute
  47. 2026-06-12 05:35 UTCVendor advisory
  48. 2026-06-12 01:26 UTCEG score recompute
  49. 2026-06-12 01:26 UTCVendor advisory
  50. 2026-06-11 21:17 UTCEG score recompute
  51. 2026-06-11 21:17 UTCVendor advisory
  52. 2026-06-11 17:09 UTCEG score recompute
  53. 2026-06-11 17:09 UTCVendor advisory
  54. 2026-06-11 14:00 UTCEPSS rescore
  55. 2026-06-11 12:58 UTCEG score recompute
  56. 2026-06-11 12:58 UTCVendor advisory
  57. 2026-06-11 08:44 UTCEG score recompute
  58. 2026-06-11 08:44 UTCVendor advisory
  59. 2026-06-11 04:34 UTCEG score recompute
  60. 2026-06-11 04:34 UTCVendor advisory
  61. 2026-06-11 00:25 UTCEG score recompute
  62. 2026-06-11 00:25 UTCVendor advisory
  63. 2026-06-10 22:18 UTCEPSS rescore
  64. 2026-06-10 19:46 UTCEG score recompute
  65. 2026-06-10 19:46 UTCVendor advisory
  66. 2026-06-10 15:37 UTCEG score recompute
  67. 2026-06-10 15:37 UTCVendor advisory
  68. 2026-06-10 13:22 UTCEPSS rescore
  69. 2026-06-10 13:22 UTCEPSS rescore
  70. 2026-06-10 11:29 UTCEG score recompute
  71. 2026-06-10 11:29 UTCVendor advisory
  72. 2026-06-10 07:20 UTCEG score recompute
  73. 2026-06-10 07:20 UTCVendor advisory
  74. 2026-06-10 02:51 UTCEG score recompute
  75. 2026-06-10 02: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 27.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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