# CVE-2026-112043: calcom cal.com/cal.diy Webhook util.ts createWebhookProcedure authorization

> Attackers can bypass authorization checks in the webhook handler by manipulating the ID argument, potentially accessing unauthorized webhook data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **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:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-6wcv-37vq-r5jx

## What is CVE-2026-112043?

CVE-2026-112043 is a medium-severity missing authorization vulnerability in calcom cal.com, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in calcom cal.com and cal.diy up to 6.2.0. Impacted is the function createWebhookProcedure of the file packages/trpc/server/routers/viewer/webhook/util.ts of the component Webhook Handler. Executing a manipulation of the argument ID can lead to authorization bypass. It is possible to launch the attack remotely. The pull request to fix this issue awaits acceptance.

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

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


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

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

## Is CVE-2026-112043 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112043 is a medium-severity missing authorization vulnerability in calcom cal.com, published on 19 Oct 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-112043 exists.

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

## Sources

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

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