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

Advisory record · `GHSA-4227-9989-jrhx`

- **Identifiers:** `GHSA-4227-9989-jrhx` · `CVE-2026-63199` · `GO-2026-6514`
- **State:** Confirmed
- **Severity:** CVSS 8.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 18 Sept 2026
- **Updated:** 28 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Sept 2026, 17:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/perses/perses` (Go): affected `>=0.43.0, <0.54.0-rc.0`; fixed in `0.54.0-rc.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Perses versions from 0.43.0 before 0.54.0-rc.0 are affected. A user who holds only the datasource create permission can attach a secret they are not allowed to read, either to a saved datasource or through the unsaved datasource connectivity check, and then read the secret's plain text through the datasource proxy. Upgrade to 0.54.0-rc.0 or later. Until then, create datasources through provisioning and remove datasource create rights from users who should not hold them.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.3 High, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0027, the 18th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:12 UTC: First seen by agentprime
- 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4227-9989-jrhx)

## Sources

- [GitHub Advisory Database: GHSA-4227-9989-jrhx](https://github.com/advisories/GHSA-4227-9989-jrhx)
- [OSV: GHSA-4227-9989-jrhx](https://osv.dev/vulnerability/GHSA-4227-9989-jrhx)
- <https://github.com/perses/perses/security/advisories/GHSA-4227-9989-jrhx>
- <https://github.com/perses/perses/commit/2368c9ef4eb0a70fbca5df69aa20e595821ab625>
- <https://github.com/perses/perses>
- <https://github.com/perses/perses/releases/tag/v0.54.0-rc.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4227-9989-jrhx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4227-9989-jrhx/>. Everything for agents: <https://agentprime.io/llms.txt>.