CVE-2025-32377
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRasa 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVoice connectors in Rasa Pro (aicodec, audiocodes_stream, and genesys) fail to enforce authentication even when a token is configured in credentials.yml, allowing unauthenticated attackers to submit voice data directly to the conversational AI assistant.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Rasa Pro versionRun 'rasa --version' or check the installed Rasa Pro package version via pip list | grep rasa-proAffected if Installed version is earlier than 3.9.20, 3.10.19, 3.11.7, or 3.12.6
-
Locate credentials.ymlFind the credentials.yml file in the Rasa Pro deployment, typically in the project root or ./rasa directoryAffected if File exists and is accessible
-
Check for affected voice connectorsInspect credentials.yml for any of these connector entries: 'aicodec:', 'audiocodes_stream:', or 'genesys:'Affected if Any of the three voice connectors (aicodec, audiocodes_stream, genesys) are present in the configuration file
-
Verify connector is enabledConfirm that the connector entry in credentials.yml is not commented out and contains configuration values (not empty)Affected if An affected connector is uncommented and configured with values (even if a token is set, the flaw bypasses authentication)
If Rasa Pro version is below the fixed releases AND any of the aicodec, audiocodes_stream, or genesys voice connectors are enabled in credentials.yml, the environment is affected by this authentication bypass vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Rasa Pro to version 3.9.20, 3.10.19, 3.11.7, or 3.12.6 (or later) to patch the authentication bypass in the affected voice connectors.
Upgrade to Rasa Pro 3.12.6 (or at minimum 3.9.20, 3.10.19, or 3.11.7 depending on compatibility)
- Identify current Rasa Pro version by checking the installed package version (e.g., pip show rasa-pro or looking in requirements.txt)
- Upgrade to one of the fixed versions: 3.9.20, 3.10.19, 3.11.7, or 3.12.6
- Run pip install rasa-pro==<chosen_version> or update requirements.txt with the chosen version
- Redeploy the Rasa Pro application with the updated version
- Verify that authentication is now properly enforced for audiocodes, audiocodes_stream, and genesys voice connectors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32377 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data