# CVE-2026-9349: calcom cal.diy Generic React API bookings-single-view.getServerSideProps.tsx getServerSideProps information disclosure

> Remote attackers can access sensitive booking data via the getServerSideProps function in Cal.com's web application.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-23fj-h8hh-93x3

## What is CVE-2026-9349?

CVE-2026-9349 is a medium-severity vulnerability in calcom cal.diy, published on 24 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in calcom cal.diy up to 4.9.4. Affected by this issue is the function getServerSideProps of the file apps/web/modules/bookings/views/bookings-single-view.getServerSideProps.tsx of the component Generic React API. This manipulation of the argument cancelledBy/rescheduledBy causes information disclosure. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-9349 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9349 is a medium-severity vulnerability in calcom cal.diy, published on 24 May 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-9349 exists.

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

## Sources

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

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