# CVE-2024-12629: Prototype Pollution in Progress® Telerik® KendoReact

> Prototype pollution in KendoReact allows attackers to inject code or cause denial of service via global prototype chain manipulation.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-h2q9-88fw-gpmp

## What is CVE-2024-12629?

CVE-2024-12629 is a medium-severity code injection vulnerability in Progress Software Telerik KendoReact, published on 12 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Progress® Telerik® KendoReact versions v3.5.0 through v9.4.0, an attacker can introduce or modify properties within the global prototype chain which can result in denial of service or command injection.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2024-12629?

It affects 1 product.


Products: Progress Kendoreact.

## How do I fix CVE-2024-12629?

No fix has been published for CVE-2024-12629 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-12629 being exploited?

There is no known exploitation of CVE-2024-12629 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12629 and fix it if it is affected.

What it is: CVE-2024-12629 is a medium-severity code injection vulnerability in Progress Software Telerik KendoReact, published on 12 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12629 in the wild and no public exploit code.

Affected product: Progress Software Telerik KendoReact. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-12629/ (Markdown: https://insights.sbomify.com/CVE-2024-12629/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-12629
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-12629
- OSV: https://osv.dev/vulnerability/CVE-2024-12629

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-12629/
Summaries are generated and may contain mistakes; the official description above is the record.