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

> Attackers with log access can steal session tokens from audit logs to hijack user accounts in the admin3 application.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-f5hf-9xjh-p8xq

## What is CVE-2026-92918?

CVE-2026-92918 is a high-severity vulnerability in cjbi admin3, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-92918?


## How do I fix CVE-2026-92918?

No fix has been published for CVE-2026-92918 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92918 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92918 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92918 and fix it if it is affected.

What it is: CVE-2026-92918 is a high-severity vulnerability in cjbi admin3, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92918 exists.

Affected product: cjbi admin3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92918/ (Markdown: https://insights.sbomify.com/CVE-2026-92918/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92918
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92918
- OSV: https://osv.dev/vulnerability/CVE-2026-92918

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92918/
Summaries are generated and may contain mistakes; the official description above is the record.