What is the CVSS score of CVE-2026-24015?

CVE-2026-24015 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

How to fix or mitigate CVE-2026-24015?

Within 24 hours: Identify all systems running affected IoTDB versions (1.0.0-1.3.6 or 2.0.0-2.0.6) and isolate them from production networks if operationally feasible. Within 7 days: Implement network segmentation to restrict IoTDB access to essential systems only, enable enhanced monitoring/logging, and contact Apache for patch timeline estimates. Within 30 days: Prepare upgrade path to patched versions (1.3.7+ or 2.0.7+) and execute migration during scheduled maintenance window.

Iotdb CVE-2026-24015

CRITICAL

Binding to an Unrestricted IP Address (CWE-1327)

2026-03-09 security@apache.org

GHSA-74cf-pgh9-m5q2

Apache Iotdb

9.8

CVSS 3.1 · NVD

View

Attack ChainAIDerived

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

Access

Send network request to IoTDB instance
Exploit

Exploit authentication bypass or injection flaw
Execution

Access unauthorized data or execute commands
Impact

Achieve full system compromise

Vulnerability Assessment

Weakness	CWE CWE-1327 OWASP Top 10:2025 A06:2021 - Vulnerable and Outdated Components ASVS 5.0 V15 - Secure Coding and Architecture Hardware binding mechanism
Exploitation Conditions	No special conditions — remote unauthenticated exploitation against default configurations of Apache IoTDB versions 1.0.0–1.3.6 and 2.0.0–2.0.6.
Impact	CVSS 9.8. IoTDB stores sensor and device data from IoT infrastructure.
Exploit ScenarioDerived	Attacker exploits vulnerability in IoTDB to access or manipulate IoT time-series data.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

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 – Mar 12, 2026

Vulnerability in Apache IoTDB from 1.0.0 before 1.3.7 and from 2.0.0 before 2.0.7. Critical severity issue in the IoT time-series database platform.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:56 CVSS 9.8

Critical vulnerability in Apache IoTDB.

RemediationAI

Update to IoTDB 1.3.7 or 2.0.7.

Affected Packages

maven org.apache.iotdb:iotdb-core fix: 1.3.7, 2.0.7

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in maven

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-1327 in Apache IoTDB, a time-series database for IoT data. Affects versions 1.0.0-1.3.6 and 2.0.0-2.0.6.

Know when 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

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

CVE Published

Mar 09, 2026 - 09:16 nvd

CRITICAL 9.8

DescriptionCVE.org

A vulnerability in Apache IoTDB.

This issue affects Apache IoTDB: from 1.0.0 before 1.3.7, from 2.0.0 before 2.0.7.

Users are recommended to upgrade to version 1.3.7 or 2.0.7, which fixes the issue.

Executive ViewAI

Why It Matters

A critical vulnerability in Apache IoTDB (CVSS 9.8) affects versions 1.0.0-1.3.6 and 2.0.0-2.0.6, with no patch currently available. Organizations using these versions face immediate risk of complete system compromise, including unauthorized data access, manipulation, and potential lateral movement within the infrastructure.

Business Impact: Severe

Compensating Controls

Until patch availability: (1) Implement strict network segmentation—restrict IoTDB to isolated VLANs with minimal east-west traffic; (2) Deploy WAF/IDS rules to detect exploitation attempts on IoTDB ports; (3) Enable comprehensive audit logging of all IoTDB queries and administrative actions; (4) Restrict administrative access to IoTDB using IP whitelisting and multi-factor authentication; (5) Disable unnecessary IoTDB features/services; (6) Increase monitoring frequency for anomalous database behavior and data access patterns.

Threat Intelligence Overview

EPSS Score

0.1%

Top 78% exploitable

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

VulDB

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 CRITICAL

CISA KEV No

Public POC No

EPSS 0.1%

Patch available Yes

Active threat No

Deciding rule

CRITICAL severity

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.