CVE-2026-58663

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qhh3-6vw4-44c4 ↗EUVD-2026-107162 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache IoTDB >= 2.0.0, < 2.0.11
fixed in 2.0.11
ETK-2026-2314Zero's internal tracking ID, independent of the CVE number., permanent identifier
32msince last run
1h 34mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h59m
0
+4h
+6h
+8h
+10h
+12h

description

Apache IoTDB versions 2.0.0 through 2.0.10 are affected by an authentication bypass in the Thrift RPC service. An attacker able to reach the affected RPC service may bypass authentication; the advisory does not provide further preconditions.

mitigation

Upgrade Apache IoTDB to version 2.0.11. Until the upgrade is complete, restrict network access to the Thrift RPC service to trusted clients.

fixed in 2.0.11

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 34m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 11:03Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-21 11:03Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-58663

{
  "etk_id": "ETK-2026-2314",
  "cve_id": "CVE-2026-58663",
  "display_id": "CVE-2026-58663",
  "ghsa_id": "GHSA-qhh3-6vw4-44c4",
  "euvd_id": "EUVD-2026-107162",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Apache IoTDB Thrift RPC service",
  "summary": "Apache IoTDB versions 2.0.0 through 2.0.10 are affected by an authentication bypass in the Thrift RPC service. An attacker able to reach the affected RPC service may bypass authentication; the advisory does not provide further preconditions.",
  "mitigation": "Upgrade Apache IoTDB to version 2.0.11. Until the upgrade is complete, restrict network access to the Thrift RPC service to trusted clients.",
  "vendor": "Apache Software Foundation",
  "product": "Apache IoTDB",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.0.0, < 2.0.11"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.0.11"
      ],
      "package_name": "Apache IoTDB",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 93.77343525,
  "t0_at": "2026-10-21T11:03:23.887000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T11:03:23.887000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T11:03:23.887000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-58663"
    }
  }
}

published 2026-10-21 11:28Z
last change 2026-10-21 13:29Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.