CVE-2026-63647

CRITICALPre-NVD 9.39.3
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
Elevated
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.3Exploit: Elevated riskExposed: 0

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

CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. Prior to 1.7.2, SseController exposes the anonymous /sse/subscribe, /sse/broadcast, and /sse/close endpoints because ShiroFilter.addPublicPathFilters permits the SSE paths, and the endpoints trust the caller-controlled userId instead of deriving an identity from an authenticated principal. An unauthenticated caller can use /sse/subscribe to read another user's workflow events, approval requests, mentions, and alerts, use /sse/broadcast to inject SYSTEM_HEARTBEAT messages into another user's stream, or use /sse/close to terminate another user's channel. This vulnerability is fixed in 1.7.2.

CVSS v3
9.3
EG Score
9.3(low)
EG Risk
73(Attend)
EG Risk 73/100SSVC: Attend

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
Severity93% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v1.7.2

Patch available: 1Panel-dev/CordysCRM v1.7.2

https://github.com/1Panel-dev/CordysCRM/releases/tag/v1.7.2
github_commit Patch Available

commit 6cb81deb5343 (1Panel-dev/CordysCRM)

Patch available: 1Panel-dev/CordysCRM v1.7.2 (contains commit 6cb81deb5343)

https://github.com/1Panel-dev/CordysCRM/commit/6cb81deb53434ae7792673c50312ff91685d7f9d
github_pr Patch Available

fix: Remove broadcast endpoint and filter out default admin user in client addition

Patch available: 1Panel-dev/CordysCRM v1.7.2 (PR #2719 merged 2026-06-17)

https://github.com/1Panel-dev/CordysCRM/pull/2719
github Patch Available🟡 PoC Available

CordysCRM SSE Notification Stream Hijack via `/sse/subscribe` · Advisory · 1Panel-dev/CordysCRM · GitHub

https://github.com/1Panel-dev/CordysCRM/security/advisories/GHSA-9qg8-cm35-xqp4

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 5× 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-19 01:36 UTCEG score recompute
  2. 2026-09-18 21:17 UTCEG score recompute
  3. 2026-09-18 20:26 UTCEG score recompute
  4. 2026-09-18 19:59 UTCEG score recompute
  5. 2026-09-18 19:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-63647?
CVE-2026-63647 is a critical vulnerability published on September 18, 2026. CordysCRM is an open source AI-powered customer relationship management system that supports private deployment. Prior to 1.7.2, SseController exposes the anonymous /sse/subscribe, /sse/broadcast, and /sse/close endpoints because ShiroFilter.addPublicPathFilters permits the SSE paths, and the…
When was CVE-2026-63647 disclosed?
CVE-2026-63647 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-63647?
CVE-2026-63647 has a CVSS v3 base score of 9.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-63647?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63647, 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

Explore the affected products and dependency analysis for CVE-2026-63647

Explore →

Is Your Infrastructure Affected by CVE-2026-63647?

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

Start Free Scan →Browse All CVEs