Skip to main content
VulnerabilityPublished

CVE-2026-109861: CAST Software Imaging · Use of Hard-coded Credentials

Affects CAST Software ImagingSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High.

Data as of 18 Nov 2026, 12:37 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CERT-PL)CVSS 4.08.7
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
CAST SoftwareImagingAffected
  • =3.6.2
Fixed in–

AI-suggested

The vendor has confirmed that the vulnerability is fixed in newer versions of CAST Imaging. Users should upgrade to the latest available version to remediate this issue. Until an upgrade is applied, restrict access to source code, application packages, logs, and configuration files to prevent attackers from obtaining the hardcoded token.

Description

CAST Imaging version 3.6.2 contains a hardcoded authentication token in the KeyCloakController class within auth-service.jar. This token can be reused by an attacker with access to source code, application packages, logs, or configuration files to call authentication service endpoints without proper authentication. Exploiting the "/api/auth/keycloak/users" endpoint allows user enumeration across Keycloak realms and retrieval of user attributes with API token hashes, facilitating reconnaissance and potential further exploitation. The vendor has confirmed the vulnerability in version 3.6.2 and states it is fixed in newer versions, though no specific fixed versions are provided.

References

Community reviews

Loading reviews…