CVE-2026-59562

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week

Also known asEUVD-2026-107166 (ENISA EUVD) · GHSA-mxqj-w2qc-786q (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS v2: —Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Missing authentication for critical function vulnerability in Apache IoTDB.

This issue affects Apache IoTDB: from 2.0.0 before 2.0.11.

Users are recommended to upgrade to version 2.0.11, which fixes the issue.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

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

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 21, 2026

Last Modified

October 22, 2026

References (2)

Vendor Advisories for CVE-2026-59562(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 16× 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-27 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-25 14:16 UTCEG score recompute
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-22 17:13 UTCEG score recompute
  8. 2026-10-22 17:12 UTCGHSA enrichmentGHSA-mxqj-w2qc-786q
  9. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-21 19:28 UTCGHSA enrichmentGHSA-mxqj-w2qc-786q
  11. 2026-10-21 19:26 UTCNVD update
  12. 2026-10-21 18:31 UTCGHSA enrichmentGHSA-mxqj-w2qc-786q
  13. 2026-10-21 18:30 UTCMITRE cvelistV5
  14. 2026-10-21 12:25 UTCNVD update
  15. 2026-10-21 11:26 UTCEG score recompute
  16. 2026-10-21 11:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-59562?
CVE-2026-59562 is a vulnerability whose severity is not yet rated; its CVE record was published on October 21, 2026. Missing authentication for critical function vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 2.0.0 before 2.0.11. Users are recommended to upgrade to version 2.0.11, which fixes the issue.
When was the CVE record for CVE-2026-59562 published?
The CVE record for CVE-2026-59562 was published on October 21, 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 22, 2026; the record at its source may have been updated since.
Is CVE-2026-59562 actively exploited?
CVE-2026-59562 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-59562?
The CVE record for CVE-2026-59562 names the fix: "Users are recommended to upgrade to version 2.0.11, which fixes the issue." The vendor advisories EchelonGraph has for CVE-2026-59562 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59562?

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

Book a Demo →Browse All CVEs