VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/gvalkov/tailon: vulnerability history, versions and safety

github.com/gvalkov/tailon is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 6 releases, first recorded in Jun 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 U1
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/gvalkov/tailon vulnerabilities

Vulert verdict on github.com/gvalkov/tailon v1.1.0 i

Updated on 23 Oct 2026

Careful: v1.1.0 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 54/100
  • Security Some issues to review
  • 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 v1.1.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 10 Jun 2024 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 358 i
  • OpenSSF scorecard 2/10 i
  • Last release 92 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 github.com/gvalkov/tailon, 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.1.1-0.20241030003403-51b2b779ac1a 30 Oct 2024 U1 Apache-2.0 No Details →
v1.1.1-0.20220325162134-7ea1d07b7b76 25 Mar 2022 U1 Apache-2.0 No Details →
v1.1.1-0.20191218162900-9c463c3910e9 18 Dec 2019 U1 Apache-2.0 No Details →
v1.1.0 07 Feb 2019 U1 Apache-2.0 No Details →
v1.0.0 18 Jul 2018 U1 Apache-2.0 No Details →
v0.1.0 15 Jul 2018 U1 Apache-2.0 No Details →

All 6 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/gvalkov/tailon

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-2056: Artica Proxy Loopback Services Remotely Accessible Unauthenticated in github.com/gvalkov/tailon N/A unrated No fix published 10 Jun 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/gvalkov/tailon

Is github.com/gvalkov/tailon safe to use?

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

What is github.com/gvalkov/tailon's Vulert package health score?

Vulert scores github.com/gvalkov/tailon 54/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/gvalkov/tailon affected?

Yes. v1.1.0, 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/gvalkov/tailon should I use?

v1.1.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/gvalkov/tailon have?

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

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

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