CVE-2025-32377

Vulnerability

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 impacts the following connectors:

• audiocodes_stream
• genesys
• jambonz

As part of our investigation to resolve this issue, we have also performed a security review of our other voice channel connectors:

• browser_audio: Does not support authentication. This is a development channel not intended for production use.
• twilio_media_streams, twilio_voice and jambonz: Authentication is currently not supported by these channels, but our investigation has found a way for us to enable it for these voice channel connectors in a future Rasa Pro release.

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

CVE-2025-32377 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.12.6, 3.11.7, 3.10.19, 3.9.20); upgrading removes the vulnerable code path.

Kodem intelligence

The issue has been resolved for audiocodes, audiocodes_stream, and genesys connectors. Fixed versions of Rasa Pro have been released for 3.9.20, 3.10.19, 3.11.7 and 3.12.6. Please update to a fixed release.

If you are using one of the affected connectors, we strongly recommend upgrading to a fixed version. For connectors where authentication is not supported (e.g., Twilio), we suggest taking extra caution and considering other compensating controls if applicable.

1. What is CVE-2025-32377? CVE-2025-32377 is a medium-severity missing authentication for critical function vulnerability in rasa-pro (pip), affecting versions >= 3.12.0, <= 3.12.5. It is fixed in 3.12.6, 3.11.7, 3.10.19, 3.9.20. A critical operation is accessible without requiring any authentication.
2. How severe is CVE-2025-32377? CVE-2025-32377 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of rasa-pro are affected by CVE-2025-32377? rasa-pro (pip) versions >= 3.12.0, <= 3.12.5 is affected.
4. Is there a fix for CVE-2025-32377? Yes. CVE-2025-32377 is fixed in 3.12.6, 3.11.7, 3.10.19, 3.9.20. Upgrade to this version or later.
5. Is CVE-2025-32377 exploitable, and should I be worried? Whether CVE-2025-32377 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-32377 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-32377?
   • Upgrade rasa-pro to 3.12.6 or later
   • Upgrade rasa-pro to 3.11.7 or later
   • Upgrade rasa-pro to 3.10.19 or later
   • Upgrade rasa-pro to 3.9.20 or later