VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/kro-run/kro: vulnerability history, versions and safety

github.com/kro-run/kro is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 70 releases, first recorded in Jun 2025. 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/kro-run/kro vulnerabilities

Vulert verdict on github.com/kro-run/kro v0.4.1 i

Updated on 23 Oct 2026

Action needed: v0.4.1 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 88/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

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.4.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 09 Jun 2025 i
  • Highest CVSS 4.1 i
  • With no published fix 0 i
  • Stars 3,078 i
  • Last release 14 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/kro-run/kro, 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.4.2-0.20250926180816-c1bc05c53842 26 Sep 2025 U1 Apache-2.0 Yes Details →
v0.4.2-0.20250914233008-65ebb02c76b5 14 Sep 2025 U1 Apache-2.0 Yes Details →
v0.4.2-0.20250829175419-ae56ce98feb9 29 Aug 2025 U1 Apache-2.0 Yes Details →
v0.4.2-0.20250825170729-6b6f9e492a19 25 Aug 2025 U1 Apache-2.0 Yes Details →
v0.4.1 22 Aug 2025 U1 Apache-2.0 Yes Details →
v0.4.1-0.20250731071608-ea6885a9e28d 31 Jul 2025 U1 Apache-2.0 Yes Details →
v0.4.0 30 Jul 2025 U1 Apache-2.0 Yes Details →
v0.3.1-0.20250606072739-9fc268b35c74 06 Jun 2025 U1 Apache-2.0 Yes Details →
v0.3.0 21 May 2025 U1 Apache-2.0 Yes Details →
v0.2.4-0.20250418171505-4f9b65d4dc18 18 Apr 2025 U1 Apache-2.0 Yes Details →
v0.2.3 16 Apr 2025 U1 Apache-2.0 Yes Details →
v0.2.2 13 Mar 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250216004344-ab0004e4bac7 16 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250216003310-1930df6275c4 16 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250214214426-565c29879475 14 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250214064934-4b063a87e44b 14 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250214064910-487773eab4d3 14 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250214011115-1a04e1143f3a 14 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250213181341-43a452347a87 13 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250213055504-bae038902495 13 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250213032747-00f2a640ab68 13 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250212222704-d205c345af22 12 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250212144225-fe885014289a 12 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250212143526-07d9d26518de 12 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250212064039-b09909e00a2b 12 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250212061615-8e08138604e6 12 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250211232522-198927fc374d 11 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250211232455-10e87173051c 11 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250211232332-741559134a19 11 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250211223612-9ee758552af6 11 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250208174730-7ea746cbd5df 08 Feb 2025 U1 Apache-2.0 Yes Details →
v0.2.2-0.20250208174730-7ea746cbd5df 08 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250208044256-3fed15089474 08 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250208032416-a37f91b2369d 08 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250207001339-1f200bd63c9f 07 Feb 2025 U1 Apache-2.0 Yes Details →
v0.2.1 07 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250207000225-4dea88e4adcd 07 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250205213112-2a8aaad13aaa 05 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250205202613-9c8683ebafc4 05 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250205202556-46d08ba97a50 05 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250205202539-64147a663847 05 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250205202513-a77a81269a63 05 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250205175620-3f9a39c0e828 05 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250205175120-5ffbe276f3f3 05 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250205174119-19b5de5adadc 05 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250204191518-b9f04190b2b0 04 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250204000626-87a9b1c46085 04 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250204000610-3a229cf69c35 04 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250203215523-3e53679c4972 03 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250203203646-cb4edb7a9733 03 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250203010507-a73651db3285 03 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250202220325-9a840f26a495 02 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250202213506-86cb8e49370b 02 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250202203757-f58212488074 02 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250201205802-45adaf5a0740 01 Feb 2025 U1 Apache-2.0 Yes Details →
v0.2.1-0.20250201205802-45adaf5a0740 01 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250201182643-cf49e5e2146f 01 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250201163536-dc78f7d8c433 01 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250201130105-9ae410f83059 01 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250201042708-28962000ac4a 01 Feb 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250131233705-e7c78b6bcc38 31 Jan 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250131195327-2f282e216f2d 31 Jan 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250131120029-fb53f0d7e0d0 31 Jan 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250131084311-be826972b580 31 Jan 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250131060136-966d4be574ec 31 Jan 2025 U1 Apache-2.0 Yes Details →
v0.2.0 30 Jan 2025 U1 Apache-2.0 Yes Details →
v0.2.0-rc.1 30 Jan 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250123212856-9d5dfa408f62 23 Jan 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250123210327-e7b80cbacdfa 23 Jan 2025 U1 Apache-2.0 Yes Details →
v0.0.0-20250123203719-bf4fc85adf57 23 Jan 2025 U1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 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/kro-run/kro

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-48710: kro Confused Deputy Vulnerability in Kube Resource Orchestrator 4.1 medium 0.2.1 04 Jun 2025
CVE-2025-48710: kro Package Confused Deputy Vulnerability N/A unrated 0.2.1 09 Jun 2025

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/kro-run/kro

Is github.com/kro-run/kro safe to use?

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

Vulert scores github.com/kro-run/kro 88/100, which reads as healthy. 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/kro-run/kro affected?

Yes. v0.4.1, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/kro-run/kro should I use?

v0.4.1 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/kro-run/kro have?

2 vulnerabilities are recorded for github.com/kro-run/kro 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/kro-run/kro vulnerabilities disclosed?

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

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