# CVE-2026-63199: Perses: Missing authorization in datasource proxy allows cross-scope secret disclosure

> Low-privilege users can bypass scope separation to disclose secrets via datasource proxy, requiring an upgrade to Perses.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-4227-9989-jrhx, GO-2026-6514

## What is CVE-2026-63199?

CVE-2026-63199 is a high-severity missing authorization vulnerability in perses, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Perses is an open-source dashboard and visualization project for observability data. From 0.43.0 until 0.54.0-rc.0, the datasource creation and unsaved datasource proxy paths authorize the caller on a Datasource or GlobalDatasource scope but do not require read permission for the separately grantable associated project or global Secret before resolving it. A low-privilege user with GlobalDatasource:create or corresponding project datasource creation rights can attach a project or global Secret that the user cannot otherwise read, point the datasource at a service controlled by the user, and cause Perses to send the decrypted secret in plaintext, bypassing project and global scope separation. This issue is fixed in version 0.54.0-rc.0.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-63199?

3 open source packages ship an affected version, including github.com/perses/perses.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/perses/perses` | Go | From 0.43.0 | 0.54.0-rc.0 |
| `github.com/perses/perses` | Go | From 0.43.0 | 0.54.0-rc.0 |
| `github.com/perses/perses` | Go | From 0.43.0 | 0.54.0-rc.0 |

## How do I fix CVE-2026-63199?

Upgrade github.com/perses/perses to 0.54.0-rc.0 or later.

## Is CVE-2026-63199 being exploited?

There is no known exploitation of CVE-2026-63199 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63199 and fix it if it is affected.

What it is: CVE-2026-63199 is a high-severity missing authorization vulnerability in perses, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63199 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/perses/perses (Go): affected from 0.43.0; fixed in 0.54.0-rc.0
- github.com/perses/perses (Go): affected from 0.43.0; fixed in 0.54.0-rc.0
- github.com/perses/perses (Go): affected from 0.43.0; fixed in 0.54.0-rc.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63199/ (Markdown: https://insights.sbomify.com/CVE-2026-63199/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63199
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63199
- OSV: https://osv.dev/vulnerability/CVE-2026-63199

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63199/
Summaries are generated and may contain mistakes; the official description above is the record.