CVE-2026-97326

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-09-24. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.3Exploit: Elevated riskExposed services: Not assessed

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

A weakness has been identified in songxinjianqwe Chat up to ac63d25297079eed5e4ba7e88d3b7a032637150d. Affected by this issue is some unknown functionality of the file chat-server/src/main/java/cn/sinjinsong/chat/server/ChatServer.java of the component chat-server. This manipulation causes server-side request forgery. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
7.3
EG Score
7.3HIGHhigh confidence
EG Risk
64
EG Risk 64/100CISA SSVC

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
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

September 25, 2026

Advisory Details (1)

Auto-updated Sep 24, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Chat-master-cve · Issue #1 · HazyX0/cve · GitHub

https://github.com/HazyX0/cve/issues/1

Vendor Advisories for CVE-2026-97326(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 52× 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-10-05 01:37 UTCEG score recompute
  2. 2026-10-05 01:37 UTCGHSA enrichment
  3. 2026-10-04 23:23 UTCEPSS rescore
  4. 2026-10-04 14:33 UTCGHSA enrichment
  5. 2026-10-04 03:29 UTCGHSA enrichment
  6. 2026-10-03 16:25 UTCEG score recompute
  7. 2026-10-03 16:25 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 05:22 UTCGHSA enrichment
  10. 2026-10-02 18:18 UTCEG score recompute
  11. 2026-10-02 18:18 UTCGHSA enrichment
  12. 2026-10-02 18:18 UTCGHSA enrichment
  13. 2026-10-02 17:57 UTCEPSS rescore
  14. 2026-10-02 07:14 UTCGHSA enrichment
  15. 2026-10-01 20:10 UTCEG score recompute
  16. 2026-10-01 20:10 UTCGHSA enrichment
  17. 2026-10-01 19:51 UTCEPSS rescore
  18. 2026-10-01 09:07 UTCGHSA enrichment
  19. 2026-09-30 22:03 UTCEG score recompute
  20. 2026-09-30 22:03 UTCGHSA enrichment
  21. 2026-09-30 15:04 UTCEPSS rescore
  22. 2026-09-30 10:59 UTCGHSA enrichment
  23. 2026-09-29 23:53 UTCEG score recompute
  24. 2026-09-29 23:52 UTCGHSA enrichment
  25. 2026-09-29 11:19 UTCGHSA enrichment
Show 27 more
  1. 2026-09-29 00:11 UTCEG score recompute
  2. 2026-09-29 00:11 UTCGHSA enrichment
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 13:52 UTCEPSS rescore
  5. 2026-09-28 13:08 UTCGHSA enrichment
  6. 2026-09-28 02:03 UTCGHSA enrichment
  7. 2026-09-27 14:59 UTCEG score recompute
  8. 2026-09-27 14:59 UTCGHSA enrichment
  9. 2026-09-27 13:49 UTCEPSS rescore
  10. 2026-09-27 03:53 UTCGHSA enrichment
  11. 2026-09-26 16:48 UTCEG score recompute
  12. 2026-09-26 16:48 UTCGHSA enrichment
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-26 05:45 UTCEG score recompute
  15. 2026-09-26 05:45 UTCGHSA enrichment
  16. 2026-09-25 18:40 UTCEG score recompute
  17. 2026-09-25 18:40 UTCGHSA enrichment
  18. 2026-09-25 18:30 UTCNVD updateCVSS v4 → 5.5
  19. 2026-09-25 17:19 UTCEG score recompute
  20. 2026-09-25 17:19 UTCGHSA enrichment
  21. 2026-09-25 17:19 UTCMITRE cvelistV5CVSS v4 → 6.9
  22. 2026-09-25 08:20 UTCEG score recompute
  23. 2026-09-25 08:20 UTCGHSA enrichment
  24. 2026-09-24 20:20 UTCEG score recompute
  25. 2026-09-24 20:19 UTCNVD updateCVSS v4 → 5.5
  26. 2026-09-24 19:52 UTCEG score recompute
  27. 2026-09-24 19:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97326?
CVE-2026-97326 is a high vulnerability published on September 24, 2026. A weakness has been identified in songxinjianqwe Chat up to ac63d25297079eed5e4ba7e88d3b7a032637150d. Affected by this issue is some unknown functionality of the file chat-server/src/main/java/cn/sinjinsong/chat/server/ChatServer.java of the component chat-server. This manipulation causes…
When was CVE-2026-97326 disclosed?
CVE-2026-97326 was first published on September 24, 2026, with the most recent update on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97326 actively exploited?
CVE-2026-97326 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-97326?
CVE-2026-97326 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97326?
No fix for CVE-2026-97326 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97326 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-97326?

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