Live › vulnerability › CVE-2026-93571
Szafir, a Polish electronic-signature application, does not check the uploaded filename during updates. A man-in-the-middle attacker who redirects the update request can deliver an XML file that is saved to a location of their choosing.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 16:26 UTC. All times on this page are UTC.
Machines running Szafir older than 2.0 build 708 are exposed when update traffic can be redirected, for example on an untrusted network. The sources do not describe the exact deployment pattern beyond that update path, so the scope beyond it is unknown.
No product ranges from the sources yet.
2.0 build 708 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Szafir is vulnerable to Path Traversal in the uploaded filename. A man-in-the-middle attacker who can reroute update request to their server can prepare arbitrary XML file that will be saved in location chosen by attacker.
This issue was fixed in version 2.0 build 708.
This page as .md · .json · in your agent: get_signal("CVE-2026-93571")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.