PatchSiren cyber security CVE debrief
CVE-2026-41114 Apache Software Foundation CVE debrief
The Apache IoTDB JDBC driver is vulnerable to uncontrolled resource consumption, leading to memory exhaustion. This issue affects versions from 1.3.3 to before 2.0.11. Users should upgrade to version 2.0.11 to fix the issue. The vulnerability is caused by the BigDecimal toPlainString method in the JDBC driver, which can lead to large-scale memory exhaustion. Affected users should assess their exposure and upgrade to the fixed version. The CVE record and source item provide information on the vulnerability and affected versions.
- Vendor
- Apache Software Foundation
- Product
- Apache IoTDB JDBC driver
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-21
- Original CVE updated
- 2026-10-30
- Advisory published
- 2026-10-21
- Advisory updated
- 2026-10-30
Who should care
Users of Apache IoTDB JDBC driver versions 1.3.3 to before 2.0.11 should assess exposure and upgrade to version 2.0.11. Affected operator, platform, vulnerability-management, and security-team impact should be reviewed. Users should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
Why it matters
The Apache IoTDB JDBC driver vulnerability can lead to memory exhaustion, affecting versions from 1.3.3 to before 2.0.11. Users should upgrade to version 2.0.11 to fix the issue.
- Memory exhaustion can occur due to uncontrolled resource consumption
- Upgrade to version 2.0.11 is required to fix the issue
Technical summary
The Apache IoTDB JDBC driver is vulnerable to uncontrolled resource consumption due to the BigDecimal toPlainString method, leading to memory exhaustion. This issue affects versions from 1.3.3 to before 2.0.11. Users should upgrade to version 2.0.11 to fix the issue. The vulnerability can lead to large-scale memory exhaustion, affecting users of the Apache IoTDB JDBC driver.
Defensive priority
Upgrade to version 2.0.11
Recommended defensive actions
- Upgrade to version 2.0.11
- Review and update affected systems
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The CVE record and source item provide information on the vulnerability and affected versions. The issue is caused by the BigDecimal toPlainString method in the JDBC driver. The vulnerability affects versions from 1.3.3 to before 2.0.11. Users should upgrade to version 2.0.11 to fix the issue. The source item provides vulnerability details, and the CVE record was published on 2026-10-21T11:07:24.947Z.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-41114 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-41114
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-41114 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-41114
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Apache IoTDB JDBC driver: Large-scale Memory Exhaustion via BigDecimal toPlainString in JDBC Dri
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/41xxx/CVE-2026-41114.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://lists.apache.org/thread.html/tvmqslwyqmglr19dccck1s3rxqypj4zc
Supplemental source - vendor-advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.