Quick answers
- Is CVE-2026-63663 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63663 being exploited in the wild.
- How severe is CVE-2026-63663?
- Medium severity, with a CVSS score of 6.5, published 6 November 2026.
- Which products and versions are affected?
- DBeaver CloudBeaver 23.2.3 to 26.1.1.
- Is there a fix for CVE-2026-63663?
- Yes: fixed in 26.1.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63663 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-63663?
- Check whether you run DBeaver CloudBeaver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 26.1.2
Technical details
The vulnerability exists in the SQL result-editing functionality (WebSQLProcessor.java) where insufficient path validation allows an authenticated attacker to traverse outside the intended session-scoped temporary upload directory. The attack requires authentication and SQL result-editing privileges. An attacker can craft a malicious file ID parameter to resolve paths outside the bounds of the intended upload folder, reading arbitrary files accessible to the CloudBeaver server process. The fix validates file IDs as UUIDs and ensures resolved paths remain within the session upload directory using path normalization and bounds checking.
Affected products
- dbeaver CloudBeaver 23.2.3 to 26.1.1
Timeline
- 2026-11-06: disclosed
- 2026-06-24: patched