CVE-2026-41114 Apache IoTDB JDBC driver: Large-scale Memory Exhaustion via BigDecimal toPlainString in JDBC Driver
Not scored
Published
Updated
Check this codebase for CVE-2026-41114 and fix it if it is affected.
What it is: CVE-2026-41114 is a vulnerability in Apache IoTDB JDBC driver, published on 21 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-41114 in the wild and no public exploit code.
Affected product: Apache IoTDB JDBC driver. No package-level version data is available, so check the vendor advisory linked from the reference page.
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-41114/ (Markdown: https://insights.sbomify.com/CVE-2026-41114/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-41114?
CVE-2026-41114 is a vulnerability in Apache IoTDB JDBC driver, published on 21 Oct 2026.
Official description
Uncontrolled Resource Consumption vulnerability in Apache IoTDB JDBC driver.
This issue affects Apache IoTDB JDBC driver: from 1.3.3 before 2.0.11.
Users are recommended to upgrade to version 2.0.11, which fixes the issue.
Weakness: CWE-400
Which versions are affected by CVE-2026-41114?
How do I fix CVE-2026-41114?
No fix has been published for CVE-2026-41114 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-41114 being exploited?
There is no known exploitation of CVE-2026-41114 in the wild and no public exploit code.
Sources
Also known as GHSA-f58p-264f-4j63.