VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.iotdb:node-commons: vulnerability history, versions and safety

org.apache.iotdb:node-commons is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 15 releases, first recorded in May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.iotdb:node-commons vulnerabilities

Vulert verdict on org.apache.iotdb:node-commons 2.0.11 i

Updated on 23 Oct 2026

Good news: 2.0.11, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

What to do: Stay on 2.0.11 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.0.11 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.0.11 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 14 May 2025 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Depended on by 13 packages i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.iotdb:node-commons, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.0.11 07 Sep 2026 none Apache-2.0 — Details →
2.0.10 03 Jul 2026 none Apache-2.0 — Details →
2.0.8 10 Apr 2026 none Apache-2.0 — Details →
1.3.7 27 Feb 2026 none Apache-2.0 — Details →
2.0.7 26 Feb 2026 none Apache-2.0 — Details →
2.0.6 15 Jan 2026 none Apache-2.0 — Details →
1.3.6 25 Dec 2025 none Apache-2.0 — Details →
1.3.5 08 Sep 2025 none Apache-2.0 — Details →
2.0.5 18 Aug 2025 none Apache-2.0 — Details →
2.0.4 03 Jul 2025 none Apache-2.0 — Details →
2.0.3 27 May 2025 none Apache-2.0 — Details →
1.3.4-1 17 May 2025 none Apache-2.0 — Details →
2.0.2-1 17 May 2025 none Apache-2.0 — Details →
2.0.2 14 Apr 2025 none Apache-2.0 — Details →
1.3.4 14 Apr 2025 none Apache-2.0 — Details →
2.0.1-beta 13 Feb 2025 none Apache-2.0 — Details →
1.3.3 17 Nov 2024 M1 Apache-2.0 Yes Details →
1.3.2 27 Jun 2024 M1 Apache-2.0 Yes Details →
1.3.1 19 Apr 2024 M1 Apache-2.0 Yes Details →
1.3.0 27 Dec 2023 M1 Apache-2.0 Yes Details →
1.2.2 11 Oct 2023 M1 Apache-2.0 Yes Details →
1.2.1 15 Sep 2023 M1 Apache-2.0 Yes Details →
1.2.0 05 Sep 2023 M1 Apache-2.0 Yes Details →
1.1.2 24 Jul 2023 M1 Apache-2.0 Yes Details →
1.1.1 10 Jun 2023 M1 Apache-2.0 Yes Details →
1.1.0 31 Mar 2023 M1 Apache-2.0 Yes Details →
1.0.1 17 Feb 2023 M1 Apache-2.0 Yes Details →
1.0.0 02 Dec 2022 M1 Apache-2.0 Yes Details →
0.14.0-preview3 14 Oct 2022 M1 Apache-2.0 Yes Details →
0.14.0-preview2 07 Sep 2022 M1 Apache-2.0 Yes Details →
0.14.0-preview1 29 Jun 2022 M1 Apache-2.0 Yes Details →

All 31 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.iotdb:node-commons

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-26864: Apache IoTDB node-commons Sensitive Information Disclosure Vulnerability 6.9 medium 1.3.4 14 May 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.iotdb:node-commons

Is org.apache.iotdb:node-commons safe to use?

Vulert records 1 vulnerabilities for org.apache.iotdb:node-commons in Maven: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.iotdb:node-commons's Vulert package health score?

Vulert scores org.apache.iotdb:node-commons 89/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.apache.iotdb:node-commons affected?

No. 2.0.11, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.apache.iotdb:node-commons should I use?

2.0.11 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.iotdb:node-commons have?

1 vulnerability is recorded for org.apache.iotdb:node-commons in the Maven ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.iotdb:node-commons vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.iotdb:node-commons in the last 12 months, and the oldest entry in this database dates to 14 May 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.iotdb:node-commons are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.iotdb:node-commons for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.iotdb:node-commons version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.