VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

ktbs.dev/teler: vulnerability history, versions and safety

ktbs.dev/teler is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 44 releases, from May 2021 to Aug 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 M1 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 ktbs.dev/teler vulnerabilities

Vulert verdict on ktbs.dev/teler v1.2.2 i

Updated on 23 Oct 2026

Action needed: v1.2.2 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 80/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Not enough data
  • Community Not enough data

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 v1.2.2 — affected i
  • Vulnerabilities on record 2 over 3 years · 0 in the last year i
  • Latest disclosure 21 Aug 2024 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Last release 66 months ago i
  • Licence Apache-2.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 ktbs.dev/teler, 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
v1.2.3-0.20210702091141-73cab9f247ab 02 Jul 2021 M1 U1 Apache-2.0 Yes Details →
v1.2.3-0.20210618064940-6b39f9f7f1b2 18 Jun 2021 M1 U1 Apache-2.0 Yes Details →
v1.2.3-0.20210608065559-e3f64a14031e 08 Jun 2021 M1 U1 Apache-2.0 Yes Details →
v1.2.3-0.20210504060725-79d5f2de8586 04 May 2021 M1 U1 Apache-2.0 Yes Details →
v1.2.3-0.20210408061354-31938d84cef2 08 Apr 2021 M1 U1 Apache-2.0 Yes Details →
v1.2.2 01 Apr 2021 M1 U1 Apache-2.0 Yes Details →
v1.2.1 24 Mar 2021 M1 U1 Apache-2.0 Yes Details →
v1.2.0 24 Mar 2021 M1 U1 Apache-2.0 Yes Details →
v1.1.1 16 Mar 2021 M1 U1 Apache-2.0 Yes Details →
v1.1.0 25 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v1.0.3 23 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v1.0.3-0.20210220154415-93a916093ecd 20 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v1.0.2 16 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v1.0.2-dev 09 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v1.0.2-0.20210209073338-818ee73abd24 09 Feb 2021 M1 U1 Apache-2.0 Yes Details →
v1.0.1 26 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v1.0.0 25 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v1.0.0-rc 25 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.5-dev 25 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.4 14 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.4-dev 10 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.3 09 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.2 09 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1 04 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-dev5.1 03 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-rc2.1 01 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-rc2 01 Nov 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-dev5 31 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-dev.4.3 30 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-rc1.3 29 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-beta4 28 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-beta3.2 25 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-dev.4.2 25 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-beta3.1 25 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-dev.4.1 24 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-beta3 20 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-dev.4 20 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-dev.3 06 Oct 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-beta2 02 Sep 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-dev1 01 Sep 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-dev2 01 Sep 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-rc1.2 25 Aug 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-beta1.2 24 Aug 2020 M1 U1 Apache-2.0 Yes Details →
v0.0.1-beta1 24 Aug 2020 M1 U1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2024 1

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 ktbs.dev/teler

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-26213: Denial-of-Service within Docker container in ktbs.dev/teler/pkg/errors 5.9 medium 0.0.1 24 May 2021
CVE-2020-26213: Denial-of-Service within Docker container in ktbs.dev/teler N/A unrated 0.0.1 21 Aug 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 ktbs.dev/teler

Is ktbs.dev/teler safe to use?

Vulert records 2 vulnerabilities for ktbs.dev/teler in Go: 0 critical, 0 high, 1 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 ktbs.dev/teler's Vulert package health score?

Vulert scores ktbs.dev/teler 80/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 ktbs.dev/teler affected?

Yes. v1.2.2, 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 ktbs.dev/teler should I use?

v1.2.2 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 ktbs.dev/teler have?

2 vulnerabilities are recorded for ktbs.dev/teler in the Go ecosystem: 0 critical, 0 high, 1 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 ktbs.dev/teler vulnerabilities disclosed?

0 vulnerabilities were recorded for ktbs.dev/teler in the last 12 months, and the oldest entry in this database dates to 24 May 2021. 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 ktbs.dev/teler 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 ktbs.dev/teler for upcoming vulnerabilities?

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