CVE-2026-109861
8.7HighPublished 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v4.010
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- High impact on confidentiality
- Weakness
- CWE-798
What an attacker gets
Unauthenticated attackers can enumerate users and steal API token hashes by reusing a hardcoded token. They need access to the application package, logs, or configuration files to extract the token.
Root cause
The auth-service.jar contains a hardcoded authentication token within the KeyCloakController class.
Affected versions
- CAST Imaging version
3.6.2 - other versions may be affected
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade to the latest version provided by CAST. Immediately restrict network access to the auth-service endpoints and rotate any API tokens that may have been exposed.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
CAST Imaging contains a hardcoded authentication token in the "KeyCloakController" class of auth-service.jar. An attacker who gains access to the source code, application package, logs, or configuration files can reuse this token to call auth-service endpoints without authentication. Using the token with the "/api/auth/keycloak/users" endpoint, the attacker can enumerate users across Keycloak realms and retrieve user attributes containing API token hashes, enabling reconnaissance and further exploitation. The vulnerability has only been confirmed in version 3.6.2 but may also affect other versions. The vendor did not provide the affected version range, but assured that the vulnerability is fixed "in newer versions".