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.3%, top 80% 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
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%CVSS: 8.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.2(medium)
EG Risk
53(Track)
EG Risk 53/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
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

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
github Patch Available🟡 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 rangeFixed inDependents
postgrex0.19.3 ... 0.22.3 (8 versions)0.22.4—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 37× 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.

  1. 2026-08-26 19:04 UTCEG score recompute
  2. 2026-08-26 14:47 UTCEPSS rescore
  3. 2026-08-25 17:18 UTCEG score recompute
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-24 15:10 UTCEG score recompute
  6. 2026-08-23 00:44 UTCEG score recompute
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 11:55 UTCEG score recompute
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 10:02 UTCEG score recompute
  11. 2026-08-20 22:56 UTCEPSS rescore
  12. 2026-08-19 19:36 UTCEG score recompute
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 17:51 UTCEG score recompute
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 14:49 UTCEG score recompute▲ 2.30
  17. 2026-08-17 14:49 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 02:22 UTCEG score recompute
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 01:16 UTCEG score recompute
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 23:02 UTCEG score recompute
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-12 21:56 UTCEG score recompute
Show 12 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 20:50 UTCEG score recompute
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-09 18:36 UTCEG score recompute
  5. 2026-08-09 13:47 UTCEPSS rescore
  6. 2026-08-08 17:30 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-07 16:23 UTCEG score recompute
  9. 2026-08-07 15:23 UTCEG score recompute
  10. 2026-08-07 13:25 UTCEG score recompute
  11. 2026-08-07 12:28 UTCEG score recompute
  12. 2026-08-07 12:27 UTCMITRE cvelistV5first tracked

Related CVEs(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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 79.5% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66838, 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-66838

Explore →

Is Your Infrastructure Affected by CVE-2026-66838?

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

Start Free Scan →Browse All CVEs