VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/wolfi-dev/wolfictl: vulnerability history, versions and safety

github.com/wolfi-dev/wolfictl is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from May 2024 to 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
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 github.com/wolfi-dev/wolfictl vulnerabilities

Vulert verdict on github.com/wolfi-dev/wolfictl v0.39.29 i

Updated on 23 Oct 2026

Action needed: v0.39.29 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 82/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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.39.29 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 04 Jun 2024 i
  • Highest CVSS 4.4 i
  • With no published fix 0 i
  • Stars 76 i
  • Last release this month 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/wolfi-dev/wolfictl, 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.39.29 17 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.29-0.20261017143258-e41d45183bc4 17 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.29-0.20261014192052-48d76849dd66 14 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.29-0.20261014093516-98b7b4f653fa 14 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.28 21 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.28-0.20260921145640-b2448bc66a3c 21 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.27 18 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.26 10 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.26-0.20260910074206-0c496997a8c8 10 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.25 13 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.24 04 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.24-0.20260804161016-f304a18016b7 04 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.23 04 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.22 07 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.21 04 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.20 22 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.20-0.20260622175051-ac222a874b82 22 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.19 18 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.18 03 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.17 19 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.16 15 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.15 05 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.14 28 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.13 23 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.12 23 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.11 16 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.10 16 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.9 09 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.8 01 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.7 24 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.6 19 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.5 09 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.4 02 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.3 26 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.2 20 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.1 11 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.39.0 03 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.31 02 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.30 29 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.29 23 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.28 17 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.27 15 Dec 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.26 10 Dec 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.25 04 Dec 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.24 02 Dec 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.23 26 Nov 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.22 20 Nov 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.21 03 Nov 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.20 29 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.20-0.20251029122212-2bcb296d9f2c 29 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.19 14 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.19-0.20251014162015-8b125ac708c6 14 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.18 23 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.17 15 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.17-0.20250915175102-246e2d8bcb63 15 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.17-0.20250915164938-78e61ce1dd55 15 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.16 12 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.15 05 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.15-0.20250905215338-07039471a94c 05 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.14 28 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.14-0.20250828200450-c31744d3dfa0 28 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.13 26 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.12 20 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.12-0.20250820060418-3c7a07f30897 20 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.11 15 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.11-0.20250815151621-7a4565af27be 15 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.11-0.20250812011228-811dddaaa1f5 12 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.10 09 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.9 01 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.9-0.20250801182318-f6d10cfe36a6 01 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.8 01 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.7 30 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.6 30 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.5 22 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.4 20 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.4-0.20250720164824-422f6b5ef711 20 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.3 17 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.2 14 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.1 11 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.38.0 08 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.9 03 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.8 24 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.7 20 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.6 19 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.5 12 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.5-0.20250610071809-5922ede4f26e 10 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.5-0.20250609172721-5d6709b83043 09 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.4 04 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.4-0.20250604172831-e725fb61082f 04 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.3 28 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.3-0.20250528172030-8b4995cb47a2 28 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.3-0.20250528083029-81dbc62ff10f 28 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.2 23 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.1 19 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20250519125745-7a0865e66ff0 19 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.37.0 17 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.36.9 16 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.36.8 13 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.36.7 09 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.36.7-0.20250506173722-bdae3a1fed7f 06 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.36.6 06 May 2025 M1 U1 — Yes Details →
v0.36.5 05 May 2025 M1 U1 — Yes Details →
v0.36.4 02 May 2025 M1 U1 — Yes Details →
v0.36.3 24 Apr 2025 M1 U1 — Yes Details →
v0.36.2 21 Apr 2025 M1 U1 — Yes Details →
v0.36.1 18 Apr 2025 M1 U1 — Yes Details →
v0.36.1-0.20250418191503-67e9cf6d25c2 18 Apr 2025 M1 U1 — Yes Details →
v0.36.0 14 Apr 2025 M1 U1 — Yes Details →
v0.35.1 11 Apr 2025 M1 U1 — Yes Details →
v0.35.0 11 Apr 2025 M1 U1 — Yes Details →
v0.34.1 03 Apr 2025 M1 U1 — Yes Details →
v0.34.0 03 Apr 2025 M1 U1 — Yes Details →
v0.33.0 28 Mar 2025 M1 U1 — Yes Details →
v0.32.0 27 Mar 2025 M1 U1 — Yes Details →
v0.31.2 21 Mar 2025 M1 U1 — Yes Details →
v0.31.2-0.20250319125401-30dc71434963 19 Mar 2025 M1 U1 — Yes Details →
v0.31.1 13 Mar 2025 M1 U1 — Yes Details →
v0.30.1-0.20250307180353-f245f6ba6da8 07 Mar 2025 M1 U1 — Yes Details →
v0.31.0 07 Mar 2025 M1 U1 — Yes Details →
v0.30.1-0.20250306195004-98445e4d603a 06 Mar 2025 M1 U1 — Yes Details →

The newest 120 of 594 versions Vulert tracks. 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/wolfi-dev/wolfictl

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
GitHub Token Leakage in wolfictl 4.4 medium 0.16.10 15 May 2024
CVE-2024-35183: GitHub Token Leakage in wolfictl N/A unrated 0.16.10 04 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/wolfi-dev/wolfictl

Is github.com/wolfi-dev/wolfictl safe to use?

Vulert records 2 vulnerabilities for github.com/wolfi-dev/wolfictl 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 github.com/wolfi-dev/wolfictl's Vulert package health score?

Vulert scores github.com/wolfi-dev/wolfictl 82/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/wolfi-dev/wolfictl affected?

Yes. v0.39.29, 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.

How many vulnerabilities does github.com/wolfi-dev/wolfictl have?

2 vulnerabilities are recorded for github.com/wolfi-dev/wolfictl 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 github.com/wolfi-dev/wolfictl vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/wolfi-dev/wolfictl in the last 12 months, and the oldest entry in this database dates to 15 May 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/wolfi-dev/wolfictl 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/wolfi-dev/wolfictl for upcoming vulnerabilities?

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