# CVE-2026-92918: admin3 session token disclosure in audit log

Source: https://junglewise.ai/threats/cve-2026-92918-admin3-session-token-disclosure-in-audit-log  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-17. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-92918 · Severity: high · CVSS 8.8 · Published 2026-09-17

admin3 is a lightweight admin framework written in Java and Spring Boot. A vulnerability causes user session tokens to be stored unprotected in audit logs. Any user with log-viewing permission can access these tokens and replay them to impersonate other users, potentially gaining unauthorized administrative access to the system.

## Quick answers

**Is CVE-2026-92918 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92918 being exploited in the wild.

**How severe is CVE-2026-92918?** High severity, with a CVSS score of 8.8, published 17 September 2026.

**Which products and versions are affected?** admin3 admin3 through 3.0.0.

**Is there a fix for CVE-2026-92918?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-92918 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-92918?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an information disclosure flaw in the audit logging subsystem. When admin3 publishes UserLoggedIn domain events, it persists the full UserinfoDTO—including active session tokens—in the audit log event body. The GET /logs endpoint returns these events as raw JSON in the eventBody field, accessible to any user holding the log:view permission. An attacker can harvest valid session tokens from the logs and replay them as Bearer credentials in the Authorization header, bypassing authentication and assuming the privileges of the victim user. No authentication or special network access is required beyond the log:view permission.

## Affected products

- admin3 admin3 through 3.0.0

## Timeline

- 2026-09-17: disclosed

## References

- [https://github.com/LinYuanyi1/cve-request-poc/blob/master/admin3/C02_log_session_token_disclosure.py](https://github.com/LinYuanyi1/cve-request-poc/blob/master/admin3/C02_log_session_token_disclosure.py)
- [https://github.com/cjbi/admin3](https://github.com/cjbi/admin3)