CVE-2021-41127 json
Maliciously Crafted Model Archive Can Lead To Arbitrary File Write in rasa
published 2021-10-21 5 y ago modified 2026-07-08 4 mo ago also GHSA-4365-fhm5-qcrx , PYSEC-2021-381 , EUVD-2021-0221
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
Rasa is an open source machine learning framework to automate text-and voice-based conversations. In affected versions a vulnerability exists in the functionality that loads a trained model `tar.gz` file which allows a malicious actor to craft a `model.tar.gz` file which can overwrite or replace bot files in the bot directory. The vulnerability is fixed in Rasa 2.8.10. For users unable to update ensure that users do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.
Patch / fix
Exploit prediction
0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H |
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:N/I:P/A:P |
| GitHub | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | rasa | <2.8.10 |
2.8.10 |
Affected products
- RasaHQ rasa
Classification
References
-
github.com
/RasaHQ/rasa/commit/1b6b502f52d73b4f8cd1959ce724b8ad0eb33989
web, patch, third-party-advisory
-
github.com
/RasaHQ/rasa/security/advisories/GHSA-4365-fhm5-qcrx
web, third-party-advisory, advisory
-
github.com
/RasaHQ/rasa
package
-
github.com
/pypa/advisory-database/tree/main/vulns/rasa/PYSEC-2021-381.yaml
web
Sources
- CVE List CVE-2021-41127
- GitHub Advisory GHSA-4365-fhm5-qcrx
- NVD CVE-2021-41127
- OSV PYSEC-2021-381
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.