Szafir accepts any client or server certificate without performing certificate and hostname validation, allowing HTTPS
Source GCVE Database
Not known to be exploited · CVSS 6.9 Medium · fixed in 2.0 : update Szafir when convenient.
Data as of 29 Oct 2026, 20:14 UTC
Thin evidence
One scorer or none| CNA (CERT-PL) | CVSS 4.0 | 6.9 |
|---|
- Patch
- Available – fixed in 2.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Krajowa Izba RozliczeniowaSzafir | Affected
| Fixed in– |
AI-suggested
Upgrade Szafir to version 2.0 build 708 or later, where the certificate and hostname validation issue is fixed. No other mitigation is indicated by the vendor advisory.
Description
Szafir versions prior to 2.0 build 708 accept any client or server certificate without validating the certificate or hostname. This allows HTTPS connections without authenticating the remote server, enabling an attacker to present arbitrary SSL/TLS certificates and potentially cause the application to download malicious update files from their server. The vulnerability is fixed in version 2.0 build 708.