CVE-2024-49375 is a critical-severity (CVSS 9) Code Injection vulnerability in rasa-pro. A fix is available for rasa-pro — see the affected versions and patch details below.
Rasa Allows Remote Code Execution via Remote Model Loading
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-49375.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
rasa-pro🐍rasa-pro🐍rasa-pro🐍rasaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Vulnerability
A vulnerability has been identified in Rasa Pro and Rasa Open Source 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:
- The HTTP API must be enabled on the Rasa instance eg with
--enable-api. This is not the default configuration. - For unauthenticated RCE to be exploitable, the user must not have configured any authentication or other security controls recommended in our documentation.
- For authenticated RCE, the attacker must posses a valid authentication token or JWT to interact with the Rasa API.
Fix
We encourage you to upgrade to a version of Rasa that includes a fix. These are:
- Rasa Pro 3.8.18, 3.9.16, 3.10.12
- Rasa Open Source 3.6.21
Once you have upgraded your Rasa Pro or Open Source installation, you will need to retrain your model using the fixed version of Rasa Pro or Open Source. If you have a custom component that inherits from one of the components listed below and modified the persist or load method, make sure to update your code. Please contact us in case you encounter any problems.
Affected components:
CountVectorFeaturizerLexicalSyntacticFeaturizerLogisticRegressionClassifierSklearnIntentClassifierDIETClassifierCRFEntityExtractorTrackerFeaturizerTEDPolicyUnexpectedIntentTEDPolicy
If you are unable to upgrade immediately, please follow our mitigation advice below.
Mitigation Advice
-
The unauthenticated RCE can be mitigated by ensuring that you enable authentication for the Rasa HTTP API if this is enabled. This means that in addition to passing
--enable-apito Rasa, you should also pass an authentication configuration as described in our documentation here. -
The authenticated RCE can be mitigated by:
- Ensuring that you only load models from trusted sources such as your own CI pipelines. You can check file hashes for model archives to confirm that a model has not been tampered with between training and use.
- Confirming that you have sufficient access controls and utilize the principle of least privilege to control who in your organization has the ability to interact with the Rasa API even with authentication enabled.
Future Releases
As an additional security step, a future release of Rasa Pro will remove the ability to enable the API without any authentication method enabled.
Credit
Rasa would like to thank Julian Scheid from Deutsche Telekom Security GmbH for responsible disclosure of this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | rasa-pro | ≥ 3.10.0&&< 3.10.12 | 3.10.12pip install --upgrade 'rasa-pro==3.10.12' |
| 🐍PyPI | rasa-pro | ≥ 3.9.0&&< 3.9.16 | 3.9.16pip install --upgrade 'rasa-pro==3.9.16' |
| 🐍PyPI | rasa-pro | all versions | 3.8.18pip install --upgrade 'rasa-pro==3.8.18' |
| 🐍PyPI | rasa | all versions | 3.6.21pip install --upgrade 'rasa==3.6.21' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rasa-pro, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rasa-pro to 3.10.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-49375 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2024-49375 in your dependencies?
Find it across PyPI, including transitive dependencies.