Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.3amended

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

CVE-2026-63199GHSA-4227-9989-jrhx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/perses/perses 0.54.0-rc.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-63199: 0.27% estimated exploitation activity in the next 30 days; percentile 18.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-4227-9989-jrhx

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6514

  4. Revision 1 · created ·

    Published from osv record GHSA-4227-9989-jrhx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63199

Advisory: Perses's missing authorization in datasource proxy allows cross-scope secret disclosure
IDs: CVE-2026-63199, GHSA-4227-9989-jrhx
Record: https://patchnext.com/advisories/cve-2026-63199 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/perses/perses 0.54.0-rc.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/perses/perses: affected >= 0.43.0, < 0.54.0-rc.0; fixed in 0.54.0-rc.0

## Suggested inspection (read-only)
- Go github.com/perses/perses: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/perses/perses.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4227-9989-jrhx (OSV record GHSA-4227-9989-jrhx lists affected ranges: Go github.com/perses/perses >=0.43.0 <0.54.0-rc.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6514 (OSV record GO-2026-6514 lists affected ranges: Go github.com/perses/perses >=0.43.0 <0.54.0-rc.0 (fixed))
- Verified: https://github.com/advisories/GHSA-4227-9989-jrhx (GitHub-reviewed advisory GHSA-4227-9989-jrhx lists affected ranges: Go github.com/perses/perses >=0.43.0 <0.54.0-rc.0)

Commands are suggestions: review each one before running it.

Loading voting…