CVE-2026-109857: CAST Software Imaging · Authentication Bypass by Spoofing
Affects CAST Software ImagingSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical.
Data as of 18 Nov 2026, 12:37 UTC
Thin evidence
One scorer or none| CNA (CERT-PL) | CVSS 4.0 | 9.2 |
|---|
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CAST SoftwareImaging | Affected
| 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. Since no specific fixed versions are provided, consult the vendor's official advisories or release notes for the exact patched versions. Until upgraded, restrict access to the affected service and monitor for suspicious activity related to OpenID Connect issuer registration.
Description
CAST Imaging version 3.6.2 contains an authentication bypass vulnerability in the TenantFilter class. The flaw allows an unauthenticated remote attacker to register a malicious OpenID Connect identity provider via the X-ISSUER-LOCATION HTTP header. This enables the attacker to create users with administrative usernames and obtain valid JWTs, resulting in complete authentication bypass and privilege escalation to administrative access. The vendor has confirmed the issue in version 3.6.2 and stated it is fixed in newer versions, though no specific fixed versions were provided.