CVE-2026-63445

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 46% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Sep 18, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

0.54.0-rc.0 / 2026-07-16

Patch available: perses/perses v0.54.0-rc.0 (pre-release)

https://github.com/perses/perses/releases/tag/v0.54.0-rc.0
github_commit

commit 75e5471040cc (perses/perses)

Fix landed in perses/perses commit 75e5471040cc — awaiting tagged release

https://github.com/perses/perses/commit/75e5471040ccb5674ea8d25c2aa16c80ccb70b2a
github Patch Available

Unvalidated project parameter enables filesystem path traversal · Advisory · perses/perses · GitHub

https://github.com/perses/perses/security/advisories/GHSA-vr5f-w35q-98jp

Vendor Advisories for CVE-2026-63445(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/perses/perses—0.54.0-rc.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 21:38 UTCEG score recompute
  2. 2026-09-23 22:17 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 21:32 UTCEG score recompute
  5. 2026-09-22 09:10 UTCEG score recompute
  6. 2026-09-21 08:24 UTCEG score recompute
  7. 2026-09-20 20:16 UTCEPSS rescore
  8. 2026-09-19 19:12 UTCEG score recompute
  9. 2026-09-18 18:27 UTCEG score recompute
  10. 2026-09-18 18:15 UTCEG score recompute
  11. 2026-09-18 17:44 UTCEG score recompute
  12. 2026-09-18 17:44 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/perses/perses

Frequently asked(5)

What is CVE-2026-63445?
CVE-2026-63445 is a high vulnerability published on September 18, 2026. 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…
When was CVE-2026-63445 disclosed?
CVE-2026-63445 was first published in the National Vulnerability Database on September 18, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63445 actively exploited?
CVE-2026-63445 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.3% of all scored CVEs.
What is the CVSS score of CVE-2026-63445?
CVE-2026-63445 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-63445?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63445, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63445

Explore →

Is Your Infrastructure Affected by CVE-2026-63445?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs