How severe is CVE-2024-56513?

No CVSS score has been assigned to CVE-2024-56513 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-56513?

CVE-2024-56513 affects the following packages: github.com/karmada-io/karmada (Go). Ecosystems affected: Go.

How do I fix CVE-2024-56513?

Update github.com/karmada-io/karmada to 1.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-56513 is resolved across your whole dependency graph.

How do I detect CVE-2024-56513 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/karmada-io/karmada, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-56513 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2024-56513 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-56513 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-56513?

CVE-2024-56513 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-56513?

CVE-2024-56513 is classified as CWE-266 (CWE-266). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-56513 published, and has it been updated?

CVE-2024-56513 was published on January 3, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2024-56513 — karmada

Fix: karmada-io/karmada@2c82055

CVE-2024-56513 is a CWE-266 vulnerability in github.com/karmada-io/karmada. A fix is available for github.com/karmada-io/karmada — see the affected versions and patch details below.

Karmada PULL Mode Cluster Privilege Escalation

Also known asGHSA-mg7w-c9x2-xh7rGO-2025-3364

Published

Jan 3, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-56513.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/karmada-io/karmada

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 there any links users can visit to find out more?

Enhancements made from the Karmada community: https://github.com/karmada-io/karmada/pull/5793
Karmada Component Permissions: https://karmada.io/docs/administrator/security/component-permission

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/karmada-io/karmada`	all versions	1.12.0`go get github.com/karmada-io/karmada@v1.12.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/karmada-io/karmada, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/karmada-io/karmada to 1.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-56513 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ The [PULL](https://karmada.io/docs/next/userguide/clustermanager/cluster-registration#pull-mode) 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

O3 Security · Impact-Aware SCA

Is CVE-2024-56513 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works