# CVE-2026-63445: Perses: Unvalidated project parameter enables filesystem path traversal

> An authenticated attacker can exploit unvalidated project parameters in file-system database mode to read arbitrary files and bypass project isolation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-vr5f-w35q-98jp, GO-2026-6528

## What is CVE-2026-63445?

CVE-2026-63445 is a high-severity path traversal vulnerability in perses, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Perses is an open-source dashboard and visualization project for observability data. Prior to 0.54.0-rc.0, list endpoints used with the file-system database bind the request-controlled project query parameter into the resource Query structure without validating it against directory traversal characters, and the resulting project value is used to select database paths. An authenticated attacker can supply directory traversal segments to leave the intended project directory, read arbitrary YAML or JSON files accessible to the Perses process, and bypass project isolation to enumerate other file-backed resources. This issue is fixed in version 0.54.0-rc.0.

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

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

3 open source packages ship an affected version, including github.com/perses/perses.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/perses/perses` | Go | All versions | 0.54.0-rc.0 |
| `github.com/perses/perses` | Go | All versions | 0.54.0-rc.0 |
| `github.com/perses/perses` | Go | All versions | 0.54.0-rc.0 |

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

Upgrade github.com/perses/perses to 0.54.0-rc.0 or later.

## Is CVE-2026-63445 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63445 is a high-severity path traversal vulnerability in perses, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63445 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/perses/perses (Go): affected all versions; fixed in 0.54.0-rc.0
- github.com/perses/perses (Go): affected all versions; fixed in 0.54.0-rc.0
- github.com/perses/perses (Go): affected all versions; fixed in 0.54.0-rc.0

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-63445/ (Markdown: https://insights.sbomify.com/CVE-2026-63445/index.md)
```

## Sources

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

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