CloudBeaver: Path Traversal in Resource Manager getProjectPath allows directory enumeration outside shared-projects sandbox
- Exploited
- No known exploitation
- Fix
- Fixed in 26.1.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 26.1.0.
- 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? →
- 8/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, is affected by a path traversal flaw in its resource manager that lets a logged-in user with resource-management privileges reach the server remotely and list directory names outside the shared-projects folder, which can reveal filesystem layout. Arbitrary file reads, writes, and deletion have not been confirmed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
CloudBeaver is a cloud database manager. Prior to 26.1.2, its resource-management project resolution accepts project identifiers without validating that they are safe path components. An authenticated user with resource-management privileges can supply a crafted project identifier that causes path resolution to escape the shared-projects directory and enumerate directory names elsewhere on the server. This can disclose filesystem layout information. Arbitrary file reads, writes, and deletion are not confirmed. The issue is fixed in 26.1.2 by validating project names before resolving the shared-project path.
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
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 26.1.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- dbeaver cloudbeaver
fixed in 26.1.0
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-55449
Is CVE-2026-55449 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-55449?
cloudbeaver: before 26.1.0.Source: cve.now feed data
How do I fix CVE-2026-55449?
Upgrade to a fixed version: 26.1.0.Source: cve.now feed data