CVE-2026-63445 — perses
Fix: perses/perses@75e5471CVE-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's unvalidated project parameter enables filesystem path traversal
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.
Real-World Exposure
github.com/perses/persesReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/perses/perses | all versions | 0.54.0-rc.0go get github.com/perses/perses@v0.54.0-rc.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-63445 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-63445. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-63445 in your dependencies?
O3 Security finds CVE-2026-63445 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.