Perses
Perses: Unvalidated project parameter enables filesystem path traversal
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.54.0-rc.0
Fixed in 0.54.0-rc.0
Mitigation
Upgrade perses to 0.54.0-rc.0 or later.
References
- Vendor advisory github.com/perses/perses/security/advisories/G…
- Patch github.com/perses/perses/commit/75e5471040ccb5…
- Release notes github.com/perses/perses/releases/tag/v0.54.0-…
Timeline
Days relative to CVE publicationFirst public PoC 60 days after publication; not in CISA KEV. First PoC: nuclei template: Perses < 0.54.0-rc.0 - Path Traversal Arbitrary File Read (nuclei template, 18 Nov 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Perses < 0.54.0-rc.0 - Path Traversal Arbitrary File Read | 18 Nov 2026 | 18 Nov 2026 |