Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97406 Overview
CVE-2026-97406 is an authentication bypass vulnerability in the XERJ Console API. The flaw allows bearer tokens to circumvent the passkey-only authentication requirement enforced on sensitive endpoints. An attacker holding a valid bearer token can directly invoke the API-token creation endpoint and mint persistent successor credentials without completing passkey verification.
Because the newly minted tokens persist beyond the original bearer token's lifecycle, an attacker can establish durable, unauthorized access to the Console API. This undermines the passkey control intended to gate privileged credential issuance.
Critical Impact
An attacker with a valid API bearer token can bypass passkey enforcement and generate persistent API tokens, enabling long-term unauthorized access to the XERJ Console API.
Affected Products
- XERJ Console API (specific versions not disclosed in NVD at time of publication)
- Deployments relying on the passkey-only authentication control for API token issuance
- Environments where API bearer tokens have been issued to users or services
Discovery Timeline
- 2026-10-20 - CVE-2026-97406 published to the National Vulnerability Database
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-97406
Vulnerability Analysis
The XERJ Console API enforces a passkey-only authentication policy on endpoints that issue new API tokens. This control is intended to ensure that only an interactively authenticated user with a registered passkey can mint new credentials. The vulnerability stems from the API accepting bearer tokens as a valid authentication method on the token creation endpoint, despite the policy requirement.
An attacker who possesses a bearer token—whether obtained through legitimate issuance, theft, interception, or reuse—can submit it to the token creation endpoint. The endpoint processes the request and returns a new persistent API token. The newly issued token functions as a successor credential and continues to operate independently of the original bearer token's revocation state.
This defect falls under Authentication Bypass and Broken Access Control categories. It also exhibits characteristics of a business logic flaw, because the authentication policy is defined but not consistently enforced across the API surface.
Root Cause
The root cause is inconsistent enforcement of the passkey authentication requirement within the API authorization middleware. The endpoint handling API-token creation evaluates bearer token presence as sufficient authentication, bypassing the passkey step-up check. The authorization layer does not validate that the current session was established through a passkey challenge before permitting credential-minting operations.
Attack Vector
An attacker requires a valid bearer token to exploit CVE-2026-97406. With that token, the attacker issues an authenticated request to the API-token creation endpoint. The API returns a persistent token controlled by the attacker. The attacker then uses the successor token to maintain access, even if the original bearer token is rotated or revoked. This produces a credential-persistence primitive useful for long-term account takeover and privilege retention.
For exploitation specifics, refer to the CERT Vulnerability Report #645818.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-97406
Indicators of Compromise
- API-token creation requests authenticated with a bearer token rather than a passkey-backed session
- Unexpected creation of long-lived API tokens associated with user or service accounts
- API tokens issued outside of normal administrative workflows or change windows
- Successor tokens observed in use after the parent bearer token has been rotated or revoked
Detection Strategies
- Audit API-token creation logs and correlate each event with the authentication method used in the originating session
- Flag any token issuance where the session authenticator is not a passkey assertion
- Compare token issuance activity against identity provider passkey challenge records to identify mismatches
Monitoring Recommendations
- Alert on API-token creation events that occur outside approved administrative accounts or hours
- Track newly issued tokens by lifetime, scope, and first-use source IP to surface anomalous persistence
- Forward Console API audit logs to a centralized analytics platform for retention and correlation with endpoint and identity telemetry
How to Mitigate CVE-2026-97406
Immediate Actions Required
- Revoke all active bearer tokens and require re-issuance under current controls
- Audit existing API tokens and remove any that cannot be attributed to a legitimate passkey-authenticated session
- Restrict access to the API-token creation endpoint at the network or gateway layer until a vendor fix is applied
- Rotate credentials for any accounts or services whose bearer tokens may have been exposed
Patch Information
No vendor patch information is available in the NVD record at time of publication. Monitor the CERT Vulnerability Report #645818 for updates on fixed versions and vendor advisories.
Workarounds
- Enforce passkey authentication at an upstream reverse proxy or API gateway for all token-creation endpoints
- Disable or restrict bearer token acceptance on sensitive administrative routes until the vulnerability is remediated
- Reduce the lifetime of issued API tokens and require frequent reissuance to limit persistence of unauthorized successor credentials
- Apply allowlists so that only designated administrative source networks can reach the token creation endpoint
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

