Remote code execution via conflicting JAR parsing
Published May 15, 2026 · Updated May 15, 2026
Signature verification bypass in KIR SzafirHost before 1.2.1 allows remote attackers to execute code through a crafted JAR. JarInputStream verifies content from the archive's beginning, while JarFile and URLClassLoader load a malicious class selected through the ZIP Central Directory at its end. Active user interaction is required, and successful exploitation runs attacker-supplied code in the SzafirHost process context.
Summary
What happened
Signature verification bypass in KIR SzafirHost before 1.2.1 allows remote attackers to execute code through a crafted JAR. JarInputStream verifies content from the archive's beginning, while JarFile and URLClassLoader load a malicious class selected through the ZIP Central Directory at its end. Active user interaction is required, and successful exploitation runs attacker-supplied code in the SzafirHost process context.
The record
- CVE
- CVE-2026-44088
- Published
- May 15, 2026
- Updated
- May 15, 2026
- Vendor
- Krajowa Izba Rozliczeniowa S.A.
- Product
- SzafirHost
- Classifications
- CWE-434, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2026CVE publishedPublication date reported by the CVE source.
- May 15, 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 <1.2.1
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo