CVE-2026-92918: admin3 through 3.0.0 Session Token Disclosure via Audit Log

Published Sep 17, 2026
·
Updated

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.

Affected Software

1 affected component
admin3>0<=3.0.0

Event History

Sep 17, 2026
CVE Published
via MITRE·12:33 PM
Data Sourced
via MITRE·12:33 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs an account or other access that grants the log:view permission. They can retrieve audit log data from the GET /logs endpoint and extract session tokens from UserLoggedIn event bodies.

2

What level of access can a stolen token provide?

The disclosed session tokens can be replayed as bearer credentials for full access as the user whose token was harvested.

3

How can I determine whether tokens may already have been exposed?

Review access to the GET /logs endpoint by principals with log:view permission and inspect audit log entries for UserLoggedIn events whose JSON bodies contain session tokens. Any such tokens should be treated as compromised because authorized log viewers could have read them.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203