NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

CVE-2026-63445 — perses

Fix: perses/perses@75e5471

CVE-2026-63445 is a Path Traversal vulnerability in github.com/perses/perses. A fix is available for github.com/perses/perses — see the affected versions and patch details below.

Perses: Unvalidated project parameter enables filesystem path traversal

Also known asGHSA-vr5f-w35q-98jpGO-2026-6528
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-63445.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk
0.06%0.39%0.73%1.06%0.6%0.6%Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected
🐹github.com/perses/perses

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

When Perses is using the file system database, on the list endpoints, the project value is bound from the request into the resource Query struct and is never validated against directory-traversal characters (validation/Flatten only runs for Create/Update bodies, not list queries).

The path is then used to retrieve files in the database directly.

Attacker can read arbitrary YAML/JSON files from the server host and can bypass the security constraints to get access to other resources contained in the file database.

For example https://localhost:8080/api/v1/dashboards?project=../projects returns the list of the project while it must not return anything.

Patches

Has the problem been patched? What versions should users upgrade to?

Workarounds

Avoid using the file system database in production. Use SQL database instead.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/perses/persesall versions0.54.0-rc.0go get github.com/perses/perses@v0.54.0-rc.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/perses/perses, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/perses/perses to 0.54.0-rc.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-63445 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This Moderate information disclosure flaw in Perses, an open-source dashboard and visualization project, is not present in Red Hat products. The vulnerable code that allows an authenticated attacker to perform directory traversal and read arbitrary files is not included in Red Hat's supported offerings.

Workaround published by Red Hat
No mitigation is currently available for this vulnerability. Red Hat recommends applying the available security update when it becomes available.
Source: Red Hat security advisory for CVE-2026-63445 (CC BY 4.0)

Frequently Asked Questions

### Impact When Perses is using the file system database, on the list endpoints, the project value is bound from the request into the resource `Query` struct and is never validated against directory-traversal characters (validation/Flatten only runs for Create/Update bodies, not list queries). The path is then used to retrieve files in the database directly. Attacker can read arbitrary YAML/JSON files from the server host and can bypass the security constraints to get access to other resources contained in the file database. For example `https://localhost:8080/api/v1/dashboards?project=..
O3 Security · Impact-Aware SCA

Is CVE-2026-63445 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-63445: perses — Fixed in 0.54.0-rc.0