cal.diy through 6.2.0 contains an open redirect vulnerability in the conferencing OAuth callback endpoint that allows attackers to redirect users to arbitrary URLs by crafting malicious state parameters. Attackers can exploit the unsigned state parameter and onErrorReturnTo field to silently redirect visitors from the trusted domain to attacker-controlled URLs for phishing attacks.
CVE-2026-63768
Score 4.3 from GitHub Security Advisory published 2026-07-20. the CNA's CVSS baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 9.6%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 20, 2026cal.diy 6.2.0 Conferencing OAuth Callback Open Redirect via Unsigned State | Advisories | VulnCheck
https://www.vulncheck.com/advisories/cal-diy-conferencing-oauth-callback-open-redirect-via-unsigned-statefix(conferencing): prevent oauth callback open redirect
Upstream fix in progress (PR #29681 · calcom/cal.diy, state=open)
https://github.com/calcom/cal.diy/pull/29681Open Redirect via Unsigned Conferencing OAuth Callback State · Issue #29679 · calcom/cal.diy · GitHub
https://github.com/calcom/cal.diy/issues/29679Vendor Advisories for CVE-2026-63768(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 23:30 UTCEG score recompute
- 2026-07-22 23:30 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 20:41 UTCEG score recompute
- 2026-07-20 19:12 UTCEG score recompute
- 2026-07-20 19:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-601
Frequently asked(5)
What is CVE-2026-63768?
When was CVE-2026-63768 disclosed?
Is CVE-2026-63768 actively exploited?
What is the CVSS score of CVE-2026-63768?
How do I remediate CVE-2026-63768?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63768
Is Your Infrastructure Affected by CVE-2026-63768?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.