Perses's unvalidated project parameter enables filesystem path traversal
CVE-2026-63445 (GitHub advisory GHSA-vr5f-w35q-98jp) is a high-severity vulnerability with a CVSS 4.0 base score of 7.1, classed as Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22), in github.com/perses/perses (Go). Affected versions: < 0.54.0-rc.0. It is fixed in 0.54.0-rc.0.
Published 18 Sept 2026Updated 18 Sept 2026
- CVE ID
- CVE-2026-63445
- GHSA ID
- GHSA-vr5f-w35q-98jp
- EPSS
- 0.56%higher than 45% of CVEs
- Weakness (CWE)
- CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- KEV status
- Not in KEV
- Published
- 18 Sept 2026
- Updated
- 18 Sept 2026
- Ecosystem
- Go
- Assigned by (CNA)
- GitHub_M
Summary
Source: OSV (GitHub advisory)
Impact
When Perses is using the file system database, on the list endpoints, the project value is bound from the request into the resource Query struct and is never validated against directory-traversal characters (validation/Flatten only runs for Create/Update bodies, not list queries).
The path is then used to retrieve files in the database directly.
Attacker can read arbitrary YAML/JSON files from the server host and can bypass the security constraints to get access to other resources contained in the file database.
For example https://localhost:8080/api/v1/dashboards?project=../projects returns the list of the project while it must not return anything.
Patches
Has the problem been patched? What versions should users upgrade to?
Workarounds
Avoid using the file system database in production. Use SQL database instead.
Technical details
Source: GitHub Advisory Database
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NHigh7.1Base score from GitHub Advisory Database
- Attack Vector AV
- Network
- Attack Complexity AC
- Low
- Attack Requirements AT
- None
- Privileges Required PR
- Low
- User Interaction UI
- None
- Confidentiality (Vulnerable System) VC
- High
- Integrity (Vulnerable System) VI
- None
- Availability (Vulnerable System) VA
- None
- Confidentiality (Subsequent Systems) SC
- None
- Integrity (Subsequent Systems) SI
- None
- Availability (Subsequent Systems) SA
- None
CISA SSVC decision points
- Exploitation
- none
- No public exploitation evidence
- Automatable
- no
- Needs manual steps per target
- Technical impact
- partial
- Limited control of the affected system
CISA Coordinator assessment (SSVC 2.0.3) via CVE.org.
Affected packages
Source: OSV (GitHub advisory)
- github.com/perses/persesGo
pkg:golang/github.com/perses/perses- Affected versions
- < 0.54.0-rc.0
- Fixed in
- 0.54.0-rc.0
| Package | Affected versions | Fixed in |
|---|---|---|
github.com/perses/perses Go pkg:golang/github.com/perses/perses |
|
|
Fix
Source: OSV (GitHub advisory)
Fix available
Upgrade to 0.54.0-rc.0 or later.
Patch commits
Merge commit from fork
+4 −0 across 1 file
- internal/api/toolbox/list.go+4 −0
Release commits
The commits each fixed release tag points at. They usually bump the version rather than contain the fix itself.
Vulnerability intelligence
Root cause analysis
Vulnerable functions
References
Advisories 4
Package 1
Other links 1
Credits
- bhilaire1afinder
Questions about CVE-2026-63445
- What is the GHSA ID for CVE-2026-63445?
- GitHub tracks CVE-2026-63445 as GHSA-vr5f-w35q-98jp.
- What is the CVSS score of CVE-2026-63445?
- CVE-2026-63445 has a CVSS 4.0 base score of 7.1 (High), vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N.
- Which versions are affected by CVE-2026-63445?
- github.com/perses/perses (Go): < 0.54.0-rc.0.
- How do I fix CVE-2026-63445?
- Upgrade to 0.54.0-rc.0 or later. The fix is in commit 75e5471.
- What is the Package URL (PURL) for CVE-2026-63445?
- The affected package's PURL is pkg:golang/github.com/perses/perses.
- Is CVE-2026-63445 exploited in the wild?
- CISA's Known Exploited Vulnerabilities catalog doesn't list CVE-2026-63445. That means no confirmed exploitation has been catalogued, not that it is safe to leave unpatched. CISA's SSVC assessment rates exploitation as "none". EPSS estimates a 0.56% chance of exploitation in the next 30 days, higher than 45% of CVEs.
Data sources
Upstream records
- OSV (GitHub advisory)LoadedRaw JSON
- GitHub Advisory DatabaseLoadedRaw JSON
- OSV (CVE record)LoadedRaw JSON
- CVE.orgLoaded
- CISA KEV catalogLoaded
Fetched 1 day ago (14 Oct 2026, 17:49 UTC). Records refresh automatically after 24 hours.
Where each part of this page came from
- Title and description
- OSV (GitHub advisory)
- Severity score
- GitHub Advisory Database
- Weakness (CWE)
- GitHub Advisory Database
- Affected packages
- OSV (GitHub advisory)
- Fix
- OSV (GitHub advisory)
- References
- Computed by CVEminer
- SSVC
- CVE.org
- KEV status
- CISA KEV catalog
- EPSS
- GitHub Advisory Database
OSV and GitHub Advisory Database content is licensed CC BY 4.0. Values marked as computed or derived were calculated by CVEminer from the upstream data.