Karmada PULL Mode Cluster Privilege Escalation

Exploitation

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

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-56513: 0.49% estimated exploitation activity in the next 30 days; percentile 42.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.

Impact What kind of vulnerability is it? Who is impacted? The PULL mode clusters registered with the karmadactl register command have excessive privileges to access control plane resources. By abusing these permissions, an attacker able to authenticate as the karmada-agent to a karmada cluster would be able to obtain administrative privileges over the entire federation system including all registered member clusters. Patches Has the problem been patched? What versions should users upgrade to? Since Karmada v1.12.0, command karmadactl register restricts the access permissions of pull mode member clusters to control plane resources. This way, an attacker able to authenticate as the karmada-agent cannot control other member clusters in Karmada. Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? Restricts the access permissions of pull mode member clusters to control plane resources according to Karmada Component Permissions Docs. References Are…

Published by the source

3 Jan 2025, 16:12 UTC

Last modified by the source

12 Mar 2025, 07:49 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mg7w-c9x2-xh7r

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

# Patch Next advisory brief: CVE-2024-56513

Advisory: Karmada PULL Mode Cluster Privilege Escalation
IDs: CVE-2024-56513, GHSA-mg7w-c9x2-xh7r
Record: https://patchnext.com/advisories/cve-2024-56513 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/karmada-io/karmada 1.12.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/karmada-io/karmada: affected < 1.12.0; fixed in 1.12.0

## Suggested inspection (read-only)
- Go github.com/karmada-io/karmada: 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/karmada-io/karmada.
- 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-mg7w-c9x2-xh7r (GitHub-reviewed advisory GHSA-mg7w-c9x2-xh7r lists affected ranges: Go github.com/karmada-io/karmada >=0 <1.12.0)

Commands are suggestions: review each one before running it.