PYSEC-2026-513

Vulnerability from pysec - Published: 2026-06-29 11:50 - Updated: 2026-07-01 20:23
VLAI
Details

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:

  • CountVectorFeaturizer
  • LexicalSyntacticFeaturizer
  • LogisticRegressionClassifier
  • SklearnIntentClassifier
  • DIETClassifier
  • CRFEntityExtractor
  • TrackerFeaturizer
  • TEDPolicy
  • UnexpectedIntentTEDPolicy

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-api to 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.

Impacted products
Name purl
rasa pkg:pypi/rasa

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "rasa",
        "purl": "pkg:pypi/rasa"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.6.21"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.0.1",
        "0.0.2",
        "0.0.3",
        "0.0.4",
        "0.0.5",
        "0.1.0",
        "0.1.1",
        "0.14.0a5",
        "0.14.0a6",
        "0.14.0a7",
        "0.14.0a8",
        "0.14.0a9",
        "0.15.0a6",
        "0.2.0a2",
        "0.2.0a3",
        "1.0.0",
        "1.0.0a1",
        "1.0.0a2",
        "1.0.0a3",
        "1.0.0a4",
        "1.0.0a5",
        "1.0.0rc1",
        "1.0.0rc10",
        "1.0.0rc11",
        "1.0.0rc12",
        "1.0.0rc2",
        "1.0.0rc3",
        "1.0.0rc4",
        "1.0.0rc5",
        "1.0.0rc6",
        "1.0.0rc7",
        "1.0.0rc8",
        "1.0.0rc9",
        "1.0.1",
        "1.0.2",
        "1.0.3",
        "1.0.4",
        "1.0.5",
        "1.0.6",
        "1.0.7",
        "1.0.8",
        "1.0.9",
        "1.1.0",
        "1.1.1",
        "1.1.2",
        "1.1.3",
        "1.1.4",
        "1.1.5",
        "1.1.6",
        "1.1.7",
        "1.1.8",
        "1.10.0",
        "1.10.0a1",
        "1.10.0a2",
        "1.10.1",
        "1.10.10",
        "1.10.11",
        "1.10.12",
        "1.10.13",
        "1.10.14",
        "1.10.15",
        "1.10.16",
        "1.10.17",
        "1.10.18",
        "1.10.19",
        "1.10.2",
        "1.10.20",
        "1.10.21",
        "1.10.22",
        "1.10.23",
        "1.10.24",
        "1.10.25",
        "1.10.26",
        "1.10.3",
        "1.10.4",
        "1.10.5",
        "1.10.6",
        "1.10.7",
        "1.10.8",
        "1.10.9",
        "1.2.0",
        "1.2.0a2",
        "1.2.0a3",
        "1.2.0a4",
        "1.2.0a5",
        "1.2.0a6",
        "1.2.0a7",
        "1.2.1",
        "1.2.10",
        "1.2.11",
        "1.2.12",
        "1.2.2",
        "1.2.3",
        "1.2.4",
        "1.2.5",
        "1.2.6",
        "1.2.7",
        "1.2.8",
        "1.2.9",
        "1.3.0",
        "1.3.0a1",
        "1.3.0a2",
        "1.3.1",
        "1.3.10",
        "1.3.1a1",
        "1.3.1a10",
        "1.3.1a11",
        "1.3.1a12",
        "1.3.1a14",
        "1.3.1a3",
        "1.3.1a4",
        "1.3.1a5",
        "1.3.1a8",
        "1.3.2",
        "1.3.3",
        "1.3.4",
        "1.3.6",
        "1.3.7",
        "1.3.8",
        "1.3.9",
        "1.4.0",
        "1.4.1",
        "1.4.2",
        "1.4.3",
        "1.4.4",
        "1.4.5",
        "1.4.6",
        "1.5.0",
        "1.5.1",
        "1.5.2",
        "1.5.3",
        "1.6.0",
        "1.6.0a1",
        "1.6.0a2",
        "1.6.1",
        "1.6.2",
        "1.7.0",
        "1.7.1",
        "1.7.2",
        "1.7.3",
        "1.7.4",
        "1.8.0",
        "1.8.1",
        "1.8.2",
        "1.8.3",
        "1.9.0",
        "1.9.1",
        "1.9.2",
        "1.9.3",
        "1.9.4",
        "1.9.5",
        "1.9.6",
        "1.9.7",
        "2.0.0",
        "2.0.0a1",
        "2.0.0a2",
        "2.0.0a3",
        "2.0.0a4",
        "2.0.0a5",
        "2.0.0a6",
        "2.0.0rc1",
        "2.0.0rc2",
        "2.0.0rc3",
        "2.0.0rc4",
        "2.0.1",
        "2.0.2",
        "2.0.3",
        "2.0.4",
        "2.0.5",
        "2.0.6",
        "2.0.7",
        "2.0.8",
        "2.1.0",
        "2.1.1",
        "2.1.2",
        "2.1.3",
        "2.2.0",
        "2.2.0a1",
        "2.2.1",
        "2.2.10",
        "2.2.2",
        "2.2.3",
        "2.2.4",
        "2.2.5",
        "2.2.6",
        "2.2.7",
        "2.2.8",
        "2.2.9",
        "2.3.0",
        "2.3.1",
        "2.3.2",
        "2.3.3",
        "2.3.4",
        "2.3.5",
        "2.4.0",
        "2.4.1",
        "2.4.2",
        "2.4.3",
        "2.5.0",
        "2.5.1",
        "2.5.2",
        "2.6.0",
        "2.6.1",
        "2.6.2",
        "2.6.3",
        "2.7.0",
        "2.7.1",
        "2.7.2",
        "2.8.0",
        "2.8.1",
        "2.8.10",
        "2.8.11",
        "2.8.12",
        "2.8.13",
        "2.8.14",
        "2.8.15",
        "2.8.16",
        "2.8.17",
        "2.8.18",
        "2.8.19",
        "2.8.2",
        "2.8.20",
        "2.8.21",
        "2.8.22",
        "2.8.23",
        "2.8.24",
        "2.8.25",
        "2.8.26",
        "2.8.27",
        "2.8.28",
        "2.8.29",
        "2.8.3",
        "2.8.30",
        "2.8.31",
        "2.8.32",
        "2.8.33",
        "2.8.34",
        "2.8.4",
        "2.8.5",
        "2.8.6",
        "2.8.7",
        "2.8.8",
        "2.8.9",
        "3.0.0",
        "3.0.0rc1",
        "3.0.0rc2",
        "3.0.0rc3",
        "3.0.1",
        "3.0.11",
        "3.0.12",
        "3.0.13",
        "3.0.2",
        "3.0.3",
        "3.0.4",
        "3.0.5",
        "3.0.6",
        "3.0.7",
        "3.0.8",
        "3.0.9",
        "3.1.0",
        "3.1.1",
        "3.1.2",
        "3.1.3",
        "3.1.4",
        "3.1.5",
        "3.1.6",
        "3.1.7",
        "3.2.0",
        "3.2.1",
        "3.2.10",
        "3.2.11",
        "3.2.12",
        "3.2.13",
        "3.2.2",
        "3.2.4",
        "3.2.5",
        "3.2.6",
        "3.2.7",
        "3.2.8",
        "3.3.0",
        "3.3.0a1",
        "3.3.1",
        "3.3.10",
        "3.3.11",
        "3.3.12",
        "3.3.2",
        "3.3.3",
        "3.3.4",
        "3.3.5",
        "3.3.6",
        "3.3.7",
        "3.3.8",
        "3.3.9",
        "3.4.0",
        "3.4.1",
        "3.4.10",
        "3.4.11",
        "3.4.12",
        "3.4.13",
        "3.4.14",
        "3.4.15",
        "3.4.16",
        "3.4.17",
        "3.4.18",
        "3.4.2",
        "3.4.3",
        "3.4.4",
        "3.4.5",
        "3.4.6",
        "3.4.7",
        "3.4.8",
        "3.4.9",
        "3.5.0",
        "3.5.0a1.dev1",
        "3.5.0a2.dev1",
        "3.5.0a2.dev2",
        "3.5.0b1",
        "3.5.1",
        "3.5.10",
        "3.5.11",
        "3.5.12",
        "3.5.13",
        "3.5.14",
        "3.5.15",
        "3.5.16",
        "3.5.17",
        "3.5.2",
        "3.5.3",
        "3.5.4",
        "3.5.5",
        "3.5.6",
        "3.5.7",
        "3.5.8",
        "3.5.9",
        "3.6.0",
        "3.6.0a1",
        "3.6.1",
        "3.6.10",
        "3.6.11",
        "3.6.12",
        "3.6.13",
        "3.6.14",
        "3.6.15",
        "3.6.16",
        "3.6.17",
        "3.6.18",
        "3.6.19",
        "3.6.1a1",
        "3.6.2",
        "3.6.20",
        "3.6.3",
        "3.6.4",
        "3.6.5",
        "3.6.6",
        "3.6.7",
        "3.6.8",
        "3.6.9"
      ]
    }
  ],
  "aliases": [
    "CVE-2024-49375",
    "GHSA-cpv4-ggrr-7j9v"
  ],
  "details": "## Vulnerability\nA 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.\n\nThe prerequisites for this are:\n- The HTTP API must be enabled on the Rasa instance eg with `--enable-api`. This is not the default configuration.\n- For unauthenticated RCE to be exploitable, the user must not have configured any authentication or other security controls recommended in our documentation.\n- For authenticated RCE, the attacker must posses a valid authentication token or JWT to interact with the Rasa API.\n\n## Fix\nWe encourage you to upgrade to a version of Rasa that includes a fix. These are:\n\n - Rasa Pro 3.8.18, 3.9.16, 3.10.12\n- Rasa Open Source 3.6.21\n\nOnce 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.\n\nAffected components:\n\n- `CountVectorFeaturizer`\n- `LexicalSyntacticFeaturizer`\n - `LogisticRegressionClassifier`\n- `SklearnIntentClassifier`\n- `DIETClassifier`\n - `CRFEntityExtractor`\n- `TrackerFeaturizer`\n- `TEDPolicy`\n- `UnexpectedIntentTEDPolicy`\n \nIf you are unable to upgrade immediately, please follow our mitigation advice below.\n\n## Mitigation Advice\n\n- 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-api` to Rasa, you should also pass an authentication configuration as described in our documentation [here](https://rasa.com/docs/rasa-pro/production/rest-api/#enabling-the-rest-api). \n\n- The authenticated RCE can be mitigated by:\n    - 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.\n    - 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.\n\n## Future Releases\n As an additional security step, a future release of Rasa Pro will remove the ability to enable the API without any authentication method enabled.\n\n## Credit\nRasa would like to thank Julian Scheid from Deutsche Telekom Security GmbH for responsible disclosure of this vulnerability.",
  "id": "PYSEC-2026-513",
  "modified": "2026-07-01T20:23:03.548254Z",
  "published": "2026-06-29T11:50:38.223427Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/RasaHQ/rasa-pro-security-advisories/security/advisories/GHSA-cpv4-ggrr-7j9v"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49375"
    },
    {
      "type": "WEB",
      "url": "https://github.com/RasaHQ/rasa/commit/2bb1d779d4f4acaf70b6dfa35dd1899dccbb1ae6"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/rasahq/rasa"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/rasa"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-cpv4-ggrr-7j9v"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Rasa Allows Remote Code Execution via Remote Model Loading"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.