CVE-2026-63199

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-83267 (ENISA EUVD) · GHSA-4227-9989-jrhx (GitHub Security Advisories)Source: ENISA EUVD

8.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Perses is an open-source dashboard and visualization project for observability data. From 0.43.0 until 0.54.0-rc.0, the datasource creation and unsaved datasource proxy paths authorize the caller on a Datasource or GlobalDatasource scope but do not require read permission for the separately grantable associated project or global Secret before resolving it. A low-privilege user with GlobalDatasource:create or corresponding project datasource creation rights can attach a project or global Secret that the user cannot otherwise read, point the datasource at a service controlled by the user, and cause Perses to send the decrypted secret in plaintext, bypassing project and global scope separation. This issue is fixed in version 0.54.0-rc.0.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity83% × 45%
Impact severity (EG Severity): CVSS 8.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.3): severity, escalated by confirmed exploitation. This CVE's 8.3 is its impact severity (EG Severity), not escalated.

EG Severity
8.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 18, 2026

Last Modified

September 30, 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 2368c9ef4eb0 (perses/perses)

Fix landed in perses/perses commit 2368c9ef4eb0 — awaiting tagged release

https://github.com/perses/perses/commit/2368c9ef4eb0a70fbca5df69aa20e595821ab625
GitHub advisoryMentions a patch (unverified)

Missing authorization in datasource proxy allows cross-scope secret disclosure · Advisory · perses/perses · GitHub

https://github.com/perses/perses/security/advisories/GHSA-4227-9989-jrhx

Vendor Advisories for CVE-2026-63199(2)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcluster-observability-operator/perses-rhel9:17908545012026-10-01redhat
gogithub.com/perses/perses @ 0.54.0-rc.0 (fixes >= 0.43.0, < 0.54.0-rc.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/perses/perses—
  • 0.43.0 up to 0.54.0-rc.0: fixed in 0.54.0-rc.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 70× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-4227-9989-jrhx · GitHub severity HIGH
  3. 2026-11-01 07:41 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-27 18:47 UTCEG score recompute
  9. 2026-10-27 18:47 UTCVendor advisory
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-25 14:13 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-10-20 09:18 UTCEG score recompute
  20. 2026-10-20 09:18 UTCVendor advisory
  21. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-10-18 03:23 UTCEG score recompute
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
Show 74 more
  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-13 12:03 UTCEG score recompute
  5. 2026-10-13 12:03 UTCVendor advisory
  6. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-12 15:49 UTCEG score recompute
  8. 2026-10-12 01:44 UTCVendor advisory
  9. 2026-10-11 19:33 UTCEG score recompute
  10. 2026-10-11 16:48 UTCEG score recompute
  11. 2026-10-11 13:58 UTCEG score recompute
  12. 2026-10-11 13:58 UTCVendor advisory
  13. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-10-11 02:47 UTCEG score recompute
  15. 2026-10-11 02:47 UTCVendor advisory
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-10 13:33 UTCVendor advisory
  18. 2026-10-10 02:29 UTCEG score recompute
  19. 2026-10-10 02:29 UTCVendor advisory
  20. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-10-09 15:28 UTCVendor advisory
  22. 2026-10-09 04:27 UTCVendor advisory
  23. 2026-10-08 17:25 UTCEG score recompute
  24. 2026-10-08 17:25 UTCVendor advisory
  25. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-10-08 05:02 UTCEG score recompute
  27. 2026-10-08 05:02 UTCVendor advisory
  28. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-10-07 18:00 UTCVendor advisory
  30. 2026-10-07 04:28 UTCVendor advisory
  31. 2026-10-06 17:26 UTCEG score recompute
  32. 2026-10-06 17:26 UTCVendor advisory
  33. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  34. 2026-10-06 06:25 UTCVendor advisory
  35. 2026-10-05 19:23 UTCEG score recompute
  36. 2026-10-05 19:23 UTCVendor advisory
  37. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  38. 2026-10-05 08:22 UTCEG score recompute
  39. 2026-10-05 08:22 UTCVendor advisory
  40. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  41. 2026-10-04 21:21 UTCVendor advisory
  42. 2026-10-04 10:20 UTCVendor advisory
  43. 2026-10-03 23:18 UTCEG score recompute
  44. 2026-10-03 23:18 UTCVendor advisory
  45. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  46. 2026-10-03 12:14 UTCVendor advisory
  47. 2026-10-03 01:13 UTCEG score recompute
  48. 2026-10-03 01:13 UTCVendor advisory
  49. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-10-02 14:12 UTCVendor advisory
  51. 2026-10-02 03:10 UTCEG score recompute
  52. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-09-30 17:49 UTCEG score recompute
  54. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-09-30 00:25 UTCEG score recompute
  56. 2026-09-29 00:47 UTCEG score recompute
  57. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  58. 2026-09-27 15:42 UTCEG score recompute
  59. 2026-09-26 17:36 UTCEG score recompute
  60. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  61. 2026-09-26 06:33 UTCEG score recompute
  62. 2026-09-24 21:24 UTCEG score recompute
  63. 2026-09-24 21:12 UTCEG score recompute
  64. 2026-09-24 18:01 UTCEG score recompute
  65. 2026-09-23 19:42 UTCEG score recompute
  66. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  67. 2026-09-22 21:40 UTCEG score recompute
  68. 2026-09-21 23:36 UTCEG score recompute
  69. 2026-09-21 01:34 UTCEG score recompute
  70. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  71. 2026-09-19 16:30 UTCEG score recompute
  72. 2026-09-18 18:27 UTCEG score recompute
  73. 2026-09-18 17:44 UTCEG score recomputeFirst assessed: 8.3 HIGH
  74. 2026-09-18 17:44 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Same product

2 shown

Go:github.com/perses/perses

Frequently asked(5)

What is CVE-2026-63199?
CVE-2026-63199 is a high-severity vulnerability; its CVE record was published on September 18, 2026. Perses is an open-source dashboard and visualization project for observability data. From 0.43.0 until 0.54.0-rc.0, the datasource creation and unsaved datasource proxy paths authorize the caller on a Datasource or GlobalDatasource scope but do not require read permission for the separately…
When was the CVE record for CVE-2026-63199 published?
The CVE record for CVE-2026-63199 was published on September 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-63199 actively exploited?
CVE-2026-63199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63199?
CVE-2026-63199 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63199?
A fix for CVE-2026-63199 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63199 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63199?

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

Book a Demo →Browse All CVEs