Description
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.
Published: 2026-10-20
Score: n/a
EPSS: n/a
KEV: No
Impact: Unauthorized Credential Creation
Action: Apply Patch
AI Analysis

Impact

The vulnerability allows an attacker to use a bearer token to bypass the passkey‑only authentication requirement of the Xerj Console API. By doing so, an unauthenticated or minimally privileged user can directly invoke the token‑creation endpoint and mint persistent API tokens. This effectively grants the attacker a long‑lived credential that can be used for further requests, enabling unauthorized access and potential lateral movement within systems that rely on those tokens for authentication.

Affected Systems

The affected product is Xerj Console API. No specific version numbers are listed in the publicly available data, so all deployed instances of this API may be susceptible unless vendor documentation specifies otherwise.

Risk and Exploitability

The CVE entry does not provide an EPSS score or a CVSS rating, and this vulnerability is not listed in the CISA KEV catalog. The exploit appears to be achievable via the publicly exposed API endpoint using a standard bearer token, which suggests a remote exploitation path over the network. Because the vulnerability can lead to the creation of new, persistent credentials, the potential impact is high; however, without an explicit CVSS score or exploit prevalence data, the exact level of risk cannot be quantified precisely.

Generated by OpenCVE AI on October 20, 2026 at 19:37 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Check the Xerj vendor website for the latest release notes and apply any available security patch that addresses the authentication bypass in the Console API.
  • Configure the API to enforce passkey authentication for all bearer token requests, ensuring that even legitimate tokens cannot grant token‑creation privileges without proper authentication.
  • Restrict or disable the API‑token creation endpoint for untrusted users, applying strict role‑based access controls so that only authorized administrators can mint new tokens.
  • Monitor API traffic for anomalous token‑minting activity and investigate any unexpected token creation events promptly.

Generated by OpenCVE AI on October 20, 2026 at 19:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 20 Oct 2026 20:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-287

Tue, 20 Oct 2026 19:30:00 +0000

Type Values Removed Values Added
References

Tue, 20 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Authentication Bypass via Bearer Tokens to Unauthorized Credential Minting
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: certcc

Published:

Updated: 2026-10-20T19:07:07.888Z

Reserved: 2026-09-24T14:49:55.504Z

Link: CVE-2026-97406

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-10-20T19:19:38.900

Modified: 2026-10-20T19:30:59.910

Link: CVE-2026-97406

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-20T19:45:13Z

Weaknesses