# Rasa Allows Remote Code Execution via Remote Model Loading

Advisory record · `GHSA-cpv4-ggrr-7j9v`

- **Identifiers:** `GHSA-cpv4-ggrr-7j9v` · `CVE-2024-49375` · `PYSEC-2026-513` · `PYSEC-2026-514`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md) · [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 29 Jun 2026
- **Updated:** 1 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `rasa` (PyPI): affected `<3.6.21`; fixed in `3.6.21`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Rasa versions before 3.6.21 are affected, and the fix is 3.6.21. The source also lists fixed Rasa Pro versions 3.8.18, 3.9.16, and 3.10.12. An attacker who can get a maliciously crafted model loaded into a Rasa instance with the HTTP API enabled can achieve remote code execution, and unauthenticated exploitation requires that no authentication was configured. Upgrade to a fixed version and retrain the model afterward.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0094, the 61st percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 29 Jun 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-cpv4-ggrr-7j9v](https://github.com/advisories/GHSA-cpv4-ggrr-7j9v)
- [OSV: GHSA-cpv4-ggrr-7j9v](https://osv.dev/vulnerability/GHSA-cpv4-ggrr-7j9v)
- <https://github.com/RasaHQ/rasa-pro-security-advisories/security/advisories/GHSA-cpv4-ggrr-7j9v>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-49375>
- <https://github.com/RasaHQ/rasa/commit/2bb1d779d4f4acaf70b6dfa35dd1899dccbb1ae6>
- <https://github.com/rasahq/rasa>
- <https://pypi.org/project/rasa>
- <https://github.com/advisories/GHSA-cpv4-ggrr-7j9v>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cpv4-ggrr-7j9v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cpv4-ggrr-7j9v/>. Everything for agents: <https://agentprime.io/llms.txt>.