Skip to main content

Apache IoTDB CVE-2026-40452

| EUVDEUVD-2026-42838 HIGH
Incorrect Authorization (CWE-863)
2026-07-10 apache GHSA-xxj7-h37p-p48c
7.5
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain valid IoTDB credentials
  2. Delivery
    Connect to REST v2 API endpoint
  3. Exploit
    Send request to /rest/v2/fastLastQuery
  4. Execution
    Authorization check bypassed
  5. Impact
    Retrieve last-value time-series data outside authorized scope

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a valid authenticated session on the Apache IoTDB instance - the phrase 'unauthorized authenticated users' in the description confirms that credentials are necessary but that the authorization layer beyond authentication is what fails. The vulnerable endpoint is /rest/v2/fastLastQuery in the REST v2 API, meaning the REST interface must be enabled and network-accessible to the attacker. The attack is unauthenticated in the sense that no elevated privilege is required - any valid credential suffices, including low-privilege accounts. Limiting factors: requires valid IoTDB credentials (eliminates fully external, anonymous attackers); requires REST v2 API to be enabled and reachable; impact is read-only disclosure of last-value data, not write or execution. Deployments that run IoTDB without the REST interface, or that restrict API access to specific trusted clients, have substantially reduced exposure.

Impact

No CVSS score or vector was provided by NVD at time of analysis, and no EPSS probability is available, which limits quantitative risk comparison. From the description, exploitation requires valid credentials (authenticated users), constraining the attack surface relative to unauthenticated flaws. The impact is limited to information disclosure of last-value time-series data - there is no indication of write, delete, or code execution impact. KEV status is negative and no POC is publicly known, suggesting this is not under active opportunistic exploitation. Real-world risk is therefore moderate-to-low in absolute terms but contextually significant in IoT/OT environments where sensor last-values (e.g., temperature, pressure, flow readings) may be operationally sensitive or safety-relevant. The absence of a CVSS vector means attack complexity, scope, and precise impact cannot be confirmed from vendor-supplied metrics - all metric assessments below are independently inferred.

Exploit ScenarioDerived

An authenticated IoTDB user with a low-privilege account - for example, a read-only service account scoped to a specific storage group - sends a direct HTTP GET request to /rest/v2/fastLastQuery targeting time-series paths outside their authorized scope. The authorization check is bypassed and the server returns the most recent sensor values for the queried paths, exposing potentially sensitive telemetry data such as equipment readings or operational metrics from other tenants or groups. No public exploit code is known, but the attack requires only knowledge of the endpoint path and valid credentials.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 10, 2026

Authorization bypass in Apache IoTDB's REST API endpoint /rest/v2/fastLastQuery allows authenticated users to access last-value time-series data they are not authorized to view. Affected versions span the 1.3.x branch (1.3.5 through 1.3.7) and the 2.0.x branch (2.0.5 through 2.0.9). No public exploit code or active exploitation has been identified at time of analysis, but the REST interface nature of the flaw means any valid credential holder can attempt unauthorized data retrieval without elevated privilege.

RemediationAI

Upgrade to Apache IoTDB version 2.0.10 or later, which is confirmed by the vendor to fix this issue. For users on the 1.3.x branch, upgrade to 1.3.8 or later is implied by the stated affected range (before 1.3.8), though the vendor recommendation explicitly names 2.0.10. The advisory is available at https://lists.apache.org/thread/04j2l6dosyboor4o2gvrzbrcrpllmh95. If immediate upgrade is not possible, a compensating control is to restrict network access to the IoTDB REST API (default port 18080) to only trusted client IP ranges using firewall or network ACLs, reducing the pool of authenticated users who can reach the vulnerable endpoint. This does not eliminate the authorization bypass but limits exposure to already-trusted principals. Note that disabling the REST v2 API entirely would break integrations relying on fastLastQuery and should be evaluated against operational impact before applying.

Affected VersionsENISA

Apache IoTDB 1.3.5 <1.3.8
Apache IoTDB 2.0.5 <2.0.10

Affected Packages

euvd apache_iotdb fix: 1.3.8, 2.0.10

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 an IoT-oriented time-series database designed for high-throughput sensor and telemetry data storage. The affected component is the REST v2 API's fastLastQuery endpoint, which returns the most recent recorded value for queried time-series. The root cause is classified as CWE-863 (Incorrect Authorization) - a failure to correctly verify that an authenticated principal possesses the required authorization for a requested resource or operation, distinct from authentication failure. The CPE string (cpe:2.3:a:apache_software_foundation:apache_iotdb:*:*:*:*:*:*:*:*) confirms the flaw spans the Apache Software Foundation's mainline IoTDB product across both the 1.3.x and 2.0.x release trains. The REST v2 API is a modern interface layer added to IoTDB for programmatic data access, meaning this endpoint is likely used by automated clients and integrations rather than only interactive users.

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

Vendor (apache) PRIMARY 7.5 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 4.3 MEDIUM

Network-accessible REST API (AV:N), low complexity, requires valid credentials (PR:L), read-only last-value data disclosure with no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

1
Patch available
Jul 10, 2026 - 09:16 EUVD

DescriptionCVE.org

Incorrect Authorization, Improper Access Control vulnerability in Apache IoTDB. Authorization bypass in /rest/v2/fastLastQuery exposes last-value data to unauthorized authenticated users.

This issue affects Apache IoTDB: from 1.3.5 before 1.3.8, from 2.0.5 before 2.0.10.

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

Threat Intelligence Overview

EPSS Score
0.1%
Top 96% exploitable
Prevalence
Low
specialized IoT time-series database, niche industrial/IoT deployments
Social Media
2
Sightings
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-59562 CRITICAL
9.8 Oct 21

Missing authentication for a critical function in Apache IoTDB 2.0.0 through 2.0.10 lets unauthenticated remote attacker

CVE-2026-58663 CRITICAL
9.8 Oct 21

Unauthenticated remote attackers can bypass authentication in Apache IoTDB 2.0.0 through 2.0.10 through the Thrift RPC s

CVE-2026-40008 CRITICAL
9.8 Jul 10

Unsafe reflection in Apache IoTDB's pipe processor lets a user-supplied fully qualified Java class name be loaded and in

CVE-2026-28564 CRITICAL
9.8 Jul 10

Authentication bypass via capture-replay in Apache IoTDB (1.0.0 through 2.0.9) lets attackers reuse stale credentials ag

CVE-2026-24014 CRITICAL
9.8 Jul 06

Arbitrary file write in Apache IoTDB DataNode (versions 1.3.3 up to but not including 2.0.8) allows attackers who can re

CVE-2026-40005 CRITICAL
9.1 Jul 10

Arbitrary file write in Apache IoTDB (versions 1.0.0 through 2.0.9) lets remote attackers plant files anywhere the IoTDB

CVE-2026-59229 HIGH
8.8 Oct 21

Apache IoTDB 2.0.0 through 2.0.11 mishandles identity in its Legacy Pipe receiver: the handshake and sendPipeData handle

CVE-2026-44630 HIGH
7.5 Aug 10

Denial of service in Apache IoTDB's Thrift-based RPC service allows remote unauthenticated attackers to crash the databa

CVE-2026-40006 HIGH
7.5 Jul 10

Unauthenticated denial of service in Apache IoTDB (1.0.0 through 2.0.9) allows remote attackers to crash or degrade the

CVE-2026-24012 HIGH
7.5 Jul 06

Denial of service in Apache IoTDB versions 1.3.3 through 2.0.7 lets remote attackers crash the DataNode process by submi

CVE-2026-40007 HIGH
7.5 Jul 10

Denial of service in Apache IoTDB versions 1.0.0 up to (but not including) 2.0.10 lets an unauthenticated network attack

CVE-2026-24013 CRITICAL
9.1 Jul 06

Authentication bypass via sessionId spoofing in Apache IoTDB (1.3.3 through versions before 2.0.8) lets a remote, unauth

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy