# CVE-2026-16624: CVE-2026-16624

> Authenticated users can create webhooks for any team by injecting unvalidated team IDs, allowing them to steal sensitive booking data including emails and passwords.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-4fwh-xxpv-xfm6, GHSA-72qw-2qpq-fg7j

## What is CVE-2026-16624?

CVE-2026-16624 is a critical missing authorization vulnerability in Cal.com Cal.diy, published on 22 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cal.com OSS ships lacks authorization on webhook teamId creation, allowing any authenticated user to create a webhook on any team via unvalidated teamId injection, then steal booking data, including fields like organizer/attendee emails and custom responses, and conditionally video-call passwords, by triggering webhook delivery.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


## How do I fix CVE-2026-16624?

No fix has been published for CVE-2026-16624 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16624 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16624 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16624 is a critical missing authorization vulnerability in Cal.com Cal.diy, published on 22 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16624 exists.

Affected product: Cal.com Cal.diy. 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-16624/ (Markdown: https://insights.sbomify.com/CVE-2026-16624/index.md)
```

## Sources

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

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