How severe is CVE-2026-63458?

No CVSS score has been assigned to CVE-2026-63458 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-63458?

CVE-2026-63458 affects the following packages: github.com/perses/perses (Go). Ecosystems affected: Go.

How do I fix CVE-2026-63458?

Update github.com/perses/perses to 0.54.0-beta.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-63458 is resolved across your whole dependency graph.

How do I detect CVE-2026-63458 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/perses/perses, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-63458 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-63458 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-63458 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-63458?

CVE-2026-63458 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-63458?

CVE-2026-63458 is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-63458 published, and has it been updated?

CVE-2026-63458 was published on September 18, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-63458 — perses

Fix: perses/perses@8015fb3

CVE-2026-63458 is a CWE-639 vulnerability in github.com/perses/perses. A fix is available for github.com/perses/perses — see the affected versions and patch details below.

Perses project query parameter authorization bypass exposes cross-project resources

Also known asGHSA-cjgj-2fwf-4c2wGO-2026-6518

Published

Sep 18, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-63458.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.11%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/perses/perses

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

What kind of vulnerability is it?

An authenticated user who is only a viewer on project team-a requests GET /api/v1/projects/team-a/dashboards?project=finance-secret (or simply GET /api/v1/datasources?project=finance-secret) and receives the full list of the finance-secret project's dashboards and datasource specifications, despite having no role on that project. This defeats Perses' project-level tenant isolation for all project-scoped read resources.

Who is impacted?

Any authenticated user reads every project's dashboards, datasources, variables across tenants.

Patches

Has the problem been patched? What versions should users upgrade to?

Workarounds

None

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/perses/perses`	all versions	0.54.0-beta.3`go get github.com/perses/perses@v0.54.0-beta.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/perses/perses, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/perses/perses to 0.54.0-beta.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-63458 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This Moderate impact information disclosure flaw in Perses, as used in Red Hat Advanced Cluster Management for Kubernetes, allows an authenticated user with viewer access to one project to bypass authorization and view resources from other projects. The vulnerability is rated Moderate due to the prerequisite of…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2026-63458 (CC BY 4.0)

Frequently Asked Questions

### Impact _What kind of vulnerability is it?_ An authenticated user who is only a viewer on project team-a requests GET /api/v1/projects/team-a/dashboards?project=finance-secret (or simply GET /api/v1/datasources?project=finance-secret) and receives the full list of the finance-secret project's dashboards and datasource specifications, despite having no role on that project. This defeats Perses' project-level tenant isolation for all project-scoped read resources. _Who is impacted?_ Any authenticated user reads every project's dashboards, datasources, variables across tenants. ### Patches