Xerj Console API: Authentication bypass via bearer tokens
Summary
The Xerj Console API accepts API bearer tokens where it should require a passkey-authenticated session. An attacker holding one valid token can call the API-token creation endpoint and mint successor tokens that remain valid after the original token is revoked. If the original token belongs to an account owner, the successor keeps full administrative rights. Exploitation requires a valid token first.
Affected
- Xerj Console API v1.0.0-rc.11 (listed in the CVE record)
- Earlier and later versions: Unknown.
Fixed in
- No released version with the fix is known. The first fixed version is Unknown.
- A fix exists as pull request #2003 on the main branch. Its merge date is unverified.
- The fix does not revoke tokens, passkeys or invitations created before the upgrade.
Workaround
- No vendor-validated workaround is available.
- Generic suggestion: enforce passkey authentication for all bearer-token requests.
- Restrict network access to the console to trusted networks only.
Exploitation
- CERT/CC reports no exploitation in the wild.
- VulDB reports no known exploit. The vulnerability is not on CISA's KEV list.
- No public proof of concept was found.
Our recommendation
- Check whether Xerj is in use and confirm the installed version.
- Limit console access to trusted networks now.
- Audit all API tokens, enrolled passkeys and issued invitations, and revoke unknown ones.
- Track pull request #2003 and the CERT/CC note, and install the first fixed release.
- Note: the CVSS score is disputed (CVE record 9.1, VulDB 7.3, Vulners 5.8). Verify it against NVD or CERT/CC before reporting it.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- CERT/CC Vulnerability Note VU#645818 kb.cert.org
- GitHub Pull Request #2003 (xerj-org/xerj) github.com
- GitHub Issue #2020 (xerj-org/xerj) github.com
- OpenCVE: CVE-2026-97406 app.opencve.io
- VulDB: vuln 422961 vuldb.com
- Strix: CVE-2026-97406 www.strix.ai
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 06:14.
Original description (NVD)
XERJ Console API bearer tokens can bypass the passkey‑only authentication requirement and directly invoke the API‑token creation endpoint, allowing unauthorized minting of persistent successor credentials.
NVD references (2)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.