# CVE-2026-9304: calcom cal.diy Logo API route.ts validateUrlForSSRF server-side request forgery

> Attackers can exploit a flaw in the Logo API to perform server-side request forgery, potentially accessing internal resources.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 23 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-6c7x-v3mr-g29x

## What is CVE-2026-9304?

CVE-2026-9304 is a low-severity server-side request forgery vulnerability in calcom cal.diy, published on 23 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in calcom cal.diy up to 4.9.4. The affected element is the function validateUrlForSSRF of the file apps/web/app/api/logo/route.ts of the component Logo API. The manipulation results in server-side request forgery. It is possible to launch the attack remotely. Attacks of this nature are highly complex. The exploitability is described as difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-9304 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9304 is a low-severity server-side request forgery vulnerability in calcom cal.diy, published on 23 May 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-9304 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-9304/ (Markdown: https://insights.sbomify.com/CVE-2026-9304/index.md)
```

## Sources

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

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