Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

Perses's unvalidated project parameter enables filesystem path traversal

CVE-2026-63445GHSA-vr5f-w35q-98jp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/perses/perses 0.54.0-rc.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · 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 · score source
EPSS
  • CVE-2026-63445: 0.56% estimated exploitation activity in the next 30 days; percentile 46.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-vr5f-w35q-98jp

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6528

  4. Revision 1 · created ·

    Published from osv record GHSA-vr5f-w35q-98jp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63445

Advisory: Perses's unvalidated project parameter enables filesystem path traversal
IDs: CVE-2026-63445, GHSA-vr5f-w35q-98jp
Record: https://patchnext.com/advisories/cve-2026-63445 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/perses/perses 0.54.0-rc.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/perses/perses: affected < 0.54.0-rc.0; fixed in 0.54.0-rc.0

## Suggested inspection (read-only)
- Go github.com/perses/perses: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/perses/perses.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vr5f-w35q-98jp (OSV record GHSA-vr5f-w35q-98jp lists affected ranges: Go github.com/perses/perses >=0 <0.54.0-rc.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6528 (OSV record GO-2026-6528 lists affected ranges: Go github.com/perses/perses >=0 <0.54.0-rc.0 (fixed))
- Verified: https://github.com/advisories/GHSA-vr5f-w35q-98jp (GitHub-reviewed advisory GHSA-vr5f-w35q-98jp lists affected ranges: Go github.com/perses/perses >=0 <0.54.0-rc.0)

Commands are suggestions: review each one before running it.

Loading voting…