Perses is an open-source dashboard and visualization project for observability data. Prior to 0.54.0-beta.3, an authenticated user with viewer access to one project can supply another project through the project query parameter on project-scoped list endpoints, including /api/v1/projects/{project}/dashboards and /api/v1/datasources. The request-controlled project value is used to select dashboards, datasources, and variables without enforcing the caller's authorization for that selected project, which breaks project-level tenant isolation and exposes complete resource specifications belonging to other projects. This issue is fixed in version 0.54.0-beta.3.
CVE-2026-63458
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (3)
Auto-updated Sep 18, 20260.54.0-beta.3 / 2026-07-06
Patch available: perses/perses v0.54.0-beta.3 (pre-release)
https://github.com/perses/perses/releases/tag/v0.54.0-beta.3commit 8015fb340bdc (perses/perses)
Fix landed in perses/perses commit 8015fb340bdc — awaiting tagged release
https://github.com/perses/perses/commit/8015fb340bdc625953e73a7a688be5b939159540Use query parameter project to list resources without having access to · Advisory · perses/perses · GitHub
https://github.com/perses/perses/security/advisories/GHSA-cjgj-2fwf-4c2wVendor Advisories for CVE-2026-63458(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× 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.
- 2026-09-20 21:55 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 21:13 UTCEG score recompute
- 2026-09-18 20:31 UTCEG score recompute
- 2026-09-18 19:55 UTCEG score recompute
- 2026-09-18 18:27 UTCEG score recompute
- 2026-09-18 17:44 UTCEG score recompute
- 2026-09-18 17:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-63458?
When was CVE-2026-63458 disclosed?
Is CVE-2026-63458 actively exploited?
What is the CVSS score of CVE-2026-63458?
How do I remediate CVE-2026-63458?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63458
Is Your Infrastructure Affected by CVE-2026-63458?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.