Improper Server Certificate Validation in ZSIRep Client Library
- Exploited
- No known exploitation
- Fix
- Fixed in 2.12.3.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.12.3.1.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 5/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The ZSIRep client library, used in several KS medical software products such as KS-SOMED, KS-PPS, KS-MEDIS, KS-SOLAB, and KS-ASW, does not properly verify server certificates for HTTPS connections, so an attacker on the same network can impersonate the ZSIRep server without logging in and intercept or modify authentication data and documents. Because the library leaves its certificate-accepting callback active after the client closes, it can also weaken other HTTPS connections in the same application.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The ZSIRep client library (ZSIREP.CLIENT.DLL) is vulnerable to improper server certificate validation. It registers a process-wide .NET callback that accepts any certificate for HTTPS connections without verification. This allows a man-in-the-middle attacker to impersonate the ZSIRep server and intercept or modify authentication data and documents. The callback persists after the client is closed, weakening other HTTPS connections in the same application.
The issue was fixed in version 2.12.3.1. The library is used in KS-SOMED (fixed in 2026.03.0.01), KS-PPS (fixed in 2026.03.1.0), KS-MEDIS (fixed in 2026.03.0.0), KS-SOLAB (fixed in 2026.3.1.0), and KS-ASW (fixed in 2026.3.0.1).
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.12.3.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- KAMSOFT ZSIRep Client Library
From 0.0 · fixed in 2.12.3.1
Evidence 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-113618
Is CVE-2026-113618 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-113618?
ZSIRep Client Library: from 0.0 before 2.12.3.1.Source: cve.now feed data
How do I fix CVE-2026-113618?
Upgrade to a fixed version: 2.12.3.1.Source: cve.now feed data