github.com/perses/perses
Affected
- introduced
0, fixed0.54.0-rc.0(semver)
Fixed versions
0.54.0-rc.0
Fix
- Fixed version
0.54.0-rc.0go get github.com/perses/[email protected]
Advisory
Also known as: CVE-2026-63445, GO-2026-6528
Perses's unvalidated project parameter enables filesystem path traversal
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.
High Basis: The source's own band: HIGH
0, fixed 0.54.0-rc.0 (semver)0.54.0-rc.0
0.54.0-rc.0go get github.com/perses/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0