CVE-2026-63199

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Sep 18, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

0.54.0-rc.0 / 2026-07-16

Patch available: perses/perses v0.54.0-rc.0 (pre-release)

https://github.com/perses/perses/releases/tag/v0.54.0-rc.0
github_commit

commit 2368c9ef4eb0 (perses/perses)

Fix landed in perses/perses commit 2368c9ef4eb0 — awaiting tagged release

https://github.com/perses/perses/commit/2368c9ef4eb0a70fbca5df69aa20e595821ab625
github Patch Available

Missing authorization in datasource proxy allows cross-scope secret disclosure · Advisory · perses/perses · GitHub

https://github.com/perses/perses/security/advisories/GHSA-4227-9989-jrhx

Vendor Advisories for CVE-2026-63199(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/perses/perses—0.54.0-rc.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 21:24 UTCEG score recompute
  2. 2026-09-24 21:12 UTCEG score recompute
  3. 2026-09-24 18:01 UTCEG score recompute
  4. 2026-09-23 19:42 UTCEG score recompute
  5. 2026-09-23 17:54 UTCEPSS rescore
  6. 2026-09-22 21:40 UTCEG score recompute
  7. 2026-09-21 23:36 UTCEG score recompute
  8. 2026-09-21 01:34 UTCEG score recompute
  9. 2026-09-20 20:16 UTCEPSS rescore
  10. 2026-09-19 16:30 UTCEG score recompute
  11. 2026-09-18 18:27 UTCEG score recompute
  12. 2026-09-18 17:44 UTCEG score recompute
  13. 2026-09-18 17:44 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/perses/perses

Frequently asked(5)

What is CVE-2026-63199?
CVE-2026-63199 is a high vulnerability published on September 18, 2026. 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…
When was CVE-2026-63199 disclosed?
CVE-2026-63199 was first published in the National Vulnerability Database on September 18, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63199 actively exploited?
CVE-2026-63199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.6% of all scored CVEs.
What is the CVSS score of CVE-2026-63199?
CVE-2026-63199 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-63199?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63199, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63199

Explore →

Is Your Infrastructure Affected by CVE-2026-63199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs