Vulnerability in github.com/perses/perses (CVE-2026-63199)
Summary
Vulnerability in github.com/perses/perses (CVE-2026-63199). Risk of unauthorized operations or information disclosure. Exploitable via GlobalDatasource. Mitigation: upgrade to 0.54.0-rc.0 or later.
Original description
The description as published by the source.
Impact
The datasource proxy authorizes the caller on the Datasource scope, then resolves and decrypts any Secret named in the request body with no Secret-scope check.
Datasource and Secret are distinct, independently grantable role scopes, so an operator can grant datasource access without secret access. The proxy and the service to create a datasource does not verify that the operator has the correct right.
A user holding only GlobalDatasource:create can create a GlobalDatasource and attached to it a GlobalSecret without having the right to get access to. The user can also do the same by using the unSaved datasource feature proposed by the proxy used to verify the connectivity to the datasource before creating the resource.
As soon as you can attach a secret that you don't have right to see, you can then create a Datasource that you control and then read anything send by Perses. Which include the secret in plain text. You can then have access to the secret without being granted to.
The project-scoped variant does the same within a project.
Patches
The proxy and the service to create the datasource is verifying if you have the right to read a secret if a secret is attached to the datasource.
This is patch in v0.54.0-rc.0
Workarounds
This issue can be avoided by using the provisioning to create the datasource and by removing the right to create datasource.
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-63199 has been found in github.com/perses/perses.
Attackers can target a specific entry point like GlobalDatasource 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-63199" on the vendor's site.
CVE-2026-63199 (github.com/perses/perses) — CWE-862
Attack surface: GlobalDatasource / GlobalSecret
Patched: 0.54.0-rc.0 — apply immediately
Workaround: This issue can be avoided by using the provisioning to create the datasource and by removing the right to create datasource.
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-862) exists in github.com/perses/perses. Attackers reach the vulnerable code path via GlobalDatasource.
Check the vendor advisory for the affected versions of github.com/perses/perses. Attack surface: GlobalDatasource / GlobalSecret.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.54.0-rc.0.
Workaround: This issue can be avoided by using the provisioning to create the datasource and by removing the right to create datasource.
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
This issue can be avoided by using the provisioning to create the datasource and by removing the right to create datasource.パッチが適用されるまでの応急処置として、This issue can be avoided by using the provisioning to create the datasource and by removing the right to create datasource. を実施。回避策の副作用 (機能低下) を確認した上で。
-
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