VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/destinygg/chat: vulnerability history, versions and safety

github.com/destinygg/chat is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 34 releases, first recorded in Dec 2022. 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 H1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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/destinygg/chat vulnerabilities

Vulert verdict on github.com/destinygg/chat v0.0.0-20220628124252-0981d5add8f3 i

Updated on 23 Oct 2026

Careful: v0.0.0-20220628124252-0981d5add8f3 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v0.0.0-20220628124252-0981d5add8f3 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 22 Dec 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Stars 89 i
  • Last release 51 months ago 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/destinygg/chat, 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-20220628124252-0981d5add8f3 28 Jun 2022 H1 — No Details →
v0.0.0-20201101200804-dd0bd0e17a1c 01 Nov 2020 H1 — No Details →
v0.0.0-20201101193607-85b67207e32b 01 Nov 2020 H1 — No Details →
v0.0.0-20201101192000-b4ca08938287 01 Nov 2020 H1 — No Details →
v0.0.0-20200824023639-2efc68d8fefe 24 Aug 2020 H1 — No Details →
v0.0.0-20200813062710-4f3bcabdf28c 13 Aug 2020 H1 — No Details →
v0.0.0-20200714174437-d6214082744c 14 Jul 2020 H1 — No Details →
v0.0.0-20181113084504-d17177ebb2af 13 Nov 2018 H1 — No Details →
v0.0.0-20150722161012-07626f9e16ef 22 Jul 2015 H1 — No Details →
v0.0.0-20150423182207-183163a86cab 23 Apr 2015 H1 — No Details →
v0.0.0-20141220220249-8466c6d3a75e 20 Dec 2014 H1 — No Details →
v0.0.0-20141216223102-836bf485c20b 16 Dec 2014 H1 — No Details →
v0.0.0-20141214131628-ccacc8f7ded2 14 Dec 2014 H1 — No Details →
v0.0.0-20131027194603-51d3afb23d6c 27 Oct 2013 H1 — No Details →
v0.0.0-20130910222616-8ba481f08491 10 Sep 2013 H1 — No Details →
v0.0.0-20130910072533-1b19652ba571 10 Sep 2013 H1 — No Details →
v0.0.0-20130831112541-ecd1bf01793b 31 Aug 2013 H1 — No Details →
v0.0.0-20130831101020-3936280ccaf8 31 Aug 2013 H1 — No Details →
v0.0.0-20130818130532-e664b0e06a29 18 Aug 2013 H1 — No Details →
v0.0.0-20130818120127-ea1291043a50 18 Aug 2013 H1 — No Details →
v0.0.0-20130811120052-9c72989b2cc4 11 Aug 2013 H1 — No Details →
v0.0.0-20130811003027-c38976fceb36 11 Aug 2013 H1 — No Details →
v0.0.0-20130810202250-d4710774ff81 10 Aug 2013 H1 — No Details →
v0.0.0-20130806182143-ed6dc71d389b 06 Aug 2013 H1 — No Details →
v0.0.0-20130721145926-0b920edb606a 21 Jul 2013 H1 — No Details →
v0.0.0-20130721074013-de721b12317f 21 Jul 2013 H1 — No Details →
v0.0.0-20130720215730-ba3a44d1b8ce 20 Jul 2013 H1 — No Details →
v0.0.0-20130720183043-74fa90d1bd0a 20 Jul 2013 H1 — No Details →
v0.0.0-20130714150128-6f43a2d1e273 14 Jul 2013 H1 — No Details →
v0.0.0-20130713201231-33a2af38c6e3 13 Jul 2013 H1 — No Details →
v0.0.0-20130709210801-b25f7a4d4693 09 Jul 2013 H1 — No Details →
v0.0.0-20130707062923-8dc1cb210958 07 Jul 2013 H1 — No Details →
v0.0.0-20130706150614-aa96df97f4de 06 Jul 2013 H1 — No Details →
v0.0.0-20130706143039-1835e83cf1f2 06 Jul 2013 H1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 github.com/destinygg/chat

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-36625: destiny.gg chat vulnerable to cross-site request forgery 8.8 high No fix published 22 Dec 2022

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/destinygg/chat

Is github.com/destinygg/chat safe to use?

Vulert records 1 vulnerabilities for github.com/destinygg/chat in Go: 0 critical, 1 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/destinygg/chat's Vulert package health score?

Vulert scores github.com/destinygg/chat 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/destinygg/chat affected?

Yes. v0.0.0-20220628124252-0981d5add8f3, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/destinygg/chat should I use?

v0.0.0-20220628124252-0981d5add8f3 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/destinygg/chat have?

1 vulnerability is recorded for github.com/destinygg/chat in the Go ecosystem: 0 critical, 1 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/destinygg/chat vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/destinygg/chat in the last 12 months, and the oldest entry in this database dates to 22 Dec 2022. 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/destinygg/chat 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/destinygg/chat for upcoming vulnerabilities?

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