VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.google.crypto.tink:tink: vulnerability history, versions and safety

com.google.crypto.tink:tink is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 17 releases, first recorded in Oct 2020. 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 com.google.crypto.tink:tink vulnerabilities

Vulert verdict on com.google.crypto.tink:tink 1.24.0 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 1.24.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 16 Oct 2020 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Stars 309 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 com.google.crypto.tink:tink, 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
1.24.0 16 Oct 2026 none Apache-2.0 — Details →
1.23.0 09 Jul 2026 none Apache-2.0 — Details →
1.22.0 18 Jun 2026 none Apache-2.0 — Details →
1.21.0 24 Mar 2026 none Apache-2.0 — Details →
1.20.0 09 Dec 2025 none Apache-2.0 — Details →
1.19.0 21 Oct 2025 none Apache-2.0 — Details →
1.18.0 18 Jun 2025 none Apache-2.0 — Details →
1.17.0 13 Mar 2025 none Apache-2.0 — Details →
1.16.0 18 Dec 2024 none Apache-2.0 — Details →
1.15.0 30 Aug 2024 none Apache-2.0 — Details →
1.14.1 05 Aug 2024 none Apache-2.0 — Details →
1.14.0 03 Jul 2024 none Apache-2.0 — Details →
1.13.0 02 Apr 2024 none Apache-2.0 — Details →
1.12.0 05 Dec 2023 none Apache-2.0 — Details →
1.11.0 22 Sep 2023 none Apache-2.0 — Details →
1.10.0 17 Jul 2023 none Apache-2.0 — Details →
1.9.0 20 Apr 2023 none Apache-2.0 — Details →
1.8.0 22 Feb 2023 none Apache-2.0 — Details →
1.7.0 10 Aug 2022 none Apache-2.0 — Details →
1.6.1 12 Jul 2021 none Apache-2.0 — Details →
1.6.0 17 May 2021 none Apache-2.0 — Details →
1.5.0 15 Oct 2020 none Apache-2.0 — Details →
1.4.0 14 Jul 2020 M1 Apache-2.0 Yes Details →
1.4.0-rc2 15 May 2020 M1 Apache-2.0 Yes Details →
1.4.0-rc1 30 Apr 2020 M1 Apache-2.0 Yes Details →
1.3.0 12 Mar 2020 M1 Apache-2.0 Yes Details →
1.3.0-rc4 20 Feb 2020 M1 Apache-2.0 Yes Details →
1.3.0-rc3 20 Dec 2019 M1 Apache-2.0 Yes Details →
1.3.0-rc2 26 Nov 2019 M1 Apache-2.0 Yes Details →
1.3.0-rc1 01 Jul 2019 M1 Apache-2.0 Yes Details →
1.2.2 25 Jan 2019 M1 Apache-2.0 Yes Details →
1.2.1 16 Nov 2018 M1 Apache-2.0 Yes Details →
1.2.0 09 Aug 2018 M1 Apache-2.0 Yes Details →
1.2.0-rc4 01 Aug 2018 M1 Apache-2.0 Yes Details →
1.2.0-rc3 27 Jul 2018 M1 Apache-2.0 Yes Details →
1.2.0-rc2 13 Jul 2018 M1 Apache-2.0 Yes Details →
1.1.1 26 May 2018 M1 Apache-2.0 Yes Details →
1.1.0 19 Apr 2018 M1 Apache-2.0 Yes Details →
1.0.0 09 Sep 2017 M1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 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 com.google.crypto.tink:tink

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-8929: Ciphertext Malleability Issue in Tink Java 5.3 medium 1.5.0 16 Oct 2020

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.google.crypto.tink:tink

Is com.google.crypto.tink:tink safe to use?

Vulert records 1 vulnerabilities for com.google.crypto.tink:tink 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 com.google.crypto.tink:tink's Vulert package health score?

Vulert scores com.google.crypto.tink:tink 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.google.crypto.tink:tink affected?

No. 1.24.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 com.google.crypto.tink:tink have?

1 vulnerability is recorded for com.google.crypto.tink:tink 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 com.google.crypto.tink:tink vulnerabilities disclosed?

0 vulnerabilities were recorded for com.google.crypto.tink:tink in the last 12 months, and the oldest entry in this database dates to 16 Oct 2020. 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.google.crypto.tink:tink 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.google.crypto.tink:tink for upcoming vulnerabilities?

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