CVE-2026-41889

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — Patch released this week

Also known asEUVD-2026-28805 (ENISA EUVD) · GHSA-j88v-2chj-qfwx (GitHub Security Advisories) · GO-2026-5004 (OSV.dev)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 8, 2026

Last Modified

October 26, 2026

Advisory Details (3)

Auto-updated Nov 15, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

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
Web page

Release v5.9.2 · jackc/pgx · GitHub

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
oraclepatch2026-11-17oracle
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
gogithub.com/jackc/pgx—ghsa
gogithub.com/jackc/pgx/v4—ghsa
gogithub.com/jackc/pgx/v5 @ 5.9.2 (fixes < 5.9.2)—ghsa

These rows come from Oracle, Red Hat and GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 2 ecosystems)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/jackc/pgx—
  • every version through 3.6.2: no fix on record
  • every version on: no fix on record
—
github.com/jackc/pgx/v4—
  • every version through 4.18.3: no fix on record
  • every version on: no fix on record
—
github.com/jackc/pgx/v5—
  • every version up to 5.9.2: fixed in 5.9.2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-jackc-pgx-v55.8.0-1, 5.9.2-1
  • every version on: no fix on record
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 23× in last 7d / 88× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 467 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 367 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-41889?
CVE-2026-41889 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-41889 published?
The CVE record for CVE-2026-41889 was published on May 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-41889 actively exploited?
CVE-2026-41889 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-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?
A fix for CVE-2026-41889 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41889 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-41889 is also listed there, in Dutch, as NCSC-NL published it; not translated.

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.