CVE-2026-63445: Perses: Unvalidated project parameter enables filesystem path traversal
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Perses is an open-source dashboard and visualization project for observability data. Prior to 0.54.0-rc.0, list endpoints used with the file-system database bind the request-controlled project query parameter into the resource Query structure without validating it against directory traversal characters, and the resulting project value is used to select database paths. An authenticated attacker can supply directory traversal segments to leave the intended project directory, read arbitrary YAML or JSON files accessible to the Perses process, and bypass project isolation to enumerate other file-backed resources. This issue is fixed in version 0.54.0-rc.0.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-09-18).
Weakness: CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. 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
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 9 references on Exploit Observer
Live scores
- EPSS
- 0.006
low predicted chance of attack - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| perses | version < 0.54.0-rc.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-63445 Perses - Path Traversal via project query parameter on list endpoints. Add them to your Suricata rule set and reload.
Show the rules
# CVE-2026-63445 - Perses < 0.54.0-rc.0 path traversal. List endpoints backed by the file-system
# database bind the request-controlled 'project' query parameter into the resource query without
# validating directory-traversal characters (validation only runs on Create/Update bodies), letting
# an authenticated attacker leave the project directory and read arbitrary file-backed resources
# (e.g. GET /api/v1/dashboards?project=../projects). Matches a list request whose project parameter
# begins with a traversal sequence.
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-63445 Perses - Path Traversal via project query parameter on list endpoints"; flow:established,to_server; http.uri; content:"/api/v1/"; nocase; content:"project="; nocase; fast_pattern; pcre:"/[?&]project=(?:\.\.|%2e%2e)(?:%2f|\/)/i"; classtype:web-application-attack; reference:cve,CVE-2026-63445; reference:url,https://www.exploit.observer/?keyword=CVE-2026-63445&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=perses&match=exact; sid:1100603; rev:1;)
CVE-2026-63445.rules on GitHub
References
Other references
- https://github.com/perses/perses/security/advisories/GHSA-vr5f-w35q-98jp (x_refsource_CONFIRM)
- https://github.com/perses/perses/commit/75e5471040ccb5674ea8d25c2aa16c80ccb70b2a (x_refsource_MISC)
- https://github.com/perses/perses/releases/tag/v0.54.0-rc.0 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
