CVE-2026-25883 Vexa Webhook Feature has a SSRF Vulnerability
Authenticated attackers can exploit unvalidated webhook URLs to access internal services and cloud metadata, risking credential theft and data exposure.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-25883?
CVE-2026-25883 is a medium-severity server-side request forgery vulnerability in Vexa-ai vexa, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-918
Which versions are affected by CVE-2026-25883?
It affects 1 product.
Products include Vexa Vexa.
How do I fix CVE-2026-25883?
No fix has been published for CVE-2026-25883 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-25883 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25883 exists.
Other vulnerabilities in Vexa-ai vexa
Sources
Also known as GHSA-fhr6-8hff-cvg4.