GHSA-VR5F-W35Q-98JP
Vulnerability from github – Published: 2026-09-18 17:40 – Updated: 2026-09-18 17:40Impact
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.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/perses/perses"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.54.0-rc.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-63445"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-18T17:40:03Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Impact\nWhen 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). \n\nThe path is then used to retrieve files in the database directly.\n\nAttacker 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.\n\nFor example `https://localhost:8080/api/v1/dashboards?project=../projects` returns the list of the project while it must not return anything.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\n### Workarounds\nAvoid using the file system database in production. Use SQL database instead.",
"id": "GHSA-vr5f-w35q-98jp",
"modified": "2026-09-18T17:40:03Z",
"published": "2026-09-18T17:40:03Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/perses/perses/security/advisories/GHSA-vr5f-w35q-98jp"
},
{
"type": "WEB",
"url": "https://github.com/perses/perses/commit/75e5471040ccb5674ea8d25c2aa16c80ccb70b2a"
},
{
"type": "PACKAGE",
"url": "https://github.com/perses/perses"
},
{
"type": "WEB",
"url": "https://github.com/perses/perses/releases/tag/v0.54.0-rc.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
}
],
"summary": "Perses\u0027s unvalidated project parameter enables filesystem path traversal"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.