# CVE-2026-24713: Apache IoTDB: JEXL Expression Injection Vulnerability

> Attackers can execute arbitrary code via JEXL expression injection in Apache IoTDB, requiring an upgrade to secure the database.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-6w48-2g9j-v9q5

## What is CVE-2026-24713?

CVE-2026-24713 is a critical code injection vulnerability in Apache IoTDB, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Input Validation 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.

Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-24713?

4 open source packages ship an affected version, including org.apache.iotdb:iotdb-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.iotdb:iotdb-core` | Maven | From 1.0.0 | 1.3.7 |
| `org.apache.iotdb:iotdb-core` | Maven | From 1.0.0 | 1.3.7 |
| `org.apache.iotdb:iotdb-core` | Maven | From 2.0.0 | 2.0.7 |
| `org.apache.iotdb:iotdb-core` | Maven | From 2.0.0 | 2.0.7 |

Products: Apache Iotdb.

## How do I fix CVE-2026-24713?

Upgrade org.apache.iotdb:iotdb-core to a fixed version for your release line: 1.3.7 or 2.0.7.

## Is CVE-2026-24713 being exploited?

There is no known exploitation of CVE-2026-24713 in the wild and no public exploit code.

## Other vulnerabilities in Apache IoTDB

- [CVE-2026-24014](https://insights.sbomify.com/CVE-2026-24014/): Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write (critical 9.8)
- [CVE-2026-24015](https://insights.sbomify.com/CVE-2026-24015/): Apache IoTDB: Insecure Default Configuration Vulnerability (critical 9.8)
- [CVE-2024-24780](https://insights.sbomify.com/CVE-2024-24780/): Apache IoTDB: Remote Code Execution with untrusted URI of User-defined function (critical 9.8)
- [CVE-2023-46226](https://insights.sbomify.com/CVE-2023-46226/): Apache IoTDB: Remote Code Execution (RCE) risk via the UDF (critical 9.8)
- [CVE-2023-51656](https://insights.sbomify.com/CVE-2023-51656/): Apache IoTDB: Unsafe deserialize map in Sync Tool (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24713 and fix it if it is affected.

What it is: CVE-2026-24713 is a critical code injection vulnerability in Apache IoTDB, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24713 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.iotdb:iotdb-core (Maven): affected from 1.0.0; fixed in 1.3.7
- org.apache.iotdb:iotdb-core (Maven): affected from 1.0.0; fixed in 1.3.7
- org.apache.iotdb:iotdb-core (Maven): affected from 2.0.0; fixed in 2.0.7
- org.apache.iotdb:iotdb-core (Maven): affected from 2.0.0; fixed in 2.0.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24713/ (Markdown: https://insights.sbomify.com/CVE-2026-24713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24713
- OSV: https://osv.dev/vulnerability/CVE-2026-24713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24713/
Summaries are generated and may contain mistakes; the official description above is the record.