Minder trusts client-provided mapping from repo name to upstream ID

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L

EPSS

• CVE-2024-27093: 0.55% estimated exploitation activity in the next 30 days; percentile 46.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary When using a modified client or the grpc interface directly, the RegisterRepository call accepts both the repository owner / repo and the repoid. Furthermore, these two are not checked for matching before registering webhooks and data in the database. Details It is possible for an attacker to register a repository with a invalid or differing upstream ID, which causes Minder to report the repository as registered, but not remediate any future changes which conflict with policy (because the webhooks for the repo do not match any known repository in the database). When attempting to register a repo with a different repo ID, the registered provider must have admin on the named repo, or a 404 error will result. Similarly, if the stored provider token does not have repo access, then the remediations will not apply successfully. Lastly, it appears that reconciliation actions do not execute against repos with this type of mismatch. PoC With an RPC like the following text proto: I was…

Published by the source

26 Feb 2024, 22:15 UTC

Last modified by the source

17 Mar 2026, 05:05 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q6h8-4j2v-pjg4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-27093

Advisory: Minder trusts client-provided mapping from repo name to upstream ID
IDs: CVE-2024-27093, GHSA-q6h8-4j2v-pjg4
Record: https://patchnext.com/advisories/cve-2024-27093 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/stacklok/minder 0.20240226.1425. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/stacklok/minder: affected < 0.20240226.1425; fixed in 0.20240226.1425

## Suggested inspection (read-only)
- Go github.com/stacklok/minder: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/stacklok/minder.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q6h8-4j2v-pjg4 (GitHub-reviewed advisory GHSA-q6h8-4j2v-pjg4 lists affected ranges: Go github.com/stacklok/minder >=0 <0.20240226.1425)

Commands are suggestions: review each one before running it.