pypi package report

Is rasa safe?

2 known vulnerabilities, worst severity CRITICAL.

// reach

5 direct dependencies

2 carry known advisories, worst HIGH

0 packages depend on it

an advisory here reaches each of them

    Create a free accountfor every dependency path, dependent and what to upgrade
    // ai model usage

    No published models are known to use this package.


    cvss
    9.0
    critical

    CVSS v3.1 base score out of 10

    epss
    0.94%
    medium

    chance of exploitation in 30 days, 61st percentile of all CVEs

    xyz score
    4.0
    medium

    CyberXYZ composite out of 10

    fig. 01 — GHSA-cpv4-ggrr-7j9v, the advisory selected below

    // 2 advisories

    GHSA-cpv4-ggrr-7j9v

    CRITICALGitHub ratingCVE-2024-49375
    // 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.

    // cvss v3.1 vector

    CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

    Attack vector
    Network
    Attack complexity
    High
    Privileges required
    None
    User interaction
    None
    Scope
    Changed
    Confidentiality
    High
    Integrity
    High
    Availability
    High

    Checked 2026-11-08 at 00:22 UTC. The most recent advisory here was published 2025-01-14. Updated continuously from NVD, GHSA, OSV and CNA feeds.

    Think a verdict here is wrong? Tell us — we respond within 2 business days.