VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/alibabacloud-go/tea: vulnerability history, versions and safety

github.com/alibabacloud-go/tea is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go 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.

See all github.com/alibabacloud-go/tea vulnerabilities

Vulert verdict on github.com/alibabacloud-go/tea v1.5.3 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v1.5.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 43 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/alibabacloud-go/tea, 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
v1.5.4-0.20261009053536-fc408f7e5774 09 Oct 2026 none Apache-2.0 — Details →
v1.5.4-0.20260721120812-440b2ee03812 21 Jul 2026 none Apache-2.0 — Details →
v1.5.3 21 Jul 2026 none Apache-2.0 — Details →
v1.5.2 25 Jun 2026 none Apache-2.0 — Details →
v1.5.1 15 Jun 2026 none Apache-2.0 — Details →
v1.5.1-0.20260608021449-0802f0e3dccf 08 Jun 2026 none Apache-2.0 — Details →
v1.4.1-0.20260526084156-3ae6caaf9cdc 26 May 2026 none Apache-2.0 — Details →
v1.5.0 26 May 2026 none Apache-2.0 — Details →
v1.4.0 06 Jan 2026 none Apache-2.0 — Details →
v1.3.14 08 Dec 2025 none Apache-2.0 — Details →
v1.3.14-0.20251128100518-6d0a6ab32ad5 28 Nov 2025 none Apache-2.0 — Details →
v1.3.13 13 Oct 2025 none Apache-2.0 — Details →
v1.3.12 11 Sep 2025 none Apache-2.0 — Details →
v1.3.12-0.20250909074006-bbd3ea534464 09 Sep 2025 none Apache-2.0 — Details →
v1.3.11 19 Aug 2025 none Apache-2.0 — Details →
v1.3.10 23 Jul 2025 none Apache-2.0 — Details →
v1.3.9 21 Apr 2025 none Apache-2.0 — Details →
v1.3.8 07 Apr 2025 none Apache-2.0 — Details →
v1.3.6 27 Mar 2025 none Apache-2.0 — Details →
v1.3.7 27 Mar 2025 none Apache-2.0 — Details →
v1.3.5-0.20250326122900-7af78f311e78 26 Mar 2025 none Apache-2.0 — Details →
v1.3.5-0.20250326112604-a17e6d71bae5 26 Mar 2025 none Apache-2.0 — Details →
v1.3.5 25 Mar 2025 none Apache-2.0 — Details →
v1.3.5-0.20250325130701-5379d4dfbb7f 25 Mar 2025 none Apache-2.0 — Details →
v1.3.5-0.20250325124449-027c7539de1d 25 Mar 2025 none Apache-2.0 — Details →
v1.3.4 14 Mar 2025 none Apache-2.0 — Details →
v1.3.3 12 Mar 2025 none Apache-2.0 — Details →
v1.3.3-0.20250312075116-c032b7c3e5b4 12 Mar 2025 none Apache-2.0 — Details →
v1.3.3-0.20250311130820-171239d81914 11 Mar 2025 none Apache-2.0 — Details →
v1.3.2 25 Feb 2025 none Apache-2.0 — Details →
v1.3.2-0.20250225033757-8d3b5385f0fa 25 Feb 2025 none Apache-2.0 — Details →
v1.3.2-0.20250217084427-cf679a8bddfe 17 Feb 2025 none Apache-2.0 — Details →
v1.3.1 12 Feb 2025 none Apache-2.0 — Details →
v1.3.0 12 Feb 2025 none Apache-2.0 — Details →
v1.2.3-0.20250120120248-40fd48a7bbcd 20 Jan 2025 none Apache-2.0 — Details →
v1.2.3-0.20240821124219-b8dbae11d905 21 Aug 2024 none Apache-2.0 — Details →
v1.2.3-0.20240605082020-e6e537a31150 05 Jun 2024 none Apache-2.0 — Details →
v1.2.3-0.20240528133401-8788f78f9c46 28 May 2024 none Apache-2.0 — Details →
v1.2.3-0.20240528053943-f2ffca406c76 28 May 2024 none Apache-2.0 — Details →
v1.2.3-0.20240527125706-cc29d398161e 27 May 2024 none Apache-2.0 — Details →
v1.2.3-0.20240322055316-8e3b4252f0d1 22 Mar 2024 none Apache-2.0 — Details →
v1.2.2 22 Jan 2024 none Apache-2.0 — Details →
v1.2.2-0.20240122093017-bb7ae5fd3e46 22 Jan 2024 none Apache-2.0 — Details →
v1.2.2-0.20240122092627-a069442cb216 22 Jan 2024 none Apache-2.0 — Details →
v1.2.2-0.20240122091714-c1f8e3239998 22 Jan 2024 none Apache-2.0 — Details →
v1.2.2-0.20240122091209-b81493c626ef 22 Jan 2024 none Apache-2.0 — Details →
v1.2.2-0.20240122085109-de3f51116040 22 Jan 2024 none Apache-2.0 — Details →
v1.2.2-0.20231020034846-185150a903d0 20 Oct 2023 none Apache-2.0 — Details →
v1.2.2-0.20231019035449-f88b9117be29 19 Oct 2023 none Apache-2.0 — Details →
v1.2.2-0.20231017141040-c9d4d2cbbbed 17 Oct 2023 none Apache-2.0 — Details →
v1.2.1 28 Jun 2023 none Apache-2.0 — Details →
v1.2.1-0.20230628094615-2b0e131d0014 28 Jun 2023 none Apache-2.0 — Details →
v1.2.1-0.20230515074051-121efa4413dd 15 May 2023 none Apache-2.0 — Details →
v1.2.1-0.20230515073625-aa99f50b3f99 15 May 2023 none Apache-2.0 — Details →
v1.1.21-0.20230508085258-cb3a42bc23a2 08 May 2023 none Apache-2.0 — Details →
v1.2.0 08 May 2023 none Apache-2.0 — Details →
v1.1.21-0.20230426033233-e158cc5dc597 26 Apr 2023 none Apache-2.0 — Details →
v1.1.21-0.20230426032759-636d89faa76a 26 Apr 2023 none Apache-2.0 — Details →
v1.1.21-0.20230426032146-c4f78703d745 26 Apr 2023 none Apache-2.0 — Details →
v1.1.21-0.20230426032133-8a7c8512f875 26 Apr 2023 none Apache-2.0 — Details →
v1.1.21-0.20230426031845-e717c11b4a76 26 Apr 2023 none Apache-2.0 — Details →
v1.1.21-0.20230323071214-02f393be3ff1 23 Mar 2023 none Apache-2.0 — Details →
v1.1.21-0.20230323070417-bcb5bffbc705 23 Mar 2023 none Apache-2.0 — Details →
v1.1.20 20 Oct 2022 none Apache-2.0 — Details →
v1.1.20-0.20221020075655-b9ace42a5b69 20 Oct 2022 none Apache-2.0 — Details →
v1.1.19 20 Jun 2022 none Apache-2.0 — Details →
v1.1.18 14 Jun 2022 none Apache-2.0 — Details →
v1.1.18-0.20220614081613-e0a739a68172 14 Jun 2022 none Apache-2.0 — Details →
v0.0.0-20210723055408-d9ff2bfbeb30 23 Jul 2021 none Apache-2.0 — Details →
v1.1.17 23 Jul 2021 none Apache-2.0 — Details →
v1.1.17-0.20210723055408-d9ff2bfbeb30 23 Jul 2021 none Apache-2.0 — Details →
v0.0.0-20210519014226-fc13b6ebeec5 19 May 2021 none Apache-2.0 — Details →
v1.1.16 19 May 2021 none Apache-2.0 — Details →
v1.1.15 26 Jan 2021 none Apache-2.0 — Details →
v1.1.14 18 Jan 2021 none Apache-2.0 — Details →
v1.1.13 06 Jan 2021 none Apache-2.0 — Details →
v1.1.12 30 Nov 2020 none Apache-2.0 — Details →
v1.1.11 19 Oct 2020 none Apache-2.0 — Details →
v1.1.10 08 Sep 2020 none Apache-2.0 — Details →
v1.1.9 07 Sep 2020 none Apache-2.0 — Details →
v1.1.8 21 Aug 2020 none Apache-2.0 — Details →
v1.1.8-0.20200716074136-f16f5b0116d6 16 Jul 2020 none Apache-2.0 — Details →
v1.1.7 09 Jul 2020 none Apache-2.0 — Details →
v1.1.6 09 Jul 2020 none Apache-2.0 — Details →
v1.1.5 08 Jul 2020 none Apache-2.0 — Details →
v1.1.4 06 Jul 2020 none Apache-2.0 — Details →
v1.1.3 03 Jul 2020 none Apache-2.0 — Details →
v1.1.2 22 Jun 2020 none Apache-2.0 — Details →
v1.1.1 13 May 2020 none Apache-2.0 — Details →
v1.1.0 11 May 2020 none Apache-2.0 — Details →
v1.0.2 09 May 2020 none Apache-2.0 — Details →
v1.0.1 08 May 2020 none Apache-2.0 — Details →
v1.0.0 20 Apr 2020 none Apache-2.0 — Details →
v0.0.12 03 Apr 2020 none Apache-2.0 — Details →
v0.0.11 20 Mar 2020 none Apache-2.0 — Details →
v0.0.10 20 Mar 2020 none Apache-2.0 — Details →
v0.0.9 12 Mar 2020 none Apache-2.0 — Details →
v0.0.8 11 Mar 2020 none Apache-2.0 — Details →
v0.0.7 02 Mar 2020 none Apache-2.0 — Details →
v0.0.6 02 Mar 2020 none Apache-2.0 — Details →
v0.0.0-20200224110052-b8b38f503203 24 Feb 2020 none — — Details →
v0.0.5 24 Feb 2020 none — — Details →
v0.0.4 24 Feb 2020 none — — Details →
v0.0.3 24 Feb 2020 none — — Details →
v0.0.2 06 Feb 2020 none — — Details →
v0.0.0-20200103025801-3e754bc30e91 03 Jan 2020 none — — Details →
v0.0.1 03 Jan 2020 none — — Details →
v0.0.0-20191231032509-ac31e098dc2a 31 Dec 2019 none — — Details →
v0.0.0-20191219084903-1b923fea9df6 19 Dec 2019 none — — Details →
v0.0.0-20191213065341-8da7978c8dcd 13 Dec 2019 none — — Details →
v0.0.0-20191205092156-3300b502babd 05 Dec 2019 none — — Details →
v0.0.0-20191204070732-fdaeb4c99539 04 Dec 2019 none — — Details →
v0.0.0-20191113071536-aad460157047 13 Nov 2019 none — — Details →
v0.0.0-20191104093916-c8bed262c823 04 Nov 2019 none — — Details →
v0.0.0-20191011054747-c132d91088dc 11 Oct 2019 none — — Details →
v0.0.0-20190904065550-5b8aa8ff06ef 04 Sep 2019 none — — Details →

All 116 versions Vulert tracks for this package. 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 github.com/alibabacloud-go/tea

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 github.com/alibabacloud-go/tea

Is github.com/alibabacloud-go/tea safe to use?

Vulert has no vulnerabilities on record for github.com/alibabacloud-go/tea in Go 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 github.com/alibabacloud-go/tea's Vulert package health score?

Vulert scores github.com/alibabacloud-go/tea 68/100, which reads as usable, but worth attention. 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 github.com/alibabacloud-go/tea affected?

No. v1.5.3, 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 github.com/alibabacloud-go/tea should I use?

v1.5.3 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 github.com/alibabacloud-go/tea have?

0 vulnerabilities are recorded for github.com/alibabacloud-go/tea in the Go 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 github.com/alibabacloud-go/tea vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/alibabacloud-go/tea 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 github.com/alibabacloud-go/tea 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 github.com/alibabacloud-go/tea for upcoming vulnerabilities?

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