Perses's missing authorization in datasource proxy allows cross-scope secret disclosure
CVE-2026-63199 (GitHub advisory GHSA-4227-9989-jrhx) is a high-severity vulnerability with a CVSS 4.0 base score of 8.3, classed as Missing Authorization (CWE-862), in github.com/perses/perses (Go). Affected versions: >= 0.43.0, < 0.54.0-rc.0. It is fixed in 0.54.0-rc.0.
Published 18 Sept 2026Updated 18 Sept 2026
- CVE ID
- CVE-2026-63199
- GHSA ID
- GHSA-4227-9989-jrhx
- EPSS
- 0.26%higher than 19% of CVEs
- Weakness (CWE)
- CWE-862Missing Authorization
- KEV status
- Not in KEV
- Published
- 18 Sept 2026
- Updated
- 18 Sept 2026
- Ecosystem
- Go
- Assigned by (CNA)
- GitHub_M
Summary
Source: OSV (GitHub advisory)
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.
Technical details
Source: GitHub Advisory Database
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NHigh8.3Base score from GitHub Advisory Database
- Attack Vector AV
- Network
- Attack Complexity AC
- Low
- Attack Requirements AT
- None
- Privileges Required PR
- Low
- User Interaction UI
- None
- Confidentiality (Vulnerable System) VC
- High
- Integrity (Vulnerable System) VI
- None
- Availability (Vulnerable System) VA
- None
- Confidentiality (Subsequent Systems) SC
- High
- Integrity (Subsequent Systems) SI
- None
- Availability (Subsequent Systems) SA
- None
Affected packages
Source: OSV (GitHub advisory)
- github.com/perses/persesGo
pkg:golang/github.com/perses/perses- Affected versions
- >= 0.43.0, < 0.54.0-rc.0
- Fixed in
- 0.54.0-rc.0
| Package | Affected versions | Fixed in |
|---|---|---|
github.com/perses/perses Go pkg:golang/github.com/perses/perses |
|
|
Fix
Source: OSV (GitHub advisory)
Fix available
Upgrade to 0.54.0-rc.0 or later.
Patch commits
Merge commit from fork
+168 −34 across 6 files
- internal/api/dependency/service_manager.go+2 −2
- internal/api/impl/proxy/globaldatasource.go+11 −6
- internal/api/impl/proxy/localdatasource.go+11 −6
- internal/api/impl/proxy/projectdatasource.go+11 −6
- internal/api/impl/v1/datasource/service.go+73 −7
- internal/api/impl/v1/globaldatasource/service.go+60 −7
Release commits
The commits each fixed release tag points at. They usually bump the version rather than contain the fix itself.
Vulnerability intelligence
Root cause analysis
Vulnerable functions
References
Advisories 4
Package 1
Other links 1
Credits
- ImDuongfinder
Questions about CVE-2026-63199
- What is the GHSA ID for CVE-2026-63199?
- GitHub tracks CVE-2026-63199 as GHSA-4227-9989-jrhx.
- What is the CVSS score of CVE-2026-63199?
- CVE-2026-63199 has a CVSS 4.0 base score of 8.3 (High), vector 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.
- Which versions are affected by CVE-2026-63199?
- github.com/perses/perses (Go): >= 0.43.0, < 0.54.0-rc.0.
- How do I fix CVE-2026-63199?
- Upgrade to 0.54.0-rc.0 or later. The fix is in commit 2368c9e.
- What is the Package URL (PURL) for CVE-2026-63199?
- The affected package's PURL is pkg:golang/github.com/perses/perses.
- Is CVE-2026-63199 exploited in the wild?
- CISA's Known Exploited Vulnerabilities catalog doesn't list CVE-2026-63199. That means no confirmed exploitation has been catalogued, not that it is safe to leave unpatched. EPSS estimates a 0.26% chance of exploitation in the next 30 days, higher than 19% of CVEs.
Data sources
Upstream records
- OSV (GitHub advisory)LoadedRaw JSON
- GitHub Advisory DatabaseLoadedRaw JSON
- OSV (CVE record)LoadedRaw JSON
- CVE.orgLoaded
- CISA KEV catalogLoaded
Fetched 1 day ago (14 Oct 2026, 17:49 UTC). Records refresh automatically after 24 hours.
Where each part of this page came from
- Title and description
- OSV (GitHub advisory)
- Severity score
- GitHub Advisory Database
- Weakness (CWE)
- GitHub Advisory Database
- Affected packages
- OSV (GitHub advisory)
- Fix
- OSV (GitHub advisory)
- References
- Computed by CVEminer
- KEV status
- CISA KEV catalog
- EPSS
- GitHub Advisory Database
OSV and GitHub Advisory Database content is licensed CC BY 4.0. Values marked as computed or derived were calculated by CVEminer from the upstream data.