Is CVE-2026-63458 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63458 being exploited in the wild.

How severe is CVE-2026-63458?

High severity, with a CVSS score of 4, published 18 September 2026.

Which products and versions are affected?

github.com/perses/perses (Go) < 0.54.0-beta.3, SEMVER:introduced=0,fixed=0.54.0-beta.3; Perses < 0.54.0-beta.3.

Is there a fix for CVE-2026-63458?

Yes. github.com/perses/perses (Go): upgrade to 0.54.0-beta.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63458 attacked?

It is attacked over the network.

Am I affected by CVE-2026-63458?

Check whether you run github.com/perses/perses (Go) or Perses at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63458: Perses project query parameter authorization bypass

Q: Is there a fix for CVE-2026-63458?

Yes. github.com/perses/perses (Go): upgrade to 0.54.0-beta.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-63458 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-63458?

Check whether you run github.com/perses/perses (Go) or Perses at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63458 · Severity: high · CVSS 4 · Published 2026-09-18

Perses is a dashboard and data visualization platform that uses projects to isolate data and access control between teams. An authenticated user can bypass project-level access controls by manipulating a query parameter, allowing them to read dashboards, data sources, and variables from projects they should not have access to, even if they have no assigned role on those projects.

Technologies: github.com/perses/perses (Go), Perses. Vendors: Go, Perses.

Quick answers

Is CVE-2026-63458 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63458 being exploited in the wild.
How severe is CVE-2026-63458?: High severity, with a CVSS score of 4, published 18 September 2026.
Which products and versions are affected?: github.com/perses/perses (Go) < 0.54.0-beta.3, SEMVER:introduced=0,fixed=0.54.0-beta.3; Perses < 0.54.0-beta.3.
Is there a fix for CVE-2026-63458?: Yes. github.com/perses/perses (Go): upgrade to 0.54.0-beta.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63458 attacked?: It is attacked over the network.
Am I affected by CVE-2026-63458?: Check whether you run github.com/perses/perses (Go) or Perses at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/perses/perses (Go): upgrade to 0.54.0-beta.3 or later
```
go get github.com/perses/perses@v0.54.0-beta.3
```

Technical details

This is an authorization bypass vulnerability (CWE-639) in Perses' API endpoints for project-scoped read resources. An authenticated user with a viewer role on one project can request endpoints such as GET /api/v1/projects/team-a/dashboards?project=finance-secret or GET /api/v1/datasources?project=finance-secret to retrieve full resource listings from other projects to which they have no access. The vulnerability affects all project-scoped read operations and completely defeats project-level tenant isolation. Attack requires only network access and an authenticated session (low privilege); no additional preconditions apply. The vulnerability was patched in version 0.54.0-beta.3.

Affected products

Perses Perses < 0.54.0-beta.3

Identifiers

CVE-2026-63458
GHSA-cjgj-2fwf-4c2w
GO-2026-6518

Timeline

2026-07-15: disclosed
2026-09-18: advisory
2026-09-18: patched: version 0.54.0-beta.3 released

References

https://api.github.com/users/bhilaire1a

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.