VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/kudelskisecurity/crystals-go: vulnerability history, versions and safety

github.com/kudelskisecurity/crystals-go is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 27 releases, first recorded in Jan 2024. 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 H1 U1
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/kudelskisecurity/crystals-go vulnerabilities

Vulert verdict on github.com/kudelskisecurity/crystals-go v0.0.0-20240116172146-2a6ca2d4e64d i

Updated on 23 Oct 2026

Action needed: v0.0.0-20240116172146-2a6ca2d4e64d has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 62/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v0.0.0-20240116172146-2a6ca2d4e64d — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 17 Jan 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 81 i
  • OpenSSF scorecard 3/10 i
  • Last release 33 months ago i
  • Licence CC0-1.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/kudelskisecurity/crystals-go, 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
v0.0.0-20240116172146-2a6ca2d4e64d 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116171358-5d875a1f686d 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116171206-d457a8c24fe4 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116170842-1ac280896f8b 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116170201-18058ddfc4f8 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116165214-8380db837e95 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116164408-a7cf5ef51b8d 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116164145-ea1b61200d43 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116163731-d0631a8e55f8 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116163204-bffe8563a845 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116162755-b1c357381141 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116162548-edd8c6e34e16 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240116162333-d2370c3451b1 16 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240110155413-56534a791e8e 10 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240110154625-2c751b9bc9d7 10 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240110153620-c06ce985b2b8 10 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240110153505-026dfbcefbaf 10 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20240110151210-390826690a51 10 Jan 2024 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20210705112123-14b89bfbcdc8 05 Jul 2021 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20210629082329-616a8dfdba88 29 Jun 2021 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20210617121433-b283a6eb131e 17 Jun 2021 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20210617091254-3d048738bcce 17 Jun 2021 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20210617091226-3f5405831ad7 17 Jun 2021 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20210616155037-9b34b7dc28da 16 Jun 2021 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20210528171216-013a6c610b6d 28 May 2021 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20210528165814-ffd4ee941498 28 May 2021 H1 U1 CC0-1.0 Yes Details →
v0.0.0-20210420063622-7dca35759c14 20 Apr 2021 H1 U1 — Yes Details →

All 27 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 2

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 github.com/kudelskisecurity/crystals-go

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Kyberslash Timing Attack in github.com/kudelskisecurity/crystals-go N/A unrated 0.0.0-20240116172146-2a6ca2d4e64d 17 Jan 2024
Vulnerability in crystals-go package: KyberSlash Timing Side-Channel Attack N/A high 0.0.0-20240116172146-2a6ca2d4e64d 17 Jan 2024

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/kudelskisecurity/crystals-go

Is github.com/kudelskisecurity/crystals-go safe to use?

Vulert records 2 vulnerabilities for github.com/kudelskisecurity/crystals-go in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/kudelskisecurity/crystals-go's Vulert package health score?

Vulert scores github.com/kudelskisecurity/crystals-go 62/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/kudelskisecurity/crystals-go affected?

Yes. v0.0.0-20240116172146-2a6ca2d4e64d, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/kudelskisecurity/crystals-go should I use?

v0.0.0-20240116172146-2a6ca2d4e64d 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/kudelskisecurity/crystals-go have?

2 vulnerabilities are recorded for github.com/kudelskisecurity/crystals-go in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/kudelskisecurity/crystals-go vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/kudelskisecurity/crystals-go in the last 12 months, and the oldest entry in this database dates to 17 Jan 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 github.com/kudelskisecurity/crystals-go 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/kudelskisecurity/crystals-go for upcoming vulnerabilities?

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