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

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-fhr6-8hff-cvg4

## 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 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-25883?

It affects 1 product.


Products: 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.

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

- [CVE-2026-25058](https://insights.sbomify.com/CVE-2026-25058/): Vexa's unauthenticated internal transcript endpoint exposed by default (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25883 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25883 exists.

Affected product: Vexa-ai vexa. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25883/ (Markdown: https://insights.sbomify.com/CVE-2026-25883/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25883
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25883
- OSV: https://osv.dev/vulnerability/CVE-2026-25883

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25883/
Summaries are generated and may contain mistakes; the official description above is the record.