CVE-2026-66838

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). 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
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in elixir-ecto postgrex allows SQL Injection via the :comment option of Postgrex.stream/4. An attacker who can influence that value can close the comment delimiter with */ and extend the streamed statement with their own clauses, which execute under the connection's role. Ecto exposes the same option through Ecto.Repo.stream/2.

Postgrex appends the comment by concatenating it into the statement text sent in the Parse message, without escaping or rejecting */. The option is validated by comment_not_present!/1 at every other execution point; stream/4 never calls it. Because Parse accepts a single command, the injection is confined to the streamed statement and further statements cannot be chained.

This issue affects postgrex: from 0.19.3 before 0.22.4.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/100CISA SSVC

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
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 7, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 7, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 4011be852c99 (elixir-ecto/postgrex)

Fix landed in elixir-ecto/postgrex commit 4011be852c99 — awaiting tagged release

https://github.com/elixir-ecto/postgrex/commit/4011be852c99dc61ddb98cb01aa41e8775a0e3dd
github_commit

commit e1ecba618dde (elixir-ecto/postgrex)

Fix landed in elixir-ecto/postgrex commit e1ecba618dde — awaiting tagged release

https://github.com/elixir-ecto/postgrex/commit/e1ecba618ddea4cee2556bd6ad9b6285e05f9d3c
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-66838
generic

CVE-2026-66838

https://cna.erlef.org/cves/CVE-2026-66838.html
githubMentions a patch (unverified)🟡 PoC Available

SQL injection via the `:comment` option in `Postgrex.stream/4` · Advisory · elixir-ecto/ecto · GitHub

https://github.com/elixir-ecto/ecto/security/advisories/GHSA-3gww-3f36-2388

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFix by version rangeDependents
postgrex0.19.3 ... 0.22.3 (8 versions)
  • 0.19.3 up to 0.22.4: fixed in 0.22.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 42× 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 103 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-66838?
CVE-2026-66838 is a high vulnerability published on August 7, 2026. Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in elixir-ecto postgrex allows SQL Injection via the :comment option of Postgrex.stream/4. An attacker who can influence that value can close the comment delimiter with */ and extend the streamed…
When was CVE-2026-66838 disclosed?
CVE-2026-66838 was first published on August 7, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66838 actively exploited?
CVE-2026-66838 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66838?
CVE-2026-66838 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-66838?
A fix for CVE-2026-66838 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-66838?

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

Book a Demo →Browse All CVEs