CVE-2025-32377Medium· 6.5▾ SunlitRasa Pro Missing Authentication For Voice Connector APIs
▾ Sunlit zone — Low / medium · no exploitation signal
impact 35.8 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.4%
0.4% → 0.5%
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_streamgenesysjambonzAs 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.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.
rasa-pro >= 3.12.0, < 3.12.6rasa-pro >= 3.11.0, < 3.11.7rasa-pro >= 3.10.0, < 3.10.19rasa-pro < 3.9.20Upgrade to a patched release:
rasa-pro 3.12.6rasa-pro 3.11.7rasa-pro 3.10.19rasa-pro 3.9.20