Vulnerability in github.com/perses/perses (CVE-2026-63458)
Summary
Vulnerability in github.com/perses/perses (CVE-2026-63458). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/projects/team-a/dashboards. Mitigation: upgrade to 0.54.0-beta.3 or later.
Original description
The description as published by the source.
Impact
What kind of vulnerability is it?
An authenticated user who is only a viewer on project team-a requests GET /api/v1/projects/team-a/dashboards?project=finance-secret (or simply GET /api/v1/datasources?project=finance-secret) and receives the full list of the finance-secret project's dashboards and datasource specifications, despite having no role on that project. This defeats Perses' project-level tenant isolation for all project-scoped read resources.
Who is impacted?
Any authenticated user reads every project's dashboards, datasources, variables across tenants.
Patches
Has the problem been patched? What versions should users upgrade to?
Workarounds
None
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-63458 has been found in github.com/perses/perses.
Attackers can target a specific entry point like GET /api/v1/projects/team-a/dashboards 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-beta.3 or later.
If unsure, ask your IT team or search "github.com/perses/perses CVE-2026-63458" on the vendor's site.
CVE-2026-63458 (github.com/perses/perses) — CWE-639
Attack surface: GET /api/v1/projects/team-a/dashboards / GET /api/v1/datasources
Patched: 0.54.0-beta.3 — apply immediately
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.
A vulnerability (CWE-639) exists in github.com/perses/perses. Attackers reach the vulnerable code path via GET /api/v1/projects/team-a/dashboards.
Check the vendor advisory for the affected versions of github.com/perses/perses. Attack surface: GET /api/v1/projects/team-a/dashboards / GET /api/v1/datasources.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.54.0-beta.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/projects/team-a/dashboards requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/projects/team-a/dashboards' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/projects/team-a/dashboardsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/perses/perses to 0.54.0-beta.3ステージング環境で 0.54.0-beta.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/projects/team-a/dashboards on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com