CVE-2025-32377 — rasa-pro
MEDIUMCVE-2025-32377 is a medium-severity (CVSS 6.5) Missing Authentication vulnerability in rasa-pro. A fix is available for rasa-pro — see the affected versions and patch details below.
Rasa Pro Missing Authentication For Voice Connector APIs
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-32377.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
rasa-pro🐍rasa-pro🐍rasa-pro🐍rasa-proReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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_streamgenesysjambonz
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_voiceandjambonz: 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.
Fix
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | rasa-pro | ≥ 3.12.0&&< 3.12.6 | 3.12.6pip install --upgrade 'rasa-pro==3.12.6' |
| 🐍PyPI | rasa-pro | ≥ 3.11.0&&< 3.11.7 | 3.11.7pip install --upgrade 'rasa-pro==3.11.7' |
| 🐍PyPI | rasa-pro | ≥ 3.10.0&&< 3.10.19 | 3.10.19pip install --upgrade 'rasa-pro==3.10.19' |
| 🐍PyPI | rasa-pro | all versions | 3.9.20pip install --upgrade 'rasa-pro==3.9.20' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rasa-pro, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rasa-pro to 3.12.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32377 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2025-32377 in your dependencies?
Find it across PyPI, including transitive dependencies.