CVE-2026-59783

LOWPre-NVD 2.32.3
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
2.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 2.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The Zabbix Server/Proxy has a vulnerability where binary items can crash the Server/Proxy on certain NULL byte input leading to potential loss of availability. This only affects deployments where MySQL/MariaDB database is used as the Zabbix database.

CVSS v3
2.3
EG Score
2.3LOWmedium confidence
EG Risk
10
EG Risk 10/100

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 (value × EchelonGraph’s weight)
Severity23% × 45%
The EG Score, 2.3 of 10.
Exploitation0.2% × 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.2%
EPSS %ILE
12th
KEV
Not listed

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.

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

October 5, 2026

Last Modified

October 6, 2026

References (1)

Vendor Advisories for CVE-2026-59783(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
zabbix1:6.0.14+dfsg-1 ... 1:7.0.9+dfsg-1~bpo12+1 (29 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
zabbix1:7.0.10+dfsg-2 ... 1:7.0.29+dfsg-2~bpo13+1 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
zabbix1:7.0.10+dfsg-2 ... 1:7.0.27+dfsg-1 (6 versions)
  • every version up to 1:7.0.29+dfsg-1: fixed in 1:7.0.29+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 21× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-12 15:52 UTCEG score recompute
  4. 2026-10-11 19:36 UTCEG score recompute
  5. 2026-10-11 16:51 UTCEG score recompute
  6. 2026-10-11 14:13 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-09 18:37 UTCEG score recompute
  11. 2026-10-09 18:37 UTCGHSA enrichmentGHSA-2835-94vr-22j6 · GitHub severity LOW
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-10-06 15:33 UTCEG score recompute
  15. 2026-10-06 15:33 UTCGHSA enrichmentGHSA-2835-94vr-22j6 · GitHub severity LOW
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-10-05 12:31 UTCEG score recompute
  18. 2026-10-05 11:56 UTCEG score recompute
  19. 2026-10-05 11:29 UTCEG score recompute
  20. 2026-10-05 10:37 UTCEG score recomputeFirst assessed: 2.3 LOW
  21. 2026-10-05 10:36 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-59783?
CVE-2026-59783 is a low-severity vulnerability; its CVE record was published on October 5, 2026. The Zabbix Server/Proxy has a vulnerability where binary items can crash the Server/Proxy on certain NULL byte input leading to potential loss of availability. This only affects deployments where MySQL/MariaDB database is used as the Zabbix database.
When was the CVE record for CVE-2026-59783 published?
The CVE record for CVE-2026-59783 was published on October 5, 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 6, 2026; the record at its source may have been updated since.
Is CVE-2026-59783 actively exploited?
CVE-2026-59783 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59783?
CVE-2026-59783 has a CVSS base score of 2.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59783?
A fix for CVE-2026-59783 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59783 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59783?

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

Book a Demo →Browse All CVEs