# CVE-2026-6057: Unauthenticated Path Traversal in FalkorDB Browser Leads to Remote Code Execution

> Unauthenticated attackers can exploit a path traversal flaw in FalkorDB Browser to write arbitrary files and achieve remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-2987-f6gf-82vj

## What is CVE-2026-6057?

CVE-2026-6057 is a critical path traversal vulnerability in FalkorDB Browser, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FalkorDB Browser 1.9.3 contains an unauthenticated path traversal vulnerability in the file upload API that allows remote attackers to write arbitrary files and achieve remote code execution.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-6057?


## How do I fix CVE-2026-6057?

No fix has been published for CVE-2026-6057 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6057 being exploited?

There is no known exploitation of CVE-2026-6057 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6057 and fix it if it is affected.

What it is: CVE-2026-6057 is a critical path traversal vulnerability in FalkorDB Browser, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6057 in the wild and no public exploit code.

Affected product: FalkorDB Browser. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6057/ (Markdown: https://insights.sbomify.com/CVE-2026-6057/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6057
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6057
- OSV: https://osv.dev/vulnerability/CVE-2026-6057

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6057/
Summaries are generated and may contain mistakes; the official description above is the record.