Vulnerability Database · Maven · Package report

com.aliyun:aliyun-java-sdk-core: vulnerability history, versions and safety

com.aliyun:aliyun-java-sdk-core is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

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.

Vulert verdict on com.aliyun:aliyun-java-sdk-core 4.7.10 i

Updated on 23 Oct 2026

Good news: 4.7.10, the version you would install today, has no known vulnerabilities.

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

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

  • Current release 4.7.10 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 23 packages i
  • Stars 1,416 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 months 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 com.aliyun:aliyun-java-sdk-core, 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
4.7.10 26 Jun 2026 none Apache-2.0 — Details →
4.7.9 24 Jun 2026 none Apache-2.0 — Details →
4.7.8 16 Dec 2025 none Apache-2.0 — Details →
4.7.6 10 Jun 2025 none Apache-2.0 — Details →
4.7.4-20250509-hotfix 09 May 2025 none Apache-2.0 — Details →
4.7.5 18 Apr 2025 none Apache-2.0 — Details →
4.7.4-20250416-hotfix 16 Apr 2025 none Apache-2.0 — Details →
4.7.4 11 Apr 2025 none Apache-2.0 — Details →
4.7.3 04 Dec 2024 none Apache-2.0 — Details →
3.7.2 16 Oct 2024 none — — Details →
4.7.2 27 Sep 2024 none Apache-2.0 — Details →
4.7.1 23 Jul 2024 none Apache-2.0 — Details →
4.7.0 08 Jul 2024 none Apache-2.0 — Details →
4.6.4 06 Sep 2023 none Apache-2.0 — Details →
4.6.3 23 Nov 2022 none Apache-2.0 — Details →
4.6.2 14 Sep 2022 none Apache-2.0 — Details →
4.6.1 04 Aug 2022 none Apache-2.0 — Details →
4.6.0 04 Jan 2022 none Apache-2.0 — Details →
4.5.30 08 Nov 2021 none — — Details →
4.5.29 04 Nov 2021 none — — Details →
4.5.28 03 Nov 2021 none — — Details →
4.5.25 05 Aug 2021 none — — Details →
4.5.24 23 Jul 2021 none — — Details →
4.5.23 23 Jul 2021 none — — Details →
4.5.22 28 Jun 2021 none — — Details →
4.5.21 22 Jun 2021 none — — Details →
4.5.20 29 Mar 2021 none — — Details →
4.5.19 23 Mar 2021 none — — Details →
4.5.18 24 Jan 2021 none — — Details →
4.5.17 27 Nov 2020 none — — Details →
4.5.16 10 Nov 2020 none — — Details →
4.5.15 09 Nov 2020 none — — Details →
4.5.14 29 Oct 2020 none — — Details →
4.5.13 13 Oct 2020 none — — Details →
4.5.12 29 Sep 2020 none — — Details →
4.5.11 24 Sep 2020 none — — Details →
4.5.10 15 Sep 2020 none — — Details →
4.5.9 11 Sep 2020 none — — Details →
4.5.8 31 Aug 2020 none — — Details →
4.5.7 18 Aug 2020 none — — Details →
4.5.6 03 Aug 2020 none — — Details →
4.5.5 28 Jul 2020 none — — Details →
4.5.4 22 Jul 2020 none — — Details →
4.5.3 03 Jul 2020 none — — Details →
4.5.2 05 Jun 2020 none — — Details →
4.5.1 01 Apr 2020 none — — Details →
4.5.0 07 Feb 2020 none — — Details →
4.4.9 27 Nov 2019 none — — Details →
4.4.8 25 Nov 2019 none — — Details →
4.4.7 15 Nov 2019 none — — Details →
4.4.6 30 Sep 2019 none — — Details →
4.4.5 16 Sep 2019 none — — Details →
4.4.4 04 Sep 2019 none — — Details →
4.4.3 05 Aug 2019 none — — Details →
4.4.2 27 May 2019 none — — Details →
4.4.1 19 Apr 2019 none — — Details →
4.4.0 04 Apr 2019 none — — Details →
4.3.9 29 Mar 2019 none — — Details →
4.3.8 25 Mar 2019 none — — Details →
4.3.7 21 Mar 2019 none — — Details →
4.3.6 20 Mar 2019 none — — Details →
4.3.5 01 Mar 2019 none — — Details →
4.3.4 19 Feb 2019 none — — Details →
4.3.3 01 Feb 2019 none — — Details →
4.3.2 16 Jan 2019 none — — Details →
4.3.1 15 Jan 2019 none — — Details →
4.3.0 07 Jan 2019 none — — Details →
4.2.5 27 Dec 2018 none — — Details →
4.2.4 20 Dec 2018 none — — Details →
4.2.3 14 Dec 2018 none — — Details →
4.2.2 19 Nov 2018 none — — Details →
4.2.1 14 Nov 2018 none — — Details →
4.2.0 07 Nov 2018 none — — Details →
4.1.2 11 Oct 2018 none — — Details →
4.1.1 29 Sep 2018 none — — Details →
4.1.0 21 Sep 2018 none — — Details →
4.0.9 12 Sep 2018 none — — Details →
4.0.8 17 Aug 2018 none — — Details →
4.0.7 14 Aug 2018 none — — Details →
4.0.6 02 Aug 2018 none — — Details →
4.0.5 02 Aug 2018 none — — Details →
4.0.4 02 Aug 2018 none — — Details →
4.0.3 04 Jul 2018 none — — Details →
4.0.2 24 May 2018 none — — Details →
4.0.1 04 May 2018 none — — Details →
4.0.0 18 Apr 2018 none — — Details →
3.7.1 13 Apr 2018 none — — Details →
3.7.0 13 Apr 2018 none — — Details →
3.6.0 20 Mar 2018 none — — Details →
3.4.1 05 Feb 2018 none — — Details →
3.5.1 30 Jan 2018 none — — Details →
3.5.0 01 Nov 2017 none — — Details →
3.4.0 14 Oct 2017 none — — Details →
3.3.1 22 Sep 2017 none — — Details →
3.3.0 22 Sep 2017 none — — Details →
3.2.10 06 Sep 2017 none — — Details →
3.2.9 25 Aug 2017 none — — Details →
3.2.8 14 Aug 2017 none — — Details →
3.2.7 11 Aug 2017 none — — Details →
3.2.6 27 Jul 2017 none — — Details →
3.2.5 25 Jul 2017 none — — Details →
3.2.3 13 Jul 2017 none — — Details →
3.2.4 02 Jun 2017 none — — Details →
3.2.2 30 Mar 2017 none — — Details →
3.2.1 23 Mar 2017 none — — Details →
3.2.0 21 Mar 2017 none — — Details →
3.1.1 08 Mar 2017 none — — Details →
3.1.0 23 Feb 2017 none — — Details →
3.0.10 22 Feb 2017 none — — Details →
3.0.9 15 Dec 2016 none — — Details →
3.0.8 19 Sep 2016 none — — Details →
3.0.7 29 Aug 2016 none — — Details →
3.0.6 16 Aug 2016 none — — Details →
3.0.5 10 Aug 2016 none — — Details →
3.0.4 28 Jul 2016 none — — Details →
3.0.3 12 Jul 2016 none — — Details →
3.0.1 20 Jun 2016 none — — Details →
3.0.0 27 May 2016 none — — Details →
2.4.4 12 May 2016 none — — Details →
2.4.3 25 Apr 2016 none — — Details →

The newest 120 of 155 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for com.aliyun:aliyun-java-sdk-core

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 com.aliyun:aliyun-java-sdk-core

Is com.aliyun:aliyun-java-sdk-core safe to use?

Vulert has no vulnerabilities on record for com.aliyun:aliyun-java-sdk-core in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is com.aliyun:aliyun-java-sdk-core's Vulert package health score?

Vulert scores com.aliyun:aliyun-java-sdk-core 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 com.aliyun:aliyun-java-sdk-core affected?

No. 4.7.10, 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 com.aliyun:aliyun-java-sdk-core should I use?

4.7.10 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 com.aliyun:aliyun-java-sdk-core have?

0 vulnerabilities are recorded for com.aliyun:aliyun-java-sdk-core in the Maven ecosystem: 0 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 com.aliyun:aliyun-java-sdk-core vulnerabilities disclosed?

0 vulnerabilities were recorded for com.aliyun:aliyun-java-sdk-core in the last 12 months. 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 com.aliyun:aliyun-java-sdk-core 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 com.aliyun:aliyun-java-sdk-core for upcoming vulnerabilities?

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