# CVE-2024-49375: Remote Code Execution via Remote Model Loading in Rasa

> Attackers can achieve remote code execution by loading malicious models if the HTTP API is enabled without proper authentication.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2025
- **Updated:** 15 Jan 2025
- **Also known as:** GHSA-cpv4-ggrr-7j9v, PYSEC-2026-513, PYSEC-2026-514

## What is CVE-2024-49375?

CVE-2024-49375 is a critical code injection vulnerability in RasaHQ rasa-pro-security-advisories, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Open source machine learning framework. A vulnerability has been identified in Rasa that enables an attacker who has the ability to load a maliciously crafted model remotely into a Rasa instance to achieve Remote Code Execution. The prerequisites for this are: 1. The HTTP API must be enabled on the Rasa instance eg with `--enable-api`. This is not the default configuration. 2. For unauthenticated RCE to be exploitable, the user must not have configured any authentication or other security controls recommended in our documentation. 3. For authenticated RCE, the attacker must posses a valid authentication token or JWT to interact with the Rasa API. This issue has been addressed in rasa version 3.6.21 and all users are advised to upgrade. Users unable to upgrade should ensure that they require authentication and that only trusted users are given access.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-502 (Deserialization of Untrusted Data)

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

10 open source packages ship an affected version, including rasa-pro and rasa.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rasa-pro` | PyPI | All versions | 3.8.18 |
| `rasa-pro` | PyPI | All versions | 3.8.18 |
| `rasa-pro` | PyPI | All versions | 3.8.18 |
| `rasa-pro` | PyPI | From 3.10.0 | 3.10.12 |
| `rasa-pro` | PyPI | From 3.10.0 | 3.10.12 |
| `rasa-pro` | PyPI | From 3.9.0 | 3.9.16 |
| `rasa-pro` | PyPI | From 3.9.0 | 3.9.16 |
| `rasa` | PyPI | All versions | 3.6.21 |
| `rasa` | PyPI | All versions | 3.6.21 |
| `rasa` | PyPI | All versions | 3.6.21 |

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

Upgrade rasa-pro to a fixed version for your release line: 3.8.18, 3.10.12 or 3.9.16.

## Is CVE-2024-49375 being exploited?

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

Public exploit code:

- CVE-2024-49375、CVE-2021-42556、CVE-2021-41127 (github_poc): https://github.com/lierbushiwo/Rasa-cve-exp

## Fix prompt for AI coding agents

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

What it is: CVE-2024-49375 is a critical code injection vulnerability in RasaHQ rasa-pro-security-advisories, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-49375 in the wild and no public exploit code.

Affected packages and fixed versions:
- rasa-pro (PyPI): affected all versions; fixed in 3.8.18
- rasa-pro (PyPI): affected all versions; fixed in 3.8.18
- rasa-pro (PyPI): affected all versions; fixed in 3.8.18
- rasa-pro (PyPI): affected from 3.10.0; fixed in 3.10.12
- rasa-pro (PyPI): affected from 3.10.0; fixed in 3.10.12
- rasa-pro (PyPI): affected from 3.9.0; fixed in 3.9.16
- rasa-pro (PyPI): affected from 3.9.0; fixed in 3.9.16
- rasa (PyPI): affected all versions; fixed in 3.6.21
- rasa (PyPI): affected all versions; fixed in 3.6.21
- rasa (PyPI): affected all versions; fixed in 3.6.21

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-49375/ (Markdown: https://insights.sbomify.com/CVE-2024-49375/index.md)
```

## Sources

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

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