Xerj Console API bypass lets token holders mint credentials
Original title: VU#645818: Xerj Console API Authentication Bypass Leads to Unauthorized Credential Minting
CVE-2026-97406 lets a valid API token spawn persistent successor credentials that survive parent-token revocation; no patch is available.
CERT/CC published VU#645818 on an authentication bypass in the Xerj Console API, tracked as CVE-2026-97406. An attacker with a valid API token can create independent successor credentials because token issuance does not check that the session was passkey-backed, and revoking the parent token does not revoke descendants. If the token belongs to an account owner, the attacker can enroll an attacker-controlled passkey and keep administrative access. The vendor could not be reached, and no official patch was available when the note was published on October 20.
Unconfirmed: No exploitation in the wild is stated, and the vendor had not confirmed a patch.
- Xerj is an open-source search and indexing engine for AI agents.
- Both browser sessions and API bearer tokens become the same AuthSession object.
- An owner token can be used to invite and enroll an attacker passkey.
- Users are told to watch the project's GitHub and install a fix when released.
- The note credits reporter Shiran Guez.
Impact: Persistent admin access that survives token revocation
| Product | Affected |
|---|---|
| Xerj Console API | — |
- 1.Monitor the Xerj GitHub repository for a fix.
- 2.Install the latest library version once a fix is released.
- CVEs
- CVE-2026-97406
- Vendors
- Xerj
- Products
- Xerj Console API
- Organizations
- CERT/CC
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-97406 | XERJ Console API bearer tokens can bypass the passkey‑only authentication requirement and directly invoke the API‑token creation endpoint, allowing… | 9.1 | — |
From the original article
2 min read at kb.cert.orgOverview An authentication bypass vulnerability in the Xerj Console API allows sessions to bypass passkey-backed requirements during token issuance. By exploiting this flaw, an attacker with an existing valid token can create independent, persistent successor credentials directly through the console API.
kb.cert.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.