Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach IoTDB network service
-
ExploitInvoke critical function without credentials
-
ExecutionBypass missing authentication check
-
ImpactRead or modify time-series data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to an Apache IoTDB service running an affected version (2.0.0 through 2.0.10); the advisory describes a missing authentication check on a critical function, meaning no valid credentials are needed to invoke it. The limiting factors are that the specific affected function and its default exposure are not detailed in the advisory, the deployment must be running a vulnerable pre-2.0.11 version, and the IoTDB endpoint must be reachable by the attacker (e.g., not isolated behind network controls). No user interaction appears to be required based on the CWE-306 classification. |
| Impact | This is a CWE-306 (Missing Authentication for Critical Function) flaw in Apache IoTDB, which by its nature means a security-critical operation can be reached without authentication - a serious class of weakness. However, the available signals are sparse: no CVSS score or vector was provided (CVSS: N/A), there is no EPSS exploitation-probability data, the CVE is NOT listed in CISA KEV, and no public POC was identified. The only authoritative source is the Apache project's own advisory (reported by apache). Because no CVSS vector is supplied, attack vector, complexity, and privilege requirements cannot be confirmed from the input and must be inferred from the CWE and product architecture: IoTDB is a network-facing time-series database, so the missing-authentication weakness most plausibly exposes a network-reachable function to unauthenticated clients, but this is INFERRED, not confirmed. No SSVC decision data was provided. Net assessment: the vulnerability class is high-impact and should be patched promptly (fix is available in 2.0.11), but there is currently no evidence of active or at-scale exploitation - treat as a prioritized patch rather than an emergency, pending a vendor CVSS vector to confirm the true attack surface. |
| Exploit ScenarioDerived | An attacker with network reachability to an Apache IoTDB instance (versions 2.0.0 up to 2.0.11) invokes a critical function that fails to enforce authentication, performing privileged operations such as reading or manipulating stored time-series data without valid credentials. No public exploit code was identified at time of analysis, and the exact exposed function is not detailed in the advisory, so a real-world attack would require probing the service interface to locate the unauthenticated entry point. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Missing authentication in Apache IoTDB 2.0.0 through 2.0.10 exposes a security-critical function to unauthenticated remote invocation, giving attackers high confidentiality and integrity impact (assessed CVSS 3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) while availability remains unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis, but any network-reachable pre-2.0.11 IoTDB service should be treated as at risk. Apache has released 2.0.11 to address the missing authentication control.
RemediationAI
Upgrade Apache IoTDB to version 2.0.11 or later; this is the vendor-released patch and the primary fix, as documented in the Apache advisory at https://lists.apache.org/thread.html/6035x52ct37d03xllc9rw1y5q1zzqthl. If an immediate upgrade is not possible, reduce exposure by restricting network access to IoTDB service endpoints to trusted hosts through firewall or security-group rules, placing the service behind an authenticating reverse proxy, and disabling or isolating any unused IoTDB endpoints; these controls lower the attack surface but add operational overhead and can break legitimate client integrations. Until patched, monitor service logs for unauthenticated or anomalous requests to critical IoTDB functions and review whether the affected endpoint is reachable from untrusted networks.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache IoTDB is a time-series database used for industrial and IoT telemetry workloads, and the CPE entry cpe:2.3:a:apache_software_foundation:apache_iotdb:*:*:*:*:*:*:*:* identifies the Apache Software Foundation product as the affected component, with the vendor advisory restricting the vulnerable range to 2.0.0 through 2.0.10. The root cause is CWE-306, Missing Authentication for Critical Function: a security-relevant operation or endpoint does not enforce an authentication check before allowing invocation. The independent assessment’s vector (AV:N/AC:L/PR:N/UI:N) indicates that a remote attacker can reach the vulnerable function over the network without credentials and without user interaction, and the high confidentiality and integrity ratings reflect that the function can expose or modify sensitive data. The advisory does not identify the specific affected function or its default exposure, so defenders should assume any reachable pre-2.0.11 IoTDB endpoint may expose the flaw until the service is upgraded or isolated.
Know when Apache Iotdb gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CWE-306 missing authentication on a network database service implies AV:N/AC:L/PR:N/UI:N; unauthorized access to a critical function likely exposes and alters stored data (C:H/I:H), availability impact unconfirmed.
Primary rating from Vendor (apache).
Lifecycle Timeline
2DescriptionCVE.org
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.
Executive ViewAI
Apache IoTDB versions 2.0.0 through 2.0.10 ship with a missing authentication control on a security-critical function, allowing any party able to reach the service over the network to invoke it without credentials and read or alter time-series data. Because the flaw is remotely reachable and requires no login, any internet-facing or broadly reachable IoTDB deployment effectively exposes its data and integrity guarantees to unauthorized parties. Leadership should care because IoTDB typically backs operational telemetry and industrial analytics, so unauthorized read/write access can corrupt decision-making data and undermine trust in the platforms built on it.
Apply vendor patch: Apache IoTDB 2.0.11. Where upgrade cannot be completed immediately, restrict network reachability of affected 2.0.0-2.0.10 instances to trusted hosts and place an authenticating reverse proxy in front of them.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Apache Iotdb
View allUnsafe reflection in Apache IoTDB's pipe processor lets a user-supplied fully qualified Java class name be loaded and in
Authentication bypass via capture-replay in Apache IoTDB (1.0.0 through 2.0.9) lets attackers reuse stale credentials ag
Arbitrary file write in Apache IoTDB DataNode (versions 1.3.3 up to but not including 2.0.8) allows attackers who can re
Arbitrary file write in Apache IoTDB (versions 1.0.0 through 2.0.9) lets remote attackers plant files anywhere the IoTDB
Denial of service in Apache IoTDB's Thrift-based RPC service allows remote unauthenticated attackers to crash the databa
Unauthenticated denial of service in Apache IoTDB (1.0.0 through 2.0.9) allows remote attackers to crash or degrade the
Denial of service in Apache IoTDB versions 1.3.3 through 2.0.7 lets remote attackers crash the DataNode process by submi
Authorization bypass in Apache IoTDB's REST API endpoint /rest/v2/fastLastQuery allows authenticated users to access las
Denial of service in Apache IoTDB versions 1.0.0 up to (but not including) 2.0.10 lets an unauthenticated network attack
Authentication bypass via sessionId spoofing in Apache IoTDB (1.3.3 through versions before 2.0.8) lets a remote, unauth
Privilege escalation in Apache IoTDB 2.0.8 through 2.0.9 allows any authenticated low-privilege user to rename their own
Path traversal in Apache IoTDB (1.0.0 before 1.3.6 and 2.0.0 before 2.0.7) allows remote attackers to read and write fil
EUVD-2026-107166
GHSA-mxqj-w2qc-786q
CVE.org
EPSS
Exploit-DB