maven package report

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

1 known vulnerability, worst severity MODERATE.

cvss
5.3

how bad it is if exploited, out of 10

epss
0.50%

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-g5vf-v6wf-7w2r, the advisory selected below

// advisories

GHSA-g5vf-v6wf-7w2r

MODERATECVE-2020-8929

Tink's Java version before 1.5 under some circumstances allowed attackers to change the key ID part of the ciphertext, resulting in the attacker creating a second ciphertext that will decrypt to the same plaintext. This can be a problem in particular in the case of encrypting with a deterministic AEAD with a single key, and relying on the fact that there is only a single valid ciphertext per plain

Affected
< 1.5.0
Fixed in
1.5.0
Weakness
CWE-176
Published
2020-10-16
Source
github

GHSANVDMITREreferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so maven packages are not covered.

Checked 2026-09-22 at 00:46 UTC. The most recent advisory here was published 2020-10-16. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is com.google.crypto.tink:tink safe? maven package security report | CyberXYZ