Path Traversal in github.com/perses/perses (CVE-2026-63445)
Summary
Path traversal in github.com/perses/perses (CVE-2026-63445). Risk of unauthorized operations or information disclosure. Exploitable via Query. Mitigation: upgrade to 0.54.0-rc.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-63445 has been found in github.com/perses/perses.
Attackers can target a specific entry point like Query over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/perses/perses to 0.54.0-rc.0 or later.
If unsure, ask your IT team or search "github.com/perses/perses CVE-2026-63445" on the vendor's site.
CVE-2026-63445 (github.com/perses/perses) — CWE-22
Attack surface: Query
Patched: 0.54.0-rc.0 — apply immediately
Workaround: Avoid using the file system database in production.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/perses/perses. Attackers reach the vulnerable code path via Query.
Check the vendor advisory for the affected versions of github.com/perses/perses. Attack surface: Query.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.54.0-rc.0.
Workaround: Avoid using the file system database in production.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/perses/perses' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/perses/perses' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/perses/persesを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Avoid using the file system database in production.パッチが適用されるまでの応急処置として、Avoid using the file system database in production. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/perses/perses to 0.54.0-rc.0ステージング環境で 0.54.0-rc.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com