Quick answers
- Is CVE-2026-58663 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58663 being exploited in the wild.
- How severe is CVE-2026-58663?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Apache IoTDB 2.0.0 to 2.0.10.
- Is there a fix for CVE-2026-58663?
- Yes: fixed in 2.0.11. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58663 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-58663?
- Check whether you run Apache IoTDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.0.11
Technical details
An authentication bypass vulnerability exists in Apache IoTDB's Thrift RPC service that allows attackers to access the database without proper authentication. The vulnerability affects versions 2.0.0 through 2.0.10, and a fix is available in version 2.0.11. The attack vector is network-based with no reported public exploitation in the wild.
Affected products
- Apache IoTDB 2.0.0 to 2.0.10
Timeline
- 2026-10-21: disclosed