CVE-2026-26928
Unverified DLL Upload in SzafirHost Enables Remote Code Execution
Publication date: 2026-04-02
Last updated on: 2026-04-02
Assigner: CERT.PL
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| krajowa_izba_rozliczeniowa | szafirhost | 1.1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-354 | The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in SzafirHost involves improper verification of certain dynamic library files. While JAR files are correctly verified using trusted hashes and digital signatures, DLL, SO, JNILIB, and DYLIB files are not checked for hash or vendor digital signatures. This allows an attacker to provide a malicious file that gets saved in the user's /temp folder and executed by the application.
How can this vulnerability impact me? :
This vulnerability can lead to the execution of malicious code on the affected system because an attacker can supply harmful dynamic library files that the application will run without proper verification. This can compromise the security and integrity of the user's environment.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves the SzafirHost application saving and executing malicious DLL, SO, JNILIB, or DYLIB files in the user's /temp folder without verifying their hash or digital signature.
To detect this vulnerability on your system, you can monitor the /temp directory for suspicious DLL, SO, JNILIB, or DYLIB files that were recently created or modified.
Additionally, you can check the version of SzafirHost installed to see if it is below 1.1.0, as the issue was fixed starting from version 1.1.0.
- Use commands like `ls -ltr /temp/*.dll /temp/*.so /temp/*.jnilib /temp/*.dylib` on Unix-like systems to list recently modified or created files.
- Check the SzafirHost version by running the application with a version flag or checking its installation metadata.
- Monitor process execution logs or use system auditing tools to detect execution of files from the /temp directory.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade SzafirHost to version 1.1.0 or later, where this vulnerability has been fixed.
Until the upgrade is applied, restrict or monitor the execution of DLL, SO, JNILIB, or DYLIB files from the /temp directory to prevent malicious files from being executed.
Implement file integrity monitoring and restrict write permissions to the /temp folder to limit the ability of attackers to place malicious files there.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how the vulnerability in SzafirHost affects compliance with common standards and regulations such as GDPR or HIPAA.