Quick answers
- Is CVE-2026-55449 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55449 being exploited in the wild.
- How severe is CVE-2026-55449?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- DBeaver CloudBeaver prior to 26.1.2.
- Is there a fix for CVE-2026-55449?
- 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-55449 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-55449?
- 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 is a path traversal flaw in the resource-management project resolution component. The affected code accepts project identifiers without validating them as safe path components, allowing authenticated users to supply crafted identifiers that cause path resolution to escape the shared-projects directory. The fix validates project names before resolving paths using GeneralUtils.validateResourceNameUnconditionally().
Affected products
- DBeaver CloudBeaver prior to 26.1.2
Timeline
- 2026-11-06: disclosed