Approved changes feed: RSS · Atom

cpe:2.3:a:rasahq:rasa-pro-security-advisories:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorRasahq (8c9d8b45-e032-50e5-93f5-025249154f67)
ProductRasa Pro Security Advisories (2651a08d-4001-53fe-bedf-a57721a4c1ea)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2025-32377 vulnerable 2026-06-08 07:18:59.688595 Rasa Pro Missing Authentication For Voice Connector APIs
MEDIUM (6.5)
Rasa Pro is a framework for building scalable, dynamic conversational AI assistants that integrate large language models (LLMs). A vulnerability has been identified in Rasa Pro where voice connectors in Rasa Pro do not properly implement authentication even when a token is configured in the credentials.yml file. This could allow an attacker to submit voice data to the Rasa Pro assistant from an unauthenticated source. This issue has been patched for audiocodes, audiocodes_stream, and genesys connectors in versions 3.9.20, 3.10.19, 3.11.7 and 3.12.6.
Published: 2025-04-18T19:59:32.286Z
Updated: 2025-04-18T20:35:41.744Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-49375 vulnerable 2026-06-08 06:50:13.734419 Remote Code Execution via Remote Model Loading in Rasa
CRITICAL (9.1)
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.
Published: 2025-01-14T18:59:53.181Z
Updated: 2025-01-15T15:17:13.557Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.