Is github.com/stacklok/minder 0.3 vulnerable?
Go · 3 releases from 0.3.0 to 0.3.2 · latest github.com/stacklok/minder is 0.4.0 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. github.com/stacklok/minder 0.3.2, the last 0.3 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2024-27093, CVE-2024-27093. At least one has no fixed release yet.
Is your project on an affected github.com/stacklok/minder?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/stacklok/minder 0.3.2
Minder trusts client-provided mapping from repo name to upstream ID in github.com/stacklok/minder
- Affected
- All versions
- Fixed in
- No fix released
Minder trusts client-provided mapping from repo name to upstream ID
- Affected
- <0.20240226.1425
- Fixed in
- 0.20240226.1425
Every github.com/stacklok/minder 0.3.x release
Affected: 0.3.0 to 0.3.2. Latest github.com/stacklok/minder: 0.4.0.
| Version | Known advisories |
|---|---|
| github.com/stacklok/minder 0.3.2 | CVE-2024-27093, CVE-2024-27093 |
| github.com/stacklok/minder 0.3.1 | CVE-2024-27093, CVE-2024-27093 |
| github.com/stacklok/minder 0.3.0 | CVE-2024-27093, CVE-2024-27093 |
Which of your client projects are still on github.com/stacklok/minder 0.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/stacklok/minder version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/stacklok/minder versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.