XERJ Console API bearer tokens can bypass the passkey‑only authentication requirement and directly invoke the
Source GCVE Database
Not known to be exploited · CVSS 9.1 Critical.
Data as of 29 Oct 2026, 20:14 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 9.1 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| XerjConsole API | Affected
| Fixed in– |
AI-suggested
Since this is not a cloud service, remediation responsibility lies with the vendor or system administrators. Users should monitor vendor advisories for updates and apply any forthcoming patches promptly. Until a fix is available, restricting bearer token usage and enforcing strict access controls around the API-token creation endpoint is recommended.
Description
A vulnerability in the XERJ Console API allows bearer tokens to bypass the passkey-only authentication requirement. This flaw enables unauthorized users to directly invoke the API-token creation endpoint and mint persistent successor credentials without proper authentication.