Vulnerability Database · Go · Package report

github.com/temporalio/temporal: vulnerability history, versions and safety

github.com/temporalio/temporal is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Apr 2024. 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.

Vulert verdict on github.com/temporalio/temporal v0.26.0 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release v0.26.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 04 Apr 2024 i
  • Highest CVSS 4.4 i
  • With no published fix 0 i
  • Stars 23,776 i
  • OpenSSF scorecard 5/10 i
  • Last release 75 months ago i
  • Licence MIT 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/temporalio/temporal, 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.26.1-0.20200708195911-16f23cb09095 08 Jul 2020 none MIT — Details →
v0.0.0-20200628045145-f73889c37f87 28 Jun 2020 none MIT — Details →
v0.26.0 28 Jun 2020 none MIT — Details →
v0.25.0 25 Jun 2020 none MIT — Details →
v0.23.2-0.20200618003721-b1d950280a94 18 Jun 2020 none MIT — Details →
v0.23.1 20 May 2020 none MIT — Details →
v0.21.2-0.20200516025043-031bdcfdf201 16 May 2020 none MIT — Details →
v0.23.0 16 May 2020 none MIT — Details →
v0.21.1 06 Apr 2020 none MIT — Details →
v0.0.0-20200404234217-34a5163e5d30 04 Apr 2020 none MIT — Details →
v0.21.0 04 Apr 2020 none MIT — Details →
v0.20.1-0.20200328193546-8d4b65a0307c 28 Mar 2020 none MIT — Details →
v0.20.1-0.20200327234627-205d63e523e1 27 Mar 2020 none MIT — Details →
v0.0.0-20200322194326-aeb9a99844ea 22 Mar 2020 none MIT — Details →
v0.20.0 22 Mar 2020 none MIT — Details →
v0.10.1-0.20200223092924-968e559c1534 23 Feb 2020 none MIT — Details →
v0.10.1-0.20200219054951-65a0e78184fd 19 Feb 2020 none MIT — Details →
v0.10.1-0.20200209061202-6423fe1b6714 09 Feb 2020 none MIT — Details →
v0.0.0-20200205012045-b8b14483744b 05 Feb 2020 none MIT — Details →
v0.10.0 05 Feb 2020 none MIT — Details →
v0.8.2-0.20191220000720-c19422bc88d1 20 Dec 2019 none MIT — Details →
v0.8.2-0.20191212183749-83890f7fcf57 12 Dec 2019 none MIT — Details →
v0.8.2-0.20191026172607-8e92b608330d 26 Oct 2019 none MIT — Details →
v0.8.6 27 Aug 2019 none MIT — Details →
v0.8.5 27 Aug 2019 none MIT — Details →
v0.8.4 26 Aug 2019 none MIT — Details →
v0.8.3 14 Aug 2019 none MIT — Details →
v0.8.2 13 Aug 2019 none MIT — Details →
v0.8.1 12 Aug 2019 none MIT — Details →
v0.8.0 12 Aug 2019 none MIT — Details →
v0.7.3 08 Aug 2019 none MIT — Details →
v0.7.2 08 Aug 2019 none MIT — Details →
v0.7.1 06 Aug 2019 none MIT — Details →
v0.7.0 30 Jul 2019 none MIT — Details →
v0.6.1 26 Jul 2019 none MIT — Details →
v0.6.0 24 Jul 2019 none MIT — Details →
v0.5.9 17 Jun 2019 none MIT — Details →
v0.5.8 14 May 2019 none MIT — Details →
v0.5.7 08 May 2019 none MIT — Details →
v0.5.5 12 Mar 2019 none MIT — Details →
v0.5.4 08 Mar 2019 none MIT — Details →
v0.5.3 19 Feb 2019 none MIT — Details →
v0.5.2 12 Feb 2019 none MIT — Details →
v0.5.1 18 Jan 2019 none MIT — Details →
v0.5.0 07 Jan 2019 none MIT — Details →
v0.4.0 19 Oct 2018 none MIT — Details →
v0.3.15 26 Jul 2018 none MIT — Details →
v0.3.14 24 Jul 2018 none MIT — Details →
v0.3.13 09 Jun 2018 none MIT — Details →
v0.3.12 26 May 2018 none MIT — Details →
v0.3.11 16 Apr 2018 none MIT — Details →
v0.3.10 10 Apr 2018 none MIT — Details →
v0.3.9 14 Mar 2018 none MIT — Details →
v0.3.8 13 Mar 2018 none MIT — Details →
v0.3.7 12 Mar 2018 none MIT — Details →
v0.3.6 30 Jan 2018 none MIT — Details →
v0.3.5 12 Jan 2018 none MIT — Details →
v0.3.4 12 Dec 2017 none MIT — Details →
v0.3.3 05 Dec 2017 none MIT — Details →
v0.3.2 29 Sep 2017 none MIT — Details →
v0.3.1 15 Aug 2017 none MIT — Details →
v0.3.0 07 Aug 2017 none MIT — Details →
v0.2.0 30 Jun 2017 none MIT — Details →
v0.1.1-beta 07 Jun 2017 none MIT — Details →
v0.1.0-beta 06 Jun 2017 none MIT — Details →

All 65 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 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/temporalio/temporal

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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/temporalio/temporal

Is github.com/temporalio/temporal safe to use?

Vulert records 1 vulnerabilities for github.com/temporalio/temporal in Go: 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 github.com/temporalio/temporal's Vulert package health score?

Vulert scores github.com/temporalio/temporal 78/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 github.com/temporalio/temporal affected?

No. v0.26.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.

Which version of github.com/temporalio/temporal should I use?

v0.26.0 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/temporalio/temporal have?

1 vulnerability is recorded for github.com/temporalio/temporal in the Go 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 github.com/temporalio/temporal vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/temporalio/temporal in the last 12 months, and the oldest entry in this database dates to 04 Apr 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/temporalio/temporal 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/temporalio/temporal for upcoming vulnerabilities?

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