{"answers":{"affected":"3 open source packages ship an affected version, including github.com/perses/perses.","exploited":"There is no known exploitation of CVE-2026-63199 in the wild and no public exploit code.","fix":"Upgrade github.com/perses/perses to 0.54.0-rc.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-63199 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-63199 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/perses/perses (Go): affected from 0.43.0; fixed in 0.54.0-rc.0\n- github.com/perses/perses (Go): affected from 0.43.0; fixed in 0.54.0-rc.0\n- github.com/perses/perses (Go): affected from 0.43.0; fixed in 0.54.0-rc.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63199/ (Markdown: https://insights.sbomify.com/CVE-2026-63199/index.md)","id":"CVE-2026-63199","markdown":"https://insights.sbomify.com/CVE-2026-63199/index.md","name":"CVE-2026-63199","record":{"aliases":["GHSA-4227-9989-jrhx","GO-2026-6514"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Perses dashboard","requires_auth":"low_privilege","summary":"Low-privilege users can bypass scope separation to disclose secrets via datasource proxy, requiring an upgrade to Perses.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Perses: Missing authorization in datasource proxy allows cross-scope secret disclosure","id":"CVE-2026-63199","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Logto: Account API can disclose stored third-party provider tokens without the identities scope","id":"CVE-2026-63203"},"packages":[{"ecosystem":"Go","fixed":["0.54.0-rc.0"],"introduced":["0.43.0"],"last_affected":[],"package":"github.com/perses/perses","purl":null,"source":"GHSA-4227-9989-jrhx"},{"ecosystem":"Go","fixed":["0.54.0-rc.0"],"introduced":["0.43.0"],"last_affected":[],"package":"github.com/perses/perses","purl":"pkg:golang/github.com/perses/perses","source":"GHSA-4227-9989-jrhx"},{"ecosystem":"Go","fixed":["0.54.0-rc.0"],"introduced":["0.43.0"],"last_affected":[],"package":"github.com/perses/perses","purl":"pkg:golang/github.com/perses/perses","source":"GO-2026-6514"}],"prev":{"headline":"FearlessCMS: Unauthenticated debug scripts expose filesystem operations and XSS","id":"CVE-2026-63190"},"products":["perses"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["perses"]},"summary":"Low-privilege users can bypass scope separation to disclose secrets via datasource proxy, requiring an upgrade to Perses.","url":"https://insights.sbomify.com/CVE-2026-63199/"}