A vulnerability has been found in Vexa-ai vexa and classified as critical . This affects an unknown function of the file /internal/transcripts/ . This manipulation of the argument meeting_id causes missing authentication. This vulnerability appears as CVE-2026-25058 . The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358334 · CVE-2026-25058 · GHSA-W73R-2449-QWGH
VEXA-AI VEXA PRIOR 0.10.0-260419-1910 /INTERNAL/TRANSCRIPTS/ MEETING_ID MISSING AUTHENTICATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
6.3 $0-$5k 3.40
Summaryinfo
A vulnerability was found in Vexa-ai vexa and classified as critical. This impacts an unknown function of the file /internal/transcripts/. Such manipulation of the argument meeting_id leads to missing authentication. This vulnerability is traded as CVE-2026-25058. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.
Detailsinfo
A vulnerability was found in Vexa-ai vexa. It has been rated as critical. Affected by this issue is an unknown code of the file /internal/transcripts/. The manipulation of the argument meeting_id with an unknown input leads to a missing authentication vulnerability. Using CWE to declare the problem leads to CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Impacted is confidentiality. CVE summarizes:
Vexa is an open-source, self-hostable meeting bot API and meeting transcription API. Prior to 0.10.0-260419-1910, the Vexa transcription-collector service exposes an internal endpoint `GET /internal/transcripts/{meeting_id}` that returns transcript data for any meeting without any authentication or authorization checks. An unauthenticated attacker can enumerate all meeting IDs, access any user's meeting transcripts without credentials, and steal confidential business conversations, passwords, and/or PII. Version 0.10.0-260419-1910 patches the issue.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-25058 since 01/28/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit.
Upgrading to version 0.10.0-260419-1910 eliminates this vulnerability.
Productinfo
Type
Artificial Intelligence Software
Vendor
Vexa-ai
Name
vexa
Website
Product: https://github.com/Vexa-ai/vexa/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Missing authentication
CWE: CWE-306 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: vexa 0.10.0-260419-1910
Timelineinfo
01/28/2026 CVE reserved
04/20/2026 +81 days Advisory disclosed
04/20/2026 +0 days VulDB entry created
04/20/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: GHSA-w73r-2449-qwgh
Status: Confirmed
CVE: CVE-2026-25058 (🔒)
GCVE (CVE): GCVE-0-2026-25058
GCVE (VulDB): GCVE-100-358334
Entryinfo
Created: 04/20/2026 19:55
Changes: 04/20/2026 19:55 (66)
Complete: 🔍
Cache ID: 99:4BD:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸