CVE-2026-25883 | Vexa-ai vexa prior 0.10.0-260419-1910 HTTP POST Request server-side request forgery (GHSA-fhr6-8hff-cvg4)

VDB-358343 · CVE-2026-25883 · GHSA-FHR6-8HFF-CVG4 VEXA-AI VEXA PRIOR 0.10.0-260419-1910 HTTP POST REQUEST SERVER-SIDE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.4 $0-$5k 4.08 Summaryinfo A vulnerability classified as critical has been found in Vexa-ai vexa. The impacted element is an unknown function of the component HTTP POST Request Handler. The manipulation leads to server-side request forgery. This vulnerability is listed as CVE-2026-25883. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component. Detailsinfo A vulnerability was found in Vexa-ai vexa. It has been rated as critical. This issue affects some unknown processing of the component HTTP POST Request Handler. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is: Vexa is an open-source, self-hostable meeting bot API and meeting transcription API. Prior to 0.10.0-260419-1910, the Vexa webhook feature allows authenticated users to configure an arbitrary URL that receives HTTP POST requests when meetings complete. The application performs no validation on the webhook URL, enabling Server-Side Request Forgery (SSRF). An authenticated attacker can set their webhook URL to target internal services (Redis, databases, admin panels), cloud metadata endpoints (AWS/GCP credential theft), and/or localhost services. Version 0.10.0-260419-1910 patches the issue. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-25883 since 02/06/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. 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.6 VulDB Meta Temp Score: 6.4 VulDB Base Score: 7.3 VulDB Temp Score: 7.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 5.8 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: Server-side request forgery CWE: CWE-918 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 02/06/2026 CVE reserved 04/20/2026 +72 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-fhr6-8hff-cvg4 Status: Confirmed CVE: CVE-2026-25883 (🔒) GCVE (CVE): GCVE-0-2026-25883 GCVE (VulDB): GCVE-100-358343 Entryinfo Created: 04/20/2026 20:02 Changes: 04/20/2026 20:02 (65) Complete: 🔍 Cache ID: 99:F86:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸