CloudBeaver: Authorization Bypass (BFLA) - Data Export Restriction Bypass
- 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 an authorization flaw where some server-side data exports ignore the administrator's global export restriction. A remote attacker who has a low-privilege, non-administrative login and access to a shared database connection can use it to export database contents they are allowed to query but not export.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
CloudBeaver is a cloud database manager. In versions up to and including 26.1.1, some server-side export operations do not consistently enforce the global data export restriction. An authenticated non-administrative user with access to a shared database connection can initiate certain server-side data exports even when an administrator has disabled exports. This can disclose database contents that the user is permitted to query but is not permitted to export. The issue does not grant additional database read privileges. It is fixed in 26.1.2 by consistently enforcing the global restriction for server-side exports.
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
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-63664
Is CVE-2026-63664 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-63664?
cloudbeaver: before 26.1.2.Source: cve.now feed data
How do I fix CVE-2026-63664?
Upgrade to a fixed version: 26.1.2.Source: cve.now feed data