CloudBeaver: Path Traversal in updateResultsDataBatch Allows Unauthorized Server File Stream Access
- Exploited
- No known exploitation
- Fix
- Fixed in 26.1.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 26.1.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
CloudBeaver, a cloud database manager, has a path traversal flaw in its SQL result-editing feature that lets a logged-in user with result-editing privileges read files from the server outside the intended temporary upload directory. It can be reached remotely by any user with those low-level privileges, and no user interaction is needed; in affected database value-handling cases, it can expose local files readable by the CloudBeaver server process.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
CloudBeaver is a cloud database manager. From version 23.2.3 until 26.1.2, a path traversal vulnerability in its SQL result-editing functionality allows an authenticated user with SQL result-editing privileges to cause the server to open files outside the intended temporary upload directory. In affected database value-handling scenarios, this can disclose local files readable by the CloudBeaver server process. Version 26.1.2 prevents traversal outside the intended temporary upload directory.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 26.1.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- dbeaver cloudbeaver
From 23.2.3 · fixed in 26.1.2
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63663
Is CVE-2026-63663 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-63663?
cloudbeaver: from 23.2.3 before 26.1.2.Source: cve.now feed data
How do I fix CVE-2026-63663?
Upgrade to a fixed version: 26.1.2.Source: cve.now feed data