dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-49375

CRITICAL · 9.0 CVSS v3.1 Published 2025-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Open source machine learning framework. A vulnerability has been identified in Rasa 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: 1. The HTTP API must be enabled on the Rasa instance eg with `--enable-api`. This is not the default configuration. 2. For unauthenticated RCE to be exploitable, the user must not have configured any authentication or other security controls recommended in our documentation. 3. For authenticated RCE, the attacker must posses a valid authentication token or JWT to interact with the Rasa API. This issue has been addressed in rasa version 3.6.21 and all users are advised to upgrade. Users unable to upgrade should ensure that they require authentication and that only trusted users are given access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Rasa Open Source contains a critical vulnerability (CVSS 9) allowing Remote Code Execution through loading a maliciously crafted model remotely. The attack requires the HTTP API to be enabled (--enable-api flag) and either no authentication configured or a valid authentication token.

MitigationUpgrade to Rasa version 3.6.21. If upgrading is not possible, ensure HTTP API authentication is properly configured and limit access to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Rasa installation and version
    Run 'rasa --version' or check your Python environment with 'pip show rasa' to retrieve the installed Rasa version number
    Affected if The installed version is lower than 3.6.21 (e.g., 3.5.x, 3.4.x, earlier versions)
  2. Verify HTTP API is enabled
    Check your Rasa startup command for the '--enable-api' flag, or inspect your 'credentials.yml' and 'endpoints.yml' configuration files for API-related endpoints (e.g., 'http://localhost:5005')
    Affected if The --enable-api flag is present in the startup command, or API endpoints are configured and exposed in your Rasa deployment
  3. Examine API authentication configuration
    Review your 'credentials.yml' and 'endpoints.yml' files, as well as any authentication middleware or token configuration, to determine whether the HTTP API requires authentication
    Affected if The HTTP API is exposed without authentication enforcement, or authentication is disabled or misconfigured for API endpoints
  4. Confirm API exposure to network
    Check your Rasa server configuration, firewall rules, or container/network settings to determine if the HTTP API port (default 5005) is accessible from untrusted networks or the public internet
    Affected if The Rasa API is reachable from untrusted network segments or the internet without proper access controls

You are affected if Rasa is installed with a version before 3.6.21 AND the HTTP API is enabled (--enable-api flag) AND authentication is either disabled or could be bypassed, creating a path for unauthenticated or authenticated remote code execution via model loading.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Rasa version 3.6.21. If upgrading is not possible, ensure HTTP API authentication is properly configured and limit access to trusted users only.

Recommended fix High confidence

Rasa version 3.6.21 or later

  1. Upgrade Rasa to version 3.6.21 or later by running the appropriate package manager command (e.g., pip install rasa==3.6.21)
  2. If upgrading is not immediately possible, ensure the HTTP API is not enabled unless absolutely necessary
  3. Configure authentication for the Rasa HTTP API if it must be enabled
  4. Restrict access to the Rasa API to only trusted users and networks
  5. Review and implement security controls as recommended in the Rasa documentation

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-49375 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data