CVE-2026-92918

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

admin3 through 3.0.0 persists user session tokens in the audit log event body when publishing UserLoggedIn domain events. Attackers with log:view permission can read the JSON response from the GET /logs endpoint to harvest session tokens and replay them as bearer credentials for full user access.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (6)

Auto-updated Sep 17, 2026
No patch confirmed yet.
generic

admin3 through 3.0.0 Session Token Disclosure via Audit Log | Advisories | VulnCheck

https://www.vulncheck.com/advisories/admin3-through-3.0.0-session-token-disclosure-via-audit-log
generic

GitHub - cjbi/admin3: 一个轻巧的后台管理框架，项目后端基于Java21、SpringBoot3.2，前端基于TypeScript、Vite3、Vue3、Element Plus，只提供登录会话、用户管理、角色管理、权限资源管理、事件日志、对象存储等基础功能的最佳实践方案，不做过多的封装，适合二次定制开发、接私活、源码学习等场景 · GitHub

https://github.com/cjbi/admin3
generic

admin3/admin3-server/src/main/resources/data.sql at 3.0.0 · cjbi/admin3 · GitHub

https://github.com/cjbi/admin3/blob/3.0.0/admin3-server/src/main/resources/data.sql
generic

admin3/admin3-server/src/main/java/tech/wetech/admin3/infra/service/DefaultSessionService.java at 3.0.0 · cjbi/admin3 · GitHub

https://github.com/cjbi/admin3/blob/3.0.0/admin3-server/src/main/java/tech/wetech/admin3/infra/service/DefaultSessionService.java
generic

admin3/admin3-server/src/main/java/tech/wetech/admin3/sys/service/LogService.java at 3.0.0 · cjbi/admin3 · GitHub

https://github.com/cjbi/admin3/blob/3.0.0/admin3-server/src/main/java/tech/wetech/admin3/sys/service/LogService.java
generic

cve-request-poc/admin3/C02_log_session_token_disclosure.py at master · LinYuanyi1/cve-request-poc · GitHub

https://github.com/LinYuanyi1/cve-request-poc/blob/master/admin3/C02_log_session_token_disclosure.py

Vendor Advisories for CVE-2026-92918(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 13× in last 7d / 13× 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-20 13:07 UTCGHSA enrichment
  2. 2026-09-20 01:07 UTCEG score recompute
  3. 2026-09-20 01:07 UTCGHSA enrichment
  4. 2026-09-19 13:10 UTCGHSA enrichment
  5. 2026-09-19 01:13 UTCEG score recompute
  6. 2026-09-19 01:12 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 13:15 UTCGHSA enrichment
  9. 2026-09-18 01:18 UTCEG score recompute
  10. 2026-09-18 01:18 UTCGHSA enrichment
  11. 2026-09-17 13:21 UTCEG score recompute
  12. 2026-09-17 12:36 UTCEG score recompute
  13. 2026-09-17 12:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92918?
CVE-2026-92918 is a high vulnerability published on September 17, 2026. admin3 through 3.0.0 persists user session tokens in the audit log event body when publishing UserLoggedIn domain events. Attackers with log:view permission can read the JSON response from the GET /logs endpoint to harvest session tokens and replay them as bearer credentials for full user access.
When was CVE-2026-92918 disclosed?
CVE-2026-92918 was first published in the National Vulnerability Database on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92918 actively exploited?
CVE-2026-92918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.8% of all scored CVEs.
What is the CVSS score of CVE-2026-92918?
CVE-2026-92918 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-92918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92918, 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-92918

Explore →

Is Your Infrastructure Affected by CVE-2026-92918?

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

Start Free Scan →Browse All CVEs