CVE-2026-59109

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.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: 8.8Exploit: Elevated riskExposed: 0

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

SQL injection in the Zalktis accounting application via trading-partner-controlled text fields in received electronic invoices. When importing a received e-invoice (UBL/PEPPOL) or an e-commerce export, Zalktis concatenates partner-controlled values directly into SQL statement text using string concatenation, with neither parameterised queries nor escaping. The application's own escaping helper, Dazadi.sql_txt(), is not invoked on these code paths, so a party that sends an invoice can break out of the string literal and alter the query logic.

This issue affects Zalktis: before 2026.1.586 and before 2026.2.592.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

Ievainojamību ziņošanas platforma

https://cvd.cert.lv/disclosed/vuln-all-631428755

Vendor Advisories for CVE-2026-59109(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 36× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 16:14 UTCGHSA enrichment
  3. 2026-08-20 05:21 UTCGHSA enrichment
  4. 2026-08-19 18:27 UTCEG score recompute
  5. 2026-08-19 18:27 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 07:33 UTCGHSA enrichment
  8. 2026-08-18 20:40 UTCEG score recompute
  9. 2026-08-18 20:39 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 09:45 UTCGHSA enrichment
  12. 2026-08-17 22:50 UTCEG score recompute
  13. 2026-08-17 22:50 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 11:56 UTCGHSA enrichment
  16. 2026-08-17 01:03 UTCEG score recompute
  17. 2026-08-17 01:03 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:09 UTCGHSA enrichment
  20. 2026-08-16 03:16 UTCEG score recompute
  21. 2026-08-16 03:16 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 16:23 UTCGHSA enrichment
  24. 2026-08-15 05:29 UTCEG score recompute
  25. 2026-08-15 05:29 UTCGHSA enrichment
Show 11 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 18:35 UTCEG score recompute
  3. 2026-08-14 18:35 UTCGHSA enrichment
  4. 2026-08-14 18:09 UTCEG score recompute
  5. 2026-08-14 18:09 UTCGHSA enrichment
  6. 2026-08-14 15:05 UTCGHSA enrichment
  7. 2026-08-14 04:12 UTCEG score recompute
  8. 2026-08-14 04:12 UTCGHSA enrichment
  9. 2026-08-13 17:18 UTCEG score recompute
  10. 2026-08-13 17:02 UTCEG score recompute
  11. 2026-08-13 17:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59109?
CVE-2026-59109 is a high vulnerability published on August 13, 2026. SQL injection in the Zalktis accounting application via trading-partner-controlled text fields in received electronic invoices. When importing a received e-invoice (UBL/PEPPOL) or an e-commerce export, Zalktis concatenates partner-controlled values directly into SQL statement text using string…
When was CVE-2026-59109 disclosed?
CVE-2026-59109 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59109 actively exploited?
CVE-2026-59109 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 75.9% of all scored CVEs.
What is the CVSS score of CVE-2026-59109?
CVE-2026-59109 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-59109?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59109, 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

Explore the affected products and dependency analysis for CVE-2026-59109

Explore →

Is Your Infrastructure Affected by CVE-2026-59109?

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

Start Free Scan →Browse All CVEs