Skip to main content

VU#645818: Xerj Console API Authentication Bypass Leads to Unauthorized Credential Minting

0
High
Published: 10/20/2026 (10/20/2026, 18:09:44 UTC)
Source: CERT/CC

Description

An authentication bypass vulnerability in the Xerj Console API allows attackers with a valid token to create successor API tokens without passkey authentication. This flaw enables persistent unauthorized access and privilege escalation within the Xerj system, even if the original token is revoked. The vulnerability arises from the Xerj system treating browser sessions and API tokens identically without verifying passkey-backed authentication during token issuance. No official patch is currently available, and the vendor has not provided a statement.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/20/2026, 18:20:07 UTC

Technical Analysis

CVE-2026-97406 is an authentication bypass vulnerability in the Xerj Console API. Xerj converts both browser sessions and API bearer tokens into a generic AuthSession object, and the token creation handler does not verify if the session was authenticated via a passkey as required by the security contract. Consequently, an attacker possessing a valid Xerj API token can invoke the token creation endpoint to mint independent successor credentials with the same privileges as the original token. The platform lacks hierarchical revocation logic, so revoking the parent token does not invalidate descendant tokens. This architectural flaw allows attackers to maintain persistent access, bypass multi-factor authentication controls, and escalate privileges, including gaining administrative control and enrolling attacker-controlled passkeys.

Potential Impact

Exploitation allows persistent unauthorized access that bypasses multi-factor authentication. If the compromised token belongs to an account owner, the attacker can gain full administrative privileges, issue new account invitations, and enroll attacker-controlled passkeys. This results in permanent control over the Xerj instance and its sensitive data indices. Token revocation does not mitigate the threat due to the lack of hierarchical revocation logic.

Mitigation Recommendations

No official patch or vendor advisory is currently available. Users should monitor the Xerj project's GitHub repository for updates and apply the latest version once a fix is released. Until then, no direct mitigation is confirmed.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Classification
{"confidence":0.95,"severitySource":"heuristic","classifier":"rss-v2"}
Article Source
{"url":"https://kb.cert.org/vuls/id/645818","fetched":true,"fetchedAt":"2026-10-20T18:20:00.721Z","wordCount":590}

Threat ID: 6ad7b0d02cdf04f6564e4bb1

Added to database: 10/20/2026, 18:20:00 UTC

Last enriched: 10/20/2026, 18:20:07 UTC

Last updated: 10/21/2026, 00:19:02 UTC

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses