VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

ai.djl:api: vulnerability history, versions and safety

ai.djl:api is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 33 releases, from Jun 2024 to Jan 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C2
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 ai.djl:api vulnerabilities

Vulert verdict on ai.djl:api 0.39.0 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 0.39.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 29 Jan 2025 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 28 packages i
  • Stars 4,857 i
  • OpenSSF scorecard 6/10 i
  • Last release this month 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 ai.djl:api, 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
0.39.0 20 Oct 2026 none Apache-2.0 — Details →
0.38.0 09 Sep 2026 none Apache-2.0 — Details →
0.37.0 04 Sep 2026 none Apache-2.0 — Details →
0.36.0 16 Dec 2025 none Apache-2.0 — Details →
0.35.1 03 Dec 2025 none Apache-2.0 — Details →
0.35.0 20 Oct 2025 none Apache-2.0 — Details →
0.34.0 12 Aug 2025 none Apache-2.0 — Details →
0.33.0 09 May 2025 none Apache-2.0 — Details →
0.32.0 07 Feb 2025 none Apache-2.0 — Details →
0.31.1 19 Dec 2024 none Apache-2.0 — Details →
0.31.0 18 Nov 2024 C1 Apache-2.0 Yes Details →
0.30.0 12 Sep 2024 C1 Apache-2.0 Yes Details →
0.29.0 18 Jul 2024 C1 Apache-2.0 Yes Details →
0.28.0 15 May 2024 C1 Apache-2.0 Yes Details →
0.27.0 28 Mar 2024 C2 Apache-2.0 Yes Details →
0.26.0 10 Jan 2024 C2 Apache-2.0 Yes Details →
0.25.0 05 Nov 2023 C2 Apache-2.0 Yes Details →
0.24.0 02 Oct 2023 C2 Apache-2.0 Yes Details →
0.23.0 11 Jul 2023 C2 Apache-2.0 Yes Details →
0.22.1 17 Apr 2023 C2 Apache-2.0 Yes Details →
0.22.0 12 Apr 2023 C2 Apache-2.0 Yes Details →
0.21.0 16 Feb 2023 C2 Apache-2.0 Yes Details →
0.20.0 29 Nov 2022 C2 Apache-2.0 Yes Details →
0.19.0 13 Sep 2022 C2 Apache-2.0 Yes Details →
0.18.0 09 Jul 2022 C2 Apache-2.0 Yes Details →
0.17.0 10 May 2022 C2 Apache-2.0 Yes Details →
0.16.0 20 Mar 2022 C2 Apache-2.0 Yes Details →
0.15.0 18 Jan 2022 C2 Apache-2.0 Yes Details →
0.14.0 09 Nov 2021 C2 Apache-2.0 Yes Details →
0.13.0 11 Oct 2021 C2 Apache-2.0 Yes Details →
0.12.0 08 Jul 2021 C2 Apache-2.0 Yes Details →
0.11.0 01 May 2021 C2 Apache-2.0 Yes Details →
0.10.0 23 Feb 2021 C2 Apache-2.0 Yes Details →
0.9.0 18 Dec 2020 C2 Apache-2.0 Yes Details →
0.8.0 22 Sep 2020 C2 Apache-2.0 Yes Details →
0.7.0 03 Sep 2020 C2 Apache-2.0 Yes Details →
0.6.0 24 Jun 2020 C2 Apache-2.0 Yes Details →
0.5.0 12 May 2020 C2 Apache-2.0 Yes Details →
0.4.1 03 Apr 2020 C2 Apache-2.0 Yes Details →
0.4.0 28 Mar 2020 C2 Apache-2.0 Yes Details →
0.3.0 22 Feb 2020 C2 Apache-2.0 Yes Details →
0.2.1 15 Jan 2020 C2 Apache-2.0 Yes Details →
0.2.0 27 Nov 2019 C2 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for ai.djl:api

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-37902: DeepJavaLibrary API absolute path traversal 10.0 critical 0.28.0 17 Jun 2024
CVE-2025-0851: Deep Java Library Path Traversal Vulnerability 9.8 critical 0.31.1 29 Jan 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 ai.djl:api

Is ai.djl:api safe to use?

Vulert records 2 vulnerabilities for ai.djl:api in Maven: 2 critical, 0 high, 0 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 ai.djl:api's Vulert package health score?

Vulert scores ai.djl:api 81/100, which reads as in good shape. 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 ai.djl:api affected?

No. 0.39.0, 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.

How many vulnerabilities does ai.djl:api have?

2 vulnerabilities are recorded for ai.djl:api in the Maven ecosystem: 2 critical, 0 high, 0 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 ai.djl:api vulnerabilities disclosed?

0 vulnerabilities were recorded for ai.djl:api in the last 12 months, and the oldest entry in this database dates to 17 Jun 2024. 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 ai.djl:api 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 ai.djl:api for upcoming vulnerabilities?

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