Skip to main content
Mallory
HighVulnerability

CVE-2026-13165: RCE in SzafirHost native library archive verification

Published Jun 29, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.6High · v4
EPSS0.71%54th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-13165CWE-434 · Unrestricted Upload of File with…

CVE-2026-13165 is a remote code execution vulnerability in Krajowa Izba Rozliczeniowa's SzafirHost affecting versions prior to 1.2.2. The flaw is caused by inconsistent parsing of downloaded signed native library archives: SzafirHost verifies the archive with a JarFile parser that reads the ZIP/JAR Central Directory, but extracts native libraries with JarInputStream, which processes entries sequentially from local file headers. An attacker who controls the served archive can append or insert a malicious native library entry (DLL, SO, or DYLIB) as a local-file-header entry between the last legitimate file and the Central Directory without listing it in the Central Directory. Because the verifier only inspects Central Directory entries, it does not see the injected file and accepts the archive as validly signed. The extractor, however, reads the hidden entry sequentially and writes the attacker-controlled library into the native temporary directory without an additional hash check. This parser differential allows a malicious native library to bypass signature verification and be loaded, leading to code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to bypass archive signature verification for downloaded native libraries and cause extraction of an attacker-controlled DLL, SO, or DYLIB to the native temporary directory. Because the injected library is treated as part of a trusted signed archive, exploitation can result in remote code execution in the context of the affected SzafirHost process or host environment.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure by ensuring native library archives are obtained only from fully trusted, authenticated sources under strict transport and origin control, and by independently validating archive contents before extraction. Review and harden native library extraction workflows so that only entries present in the verified Central Directory are extracted, and add explicit integrity or hash verification for extracted native libraries. These are compensating controls only; the primary mitigation is upgrading to 1.2.2 or later.

Remediation

Patch, then assume compromise.

Upgrade SzafirHost to version 1.2.2 or later. The fix addresses the inconsistency between archive verification and extraction logic. Archive validation and extraction should be performed over the same canonical set of entries, and extracted native libraries should be subject to integrity verification rather than relying solely on Central Directory-based signature checks.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-13165 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-13165 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-13165?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-13165.
Is there a patch for CVE-2026-13165?
Upgrade SzafirHost to version 1.2.2 or later. The fix addresses the inconsistency between archive verification and extraction logic.
How severe is CVE-2026-13165?
CVE-2026-13165 has a CVSS v4 score of 8.6 (High) and an EPSS score of 0.71% (54th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.