Skip to navigation

Threat reportVulnerabilityTL-2026-4788

Szafir software vulnerabilities: XXE (CVE-2026-93570), path traversal (CVE-2026-93571), improper certificate validation (CVE-2026-106036)

highMONITORING

CERT Polska disclosed three vulnerabilities in Szafir, the electronic-signature application from Krajowa Izba Rozliczeniowa (KIR): an XXE flaw allowing arbitrary local file read when a crafted XML file is signed or verified, a path traversal in the update handling, and a complete lack of certificate and hostname validation.

Key facts

IdentifiersTL-2026-4788, CVE-2026-93570, CVE-2026-93571, CVE-2026-106036, CVE-2026-9058
SeverityHIGH
CVSS8.2 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N)
First disclosed
EPSSCVE-2026-9058: 0.3% (23.8th percentile); CVE-2026-93570: 0.2% (20.3th percentile); CVE-2026-93571: 0.1% (8.1th percentile)
Affected productsKrajowa Izba Rozliczeniowa Szafir; Krajowa Izba Rozliczeniowa Szafir Weryfikująca
Weaknesses (CWE)CWE-611, CWE-22, CWE-295
ToolsSzafir, Szafir Weryfikująca
MITRE ATT&CK techniquesT1005 Data from Local System, T1195.002 Compromise Software Supply Chain, T1204.002 Malicious File, T1557 Adversary-in-the-Middle, T1565.001 Stored Data Manipulation
MotivationUNKNOWN
Target sectorselectronic-signature users
Target regionspoland
Detection rules9 (1 shown free)
Sources7 cited sources

Detection coverage

As of 2026-10-30, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-4788 across Splunk SPL, Microsoft KQL and Sigma, covering 8 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Szafir XML Opened Followed by Non-Vendor Outbound Connection (CVE-2026-93570 XXE)

Detects the CVE-2026-93570 (CWE-611) XXE trigger in the Szafir e-signature application: a Szafir process is launched with an XML file and, within the same 10-minute window, the Szafir process connects to a host outside the KIR/vendor domains, which is the behaviour of an external DTD / external entity fetch. The flaw allows arbitrary local file read when a crafted XML with a DOCTYPE external DTD is signed or verified. Exploitation is theoretical today (no ITW reports), so this is a behaviour-first early-warning rule.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1204.002, T1203, T1005, T1071.001
  • Data sources: sysmon:EventCode=1, sysmon:EventCode=3, DeviceProcessEvents, DeviceNetworkEvents
  • Severity: high
  • Confidence: medium

Splunk SPL

index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" earliest=-24h (EventCode=1 OR EventCode=3) Image="*Szafir*.exe"
| eval xml_open=if(EventCode=1 AND like(lower(CommandLine),"%.xml%"),1,0)
| eval ext_conn=if(EventCode=3 AND NOT match(lower(coalesce(DestinationHostname,"")),"(elektronicznypodpis[.]pl|kir[.]pl)$"),1,0)
| bin _time span=10m
| stats sum(xml_open) as xml_opens sum(ext_conn) as ext_conns values(CommandLine) as command_lines values(DestinationIp) as dest_ips values(DestinationHostname) as dest_hosts by host, User, Image, _time
| where xml_opens>0 AND ext_conns>0

Microsoft KQL

let XmlOpens = DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName contains "Szafir" and ProcessCommandLine contains ".xml"
| project OpenTime = Timestamp, DeviceId, OpenCommandLine = ProcessCommandLine;
DeviceNetworkEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName contains "Szafir" and ActionType == "ConnectionSuccess"
| where not(RemoteUrl endswith "elektronicznypodpis.pl" or RemoteUrl endswith "kir.pl")
| join kind=inner XmlOpens on DeviceId
| where Timestamp between (OpenTime .. (OpenTime + 10m))
| project Timestamp, DeviceName, InitiatingProcessAccountName, OpenCommandLine, RemoteIP, RemotePort, RemoteUrl

Sigma

title: Szafir XML Opened Followed by Non-Vendor Network Connection (CVE-2026-93570)
name: szafir_xml_open
id: 3f6b8a52-7c1d-4e2a-9b0f-5a1c2d3e4f11
status: experimental
description: Szafir (or Szafir Weryfikujaca) process started with an XML file argument. Building block for the CVE-2026-93570 XXE correlation.
references:
  - https://cert.pl/en/posts/2026/10/CVE-2026-93570/
  - https://nvd.nist.gov/vuln/detail/CVE-2026-93570
author: Threadlinqs Team
date: 2026/10/30
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|contains: 'Szafir'
    CommandLine|contains: '.xml'
  condition: selection
falsepositives:
  - Legitimate signing or verification of XML documents
level: informational
---
title: Szafir Non-Vendor Network Connection
name: szafir_external_connection
id: 3f6b8a52-7c1d-4e2a-9b0f-5a1c2d3e4f12
status: experimental
description: Szafir process initiating a network connection to a host outside the vendor domains. Building block for the CVE-2026-93570 XXE correlation.
references:
  - https://cert.pl/en/posts/2026/10/CVE-2026-93570/
author: Threadlinqs Team
date: 2026/10/30
logsource:
  category: network_connection
  product: windows
detection:
  selection:
    Image|contains: 'Szafir'
    Initiated: 'true'
  filter_vendor:
    DestinationHostname|endswith:
      - 'elektronicznypodpis.pl'
      - 'kir.pl'
  condition: selection and not filter_vendor
falsepositives:
  - OCSP, CRL and timestamp authority lookups
level: informational
---
title: Szafir XXE - XML Opened Then External Connection (CVE-2026-93570)
id: 3f6b8a52-7c1d-4e2a-9b0f-5a1c2d3e4f10
status: experimental
description: Correlates a Szafir process opening an XML file with a non-vendor outbound connection by Szafir within 10 minutes on the same host, indicating an external DTD or entity fetch (CWE-611, CVE-2026-93570).
references:
  - https://cert.pl/en/posts/2026/10/CVE-2026-93570/
  - https://nvd.nist.gov/vuln/detail/CVE-2026-93570
author: Threadlinqs Team
date: 2026/10/30
tags:
  - attack.execution
  - attack.t1204.002
  - attack.t1203
  - attack.collection
  - attack.t1005
  - cve.2026.93570
correlation:
  type: temporal
  rules:
    - szafir_xml_open
    - szafir_external_connection
  group-by:
    - Computer
  timespan: 10m
falsepositives:
  - Szafir contacting third-party OCSP, CRL or timestamp services while processing a signed XML
level: high

Known false positives:

  • Szafir contacting OCSP, CRL or qualified timestamp authority servers while signing or verifying a legitimately signed XML (XAdES) document
  • Administrators testing XML signing with documents that reference remote schemas

Tuning notes: Allow-list the OCSP/CRL/TSA hosts your organisation legitimately uses (extend the vendor-domain regex). The Image filter assumes the process is named Szafir*.exe; if Szafir runs under a Java launcher in your estate, add the javaw.exe host process and key on CommandLine containing szafir (the KQL version can use InitiatingProcessCommandLine). Requires Sysmon EventCode 1 and 3 collection for Szafir hosts.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • External DTD Fetch Over HTTP From Endpoint (XXE Out-of-Band, CVE-2026-93570) · unlock with TL Creds
  • Szafir Process Creating Executable or Script Content (Malicious Update Delivery) · unlock with TL Creds
  • Vulnerable or End-of-Life Szafir Software Inventory (CVE-2026-93570/93571/106036) · unlock with TL Creds
  • Szafir Launched With XML From User-Writable Location (CVE-2026-93570 Lure Opened) · unlock with TL Creds
  • Szafir Spawning Shell or Script Interpreter (Post-Update-Compromise Execution) · unlock with TL Creds
  • Szafir Network Connection to Non-Vendor Host (Update Channel AitM, CVE-2026-106036) · unlock with TL Creds
  • Szafir Process Writing Files Outside Application Directories (CVE-2026-93571 Path Traversal) · unlock with TL Creds
  • Szafir Update Channel Resolving Non-Vendor Domains (CVE-2026-106036 AitM) · unlock with TL Creds

Indicators of compromise

As of 2026-10-30, Threadlinqs Intelligence tracks 8 indicators of compromise for TL-2026-4788.

Sample indicators (1 of 8)

  • Domain: elektronicznypodpis[.]pl

Defanged, TLP:CLEAR. Full set of 8 indicators: unlock with TL Creds.

8 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Szafir is fixed in 2.0 build 708; Szafir Weryfikująca (all versions) is End of Life and remains unpatched.

CERT Polska published coordinated-disclosure advisory CVE-2026-93570 on 29 October 2026 covering three vulnerabilities in Szafir, a digital signature application developed by Krajowa Izba Rozliczeniowa S.A. (KIR). Szafir versions below 2.0.0 build 708 are affected, as are all versions of the companion product Szafir Weryfikująca. The issues were reported by Mikus Teivens of Critical Security.

CVE-2026-93570 (CWE-611, XML External Entity injection): when a user signs or verifies a crafted XML file containing a DOCTYPE declaration with an external DTD reference, the XML parser resolves external entities. This allows an attacker who can get the victim to open the file to read arbitrary files from the victim's filesystem. User interaction is required (open/sign/verify a malicious XML document). NVD scores this CVE 8.2 (HIGH) under CVSS 4.0 (AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N). It is fixed in Szafir 2.0 build 708; Szafir Weryfikująca will not be fixed because it is End of Life.

CVE-2026-93571 (CWE-22, path traversal): a man-in-the-middle attacker who can redirect Szafir's update requests can supply crafted XML files that are saved to attacker-chosen locations on the victim system. Fixed in Szafir 2.0 build 708.

CVE-2026-106036 (CWE-295, improper certificate validation): the application accepts any client or server certificate without performing certificate and hostname validation. An attacker able to intercept traffic can present a forged SSL/TLS certificate and deliver malicious updates. Fixed in Szafir 2.0 build 708. Combined with the path traversal, the update channel is attackable by a network-positioned adversary; CERT Polska describes malicious update delivery as the consequence.

The advisory reports no confirmed in-the-wild exploitation, no public proof-of-concept, and no indicators of compromise. CVSS scores for CVE-2026-93571 and CVE-2026-106036 were not published in the sources reviewed. Earlier, separate CERT Polska advisory CVE-2026-9058 (May 2026) covered a different improper certificate validation flaw in the Szafir SDK (fixed in 1.8.463.2); it is a distinct issue, noted here only as related product history.

MITRE ATT&CK techniques by tactic:

Collection

T1005 Data from Local System

Initial Access

T1195.002 Compromise Software Supply Chain

Execution

T1204.002 Malicious File

Credential Access

T1557 Adversary-in-the-Middle

Impact

T1565.001 Stored Data Manipulation

Remediation

Patches

  • Szafir 2.0 build 708 fixes CVE-2026-93570, CVE-2026-93571 and CVE-2026-106036

Immediate actions

  • Upgrade Szafir to version 2.0 build 708 or later
  • Do not sign or verify XML files received from untrusted sources until patched
  • Stop using Szafir Weryfikująca (End of Life, no fix will be released) and migrate to a supported product

Workarounds

  • No fix exists for Szafir Weryfikująca; remove it from use
  • Avoid running Szafir updates over untrusted or intercepted networks (certificate validation is absent in unpatched versions)

Longer-term hardening

  • Inventory endpoints running Szafir or Szafir Weryfikująca and track removal of unsupported versions
  • Monitor for outbound connections initiated by Szafir processes to unexpected hosts (external DTD fetches, update traffic)

Affected and fixed versions

  • Krajowa Izba Rozliczeniowa — Szafir
    Vulnerable versions: all versions below 2.0.0 build 708
    Fixed in: 2.0 build 708
  • Krajowa Izba Rozliczeniowa — Szafir Weryfikująca
    Vulnerable versions: all versions (CVE-2026-93570; End of Life)

Timeline

  • Related, separate Szafir SDK certificate validation flaw CVE-2026-9058 reported to CERT Polska (fixed in Szafir SDK 1.8.463.2)
  • CERT Polska updated the CVE-2026-9058 Szafir SDK advisory with an additional CWE
  • NVD published CVE-2026-93570 with CVSS 4.0 base score 8.2 (HIGH)
  • Szafir Weryfikująca (all versions) confirmed End of Life and not fixed for CVE-2026-93570
  • Szafir 2.0 build 708 released as the fixed version for all three vulnerabilities
  • CERT Polska published advisory for CVE-2026-93570, CVE-2026-93571 and CVE-2026-106036 in Szafir, crediting Mikus Teivens (Critical Security)

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 7 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats