# CVE-2025-32377: Rasa Pro Missing Authentication For Voice Connector APIs

> Attackers can submit voice data to Rasa Pro assistants without authentication due to missing checks in voice connectors, requiring an upgrade to patched versions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Apr 2025
- **Updated:** 18 Apr 2025
- **Also known as:** GHSA-7xq5-54jp-2mfg, PYSEC-2026-1862

## What is CVE-2025-32377?

CVE-2025-32377 is a medium-severity missing authorization vulnerability in RasaHQ rasa-pro-security-advisories, published on 18 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-32377?

9 open source packages ship an affected version, including rasa-pro.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rasa-pro` | PyPI | All versions | 3.9.20, 3.10.19, 3.11.7, 3.12.6 |
| `rasa-pro` | PyPI | All versions | 3.9.20 |
| `rasa-pro` | PyPI | All versions | 3.9.20 |
| `rasa-pro` | PyPI | From 3.10.0 | 3.10.19 |
| `rasa-pro` | PyPI | From 3.10.0 | 3.10.19 |
| `rasa-pro` | PyPI | From 3.11.0 | 3.11.7 |
| `rasa-pro` | PyPI | From 3.11.0 | 3.11.7 |
| `rasa-pro` | PyPI | From 3.12.0 | 3.12.6 |
| `rasa-pro` | PyPI | From 3.12.0 | 3.12.6 |

## How do I fix CVE-2025-32377?

Upgrade rasa-pro to a fixed version for your release line: 3.9.20, 3.10.19, 3.11.7 or 3.12.6.

## Is CVE-2025-32377 being exploited?

There is no known exploitation of CVE-2025-32377 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32377 and fix it if it is affected.

What it is: CVE-2025-32377 is a medium-severity missing authorization vulnerability in RasaHQ rasa-pro-security-advisories, published on 18 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32377 in the wild and no public exploit code.

Affected packages and fixed versions:
- rasa-pro (PyPI): affected all versions; fixed in 3.9.20, 3.10.19, 3.11.7, 3.12.6
- rasa-pro (PyPI): affected all versions; fixed in 3.9.20
- rasa-pro (PyPI): affected all versions; fixed in 3.9.20
- rasa-pro (PyPI): affected from 3.10.0; fixed in 3.10.19
- rasa-pro (PyPI): affected from 3.10.0; fixed in 3.10.19
- rasa-pro (PyPI): affected from 3.11.0; fixed in 3.11.7
- rasa-pro (PyPI): affected from 3.11.0; fixed in 3.11.7
- rasa-pro (PyPI): affected from 3.12.0; fixed in 3.12.6
- rasa-pro (PyPI): affected from 3.12.0; fixed in 3.12.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32377/ (Markdown: https://insights.sbomify.com/CVE-2025-32377/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32377
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32377
- OSV: https://osv.dev/vulnerability/CVE-2025-32377

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32377/
Summaries are generated and may contain mistakes; the official description above is the record.