XML file writes via update filename traversal
Published Oct 29, 2026 · Updated Oct 29, 2026
Path traversal in Szafir before 2.0 build 708 allows man-in-the-middle attackers to write XML files to chosen locations. The updater uses an attacker-controlled filename as a destination path without confining the write to its intended directory. Exploitation requires rerouting an update request to an attacker-controlled server; the disclosed consequence is XML file placement, not demonstrated code execution.
Summary
What happened
Path traversal in Szafir before 2.0 build 708 allows man-in-the-middle attackers to write XML files to chosen locations. The updater uses an attacker-controlled filename as a destination path without confining the write to its intended directory. Exploitation requires rerouting an update request to an attacker-controlled server; the disclosed consequence is XML file placement, not demonstrated code execution.
The record
- CVE
- CVE-2026-93571
- Published
- Oct 29, 2026
- Updated
- Oct 29, 2026
- Vendor
- Krajowa Izba Rozliczeniowa S.A.
- Product
- Szafir
- Classifications
- CWE-22, CAPEC-126, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2026CVE publishedPublication date reported by the CVE source.
- Oct 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.0 changes=[{"at":"build 708","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us