CVE-2026-97063

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-25. A secondary CVSS source baseline 9.1; sources differ by 0.0.

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

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

X-SpringBoot through 6.0 returns login verification codes in HTTP responses from unauthenticated endpoints GET /sys/mobile/code and GET /sys/email/code without sending them to account owners. Attackers can request codes using known mobile numbers or email addresses, read them from responses, and authenticate as victims via POST /sys/emailOrMobileLogin/login to hijack accounts.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
72
EG Risk 72/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
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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
19th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

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 total (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 25, 2026

Last Modified

September 28, 2026

Advisory Details (4)

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

X-SpringBoot through 6.0 Authentication Bypass via Login Code | Advisories | VulnCheck

https://www.vulncheck.com/advisories/x-springboot-through-6.0-authentication-bypass-via-login-code
generic

GitHub - yzcheng90/x-springboot: X-SpringBoot是一个轻量级的Java快速开发平台，基于springboot3和jdk21，使用虚拟线程，可配置的SaaS功能具备RBAC功能、自动代码生成、多种存储系统，多种短信平台，可开放api授权。代码简洁，架构清晰，能快速开发项目并交付【接私活利器】 · GitHub

https://github.com/yzcheng90/X-SpringBoot
generic

x-springboot/src/main/java/com/suke/czx/modules/sys/controller/SysLoginController.java at d74ddba989c0449948ff1ddb0d211b6a7ce81bfa · yzcheng90/x-springboot · GitHub

https://github.com/yzcheng90/X-SpringBoot/blob/d74ddba989c0449948ff1ddb0d211b6a7ce81bfa/src/main/java/com/suke/czx/modules/sys/controller/SysLoginController.java#L94-L134
generic

cve-request-poc/x-springboot/02_sms-code-account-takeover.py at master · LinYuanyi1/cve-request-poc · GitHub

https://github.com/LinYuanyi1/cve-request-poc/blob/master/x-springboot/02_sms-code-account-takeover.py

Vendor Advisories for CVE-2026-97063(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 60× in last 7d / 78× 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-04 11:00 UTCGHSA enrichment
  2. 2026-10-04 07:20 UTCGHSA enrichment
  3. 2026-10-04 03:39 UTCGHSA enrichment
  4. 2026-10-03 23:59 UTCGHSA enrichment
  5. 2026-10-03 20:18 UTCGHSA enrichment
  6. 2026-10-03 16:36 UTCEG score recompute
  7. 2026-10-03 16:36 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 12:55 UTCGHSA enrichment
  10. 2026-10-03 09:14 UTCGHSA enrichment
  11. 2026-10-03 05:30 UTCGHSA enrichment
  12. 2026-10-03 01:49 UTCGHSA enrichment
  13. 2026-10-02 22:08 UTCGHSA enrichment
  14. 2026-10-02 18:27 UTCEG score recompute
  15. 2026-10-02 18:27 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 14:47 UTCGHSA enrichment
  18. 2026-10-02 11:06 UTCGHSA enrichment
  19. 2026-10-02 07:25 UTCGHSA enrichment
  20. 2026-10-02 03:44 UTCGHSA enrichment
  21. 2026-10-02 00:03 UTCGHSA enrichment
  22. 2026-10-01 20:01 UTCEG score recompute
  23. 2026-10-01 20:01 UTCGHSA enrichment
  24. 2026-10-01 19:51 UTCEPSS rescore
  25. 2026-10-01 16:20 UTCGHSA enrichment
Show 53 more
  1. 2026-10-01 12:40 UTCGHSA enrichment
  2. 2026-10-01 08:59 UTCGHSA enrichment
  3. 2026-10-01 05:18 UTCGHSA enrichment
  4. 2026-10-01 01:38 UTCGHSA enrichment
  5. 2026-09-30 21:57 UTCGHSA enrichment
  6. 2026-09-30 18:17 UTCEG score recompute
  7. 2026-09-30 18:17 UTCGHSA enrichment
  8. 2026-09-30 15:04 UTCEPSS rescore
  9. 2026-09-30 14:36 UTCGHSA enrichment
  10. 2026-09-30 10:55 UTCGHSA enrichment
  11. 2026-09-30 07:10 UTCGHSA enrichment
  12. 2026-09-30 03:29 UTCGHSA enrichment
  13. 2026-09-29 23:49 UTCGHSA enrichment
  14. 2026-09-29 19:27 UTCGHSA enrichment
  15. 2026-09-29 15:39 UTCEG score recompute
  16. 2026-09-29 15:39 UTCGHSA enrichment
  17. 2026-09-29 11:59 UTCGHSA enrichment
  18. 2026-09-29 08:15 UTCGHSA enrichment
  19. 2026-09-29 04:35 UTCGHSA enrichment
  20. 2026-09-29 00:54 UTCEG score recompute
  21. 2026-09-29 00:54 UTCGHSA enrichment
  22. 2026-09-28 21:14 UTCGHSA enrichment
  23. 2026-09-28 17:46 UTCGHSA enrichment
  24. 2026-09-28 14:01 UTCEG score recompute
  25. 2026-09-28 14:01 UTCGHSA enrichment
  26. 2026-09-28 13:52 UTCEPSS rescore
  27. 2026-09-28 13:52 UTCEPSS rescore
  28. 2026-09-28 10:20 UTCGHSA enrichment
  29. 2026-09-28 06:39 UTCGHSA enrichment
  30. 2026-09-28 02:58 UTCGHSA enrichment
  31. 2026-09-27 23:15 UTCGHSA enrichment
  32. 2026-09-27 19:35 UTCGHSA enrichment
  33. 2026-09-27 15:54 UTCEG score recompute
  34. 2026-09-27 15:54 UTCGHSA enrichment
  35. 2026-09-27 13:49 UTCEPSS rescore
  36. 2026-09-27 12:14 UTCGHSA enrichment
  37. 2026-09-27 08:34 UTCGHSA enrichment
  38. 2026-09-27 04:53 UTCGHSA enrichment
  39. 2026-09-27 01:10 UTCGHSA enrichment
  40. 2026-09-26 21:26 UTCGHSA enrichment
  41. 2026-09-26 17:46 UTCEG score recompute
  42. 2026-09-26 17:45 UTCGHSA enrichment
  43. 2026-09-26 15:59 UTCEPSS rescore
  44. 2026-09-26 14:02 UTCGHSA enrichment
  45. 2026-09-26 10:22 UTCGHSA enrichment
  46. 2026-09-26 06:40 UTCGHSA enrichment
  47. 2026-09-26 03:00 UTCGHSA enrichment
  48. 2026-09-25 23:15 UTCEG score recompute
  49. 2026-09-25 23:15 UTCGHSA enrichment
  50. 2026-09-25 19:34 UTCEG score recompute
  51. 2026-09-25 18:45 UTCEG score recompute
  52. 2026-09-25 18:33 UTCEG score recompute
  53. 2026-09-25 18:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-97063?
CVE-2026-97063 is a critical vulnerability published on September 25, 2026. X-SpringBoot through 6.0 returns login verification codes in HTTP responses from unauthenticated endpoints GET /sys/mobile/code and GET /sys/email/code without sending them to account owners. Attackers can request codes using known mobile numbers or email addresses, read them from responses, and…
When was CVE-2026-97063 disclosed?
CVE-2026-97063 was first published on September 25, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97063 actively exploited?
CVE-2026-97063 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97063?
CVE-2026-97063 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97063?
No fix for CVE-2026-97063 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-97063 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-97063?

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

Book a Demo →Browse All CVEs