Skip to content
skopnix

NVD published 18 Sep 2026

CVE-2026-63445

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.

Signals

KEV, exploited in the wild
no
EPSS, 30-day forecast
0.6%, 47th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

Not in CISA's catalogue as of the last daily pull. Absence is not proof of safety. No score published by NVD.

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 1 dispatch

  1. GHSA-vr5f-w35q-98jp: Perses's unvalidated project parameter enables filesystem path traversal

Public exploit code none in our sources

No public exploit in the sources we track: GitHub proof-of-concept lists, Metasploit and Exploit-DB. Absence is not proof that none exists.

Nuclei detection templates1

  1. Perses before 0.54.0-rc.0 contains a path traversal vulnerability in the list endpoints when the file system database is used. The project query parameter is bound into the resource Query struct without validation and is joined into the database folder path, which is then walked and every file with the configured extension is returned. An attacker can leave the database folder and read arbitrary JSON or YAML files that the Perses process can access. Authentication is disabled in the default conf

    yaml · first seen by skopnix 18 Nov 2026

A Nuclei template is a scanner check that detects the flaw. It is not an exploit and is not counted as one.

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check