CVE-2026-63199

Perses's missing authorization in datasource proxy allows cross-scope secret disclosure

Workarounds

This issue can be avoided by using the provisioning to create the datasource and by removing the right to create datasource.

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.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Kodem intelligence

Already deployed Kodem?

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

1. What is CVE-2026-63199? CVE-2026-63199 is a high-severity missing authorization vulnerability in github.com/perses/perses (go), affecting versions >= 0.43.0, < 0.54.0-rc.0. It is fixed in 0.54.0-rc.0. The application does not perform an authorization check before performing a sensitive operation.
2. Which versions of github.com/perses/perses are affected by CVE-2026-63199? github.com/perses/perses (go) versions >= 0.43.0, < 0.54.0-rc.0 is affected.
3. Is there a fix for CVE-2026-63199? Yes. CVE-2026-63199 is fixed in 0.54.0-rc.0. Upgrade to this version or later.
4. Is CVE-2026-63199 exploitable, and should I be worried? Whether CVE-2026-63199 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-63199 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-63199? Upgrade github.com/perses/perses to 0.54.0-rc.0 or later.

Other vulnerabilities in github.com/perses/perses