dbcve.org
CWE-470Weakness · CWE-470

CVE-2026-40008

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Apache IoTDB. The pipe processor reads a fully qualified Java class name and instantiates it using Class.forName().newInstance() without any validation or allowlisting. This issue affects Apache IoTDB: from 1.0.0 before 2.0.10. Users are recommended to upgrade to version 2.0.10, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The pipe processor in Apache IoTDB uses Class.forName().newInstance() to dynamically load Java classes based on user-supplied fully qualified class names without any validation or allowlisting. This unsafe reflection allows remote attackers to instantiate arbitrary classes, potentially achieving remote code execution.

MitigationUpgrade Apache IoTDB to version 2.0.10 or later, which implements proper class name validation or allowlisting to prevent arbitrary class instantiation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache IoTDB installed version
    Run 'grep -r "version"' or check release notes in the IoTDB installation directory, or use any version-checking command provided by your IoTDB distribution
    Affected if The version is prior to 2.0.10 (e.g., 2.0.0 through 2.0.9, or any pre-2.0 release)
  2. Locate IoTDB configuration files
    Find the main IoTDB configuration directory (commonly under conf/ or config/ in the installation root)
    Affected if Configuration files exist, indicating an active IoTDB installation that could be running the vulnerable code
  3. Check for pipe processor configuration
    Search configuration files for pipe-related settings, such as entries containing 'pipe', 'processor', or 'class' that define pipe processing behavior
    Affected if Pipe processor is configured with custom class definitions (any 'class' parameter pointing to user-supplied fully qualified class names)
  4. Inspect active pipe definitions
    Query the running IoTDB instance or check pipe definition files for any pipe tasks that reference custom class loaders
    Affected if Any pipe definition specifies a custom class name via user-controlled parameters
  5. Review audit or access logs for class loading patterns
    Examine IoTDB logs for patterns like Class.forName() invocations or dynamic class loading requests, especially with unknown or external class names
    Affected if Logs show dynamic class loading requests for classes not part of the standard IoTDB distribution

You are affected if running any Apache IoTDB version prior to 2.0.10 AND the pipe processor feature is enabled with user-supplied class names in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache IoTDB to version 2.0.10 or later, which implements proper class name validation or allowlisting to prevent arbitrary class instantiation.

Recommended fix High confidence

2.0.10

  1. 1. Back up the current Apache IoTDB installation, configuration files, and data directories before proceeding.
  2. 2. Stop the running Apache IoTDB service to prevent data corruption during upgrade.
  3. 3. Download Apache IoTDB version 2.0.10 from the official Apache IoTDB downloads page (https://iotdb.apache.org/Download/).
  4. 4. Install or upgrade to version 2.0.10 following the standard Apache IoTDB upgrade procedure for your deployment method (binary installation or from source).
  5. 5. Restore any custom configuration files from the backup, ensuring compatibility with version 2.0.10.
  6. 6. Start the Apache IoTDB service and verify it runs without errors.
  7. 7. Test that the pipe processor functionality works correctly with the new version.
Caveat Specific breaking changes are not detailed in the provided material; however, always review release notes before upgrading in production environments.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40008 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data