CVE-2026-113618: KAMSOFT ZSIRep Client Library · Improper Certificate Validation
Affects KAMSOFT ZSIRep Client LibrarySource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.12.3.1 when convenient.
Data as of 6 Nov 2026, 14:19 UTC
Thin evidence
One scorer or none| CNA (CERT-PL) | CVSS 4.0 | 5.3 |
|---|
- Patch
- Available – fixed in 2.12.3.1
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 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 6 Nov 2026.
What to do
Upgrade KAMSOFT ZSIRep Client Library to 2.12.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| KAMSOFTZSIRep Client Library | Affected
| Fixed in
|
AI-suggested
Upgrade the ZSIRep client library to version 2.12.3.1 or later. Also, update the affected KAMSOFT products to their fixed versions: KS-SOMED 2026.03.0.01, KS-PPS 2026.03.1.0, KS-MEDIS 2026.03.0.0, KS-SOLAB 2026.3.1.0, and KS-ASW 2026.3.0.1. Applying these official fixes eliminates the improper certificate validation vulnerability. No alternative mitigations are indicated.
Description
The KAMSOFT ZSIRep client library (ZSIREP.CLIENT.DLL) suffers from improper server certificate validation, allowing man-in-the-middle attackers to impersonate the server and intercept or modify sensitive data. This vulnerability arises because the library registers a process-wide .NET callback that accepts any HTTPS certificate without verification, and this callback remains active even after the client is closed, potentially affecting other HTTPS connections in the same application. The issue has been fixed in version 2.12.3.1 and corresponding updates for related products.