dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-13165

HIGH · 8.6 CVSS v4.0 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable No privileges 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SzafirHost verifies the downloaded native library archive with one JarFile parser (reading the Central Directory) but extracts native libraries with JarInputStream parser (reading sequentially from local file headers). An attacker who controls the served archive can insert a malicious DLL/SO/DYLIB as a local-file-header entry between the last legitimate entry and the Central Directory, without adding it to the Central Directory. The signature verifier never sees the injected entry and accepts the archive as validly signed; the extractor reads it sequentially and writes the attacker library to the native temp directory with no hash check), while the archive-size check still passes. This can lead to remote code execution. This issue was fixed in version 1.2.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SzafirHost uses two different JAR parsers: JarFile reads the Central Directory for signature verification while JarInputStream reads sequentially from local file headers for extraction. An attacker controlling the served archive can inject a malicious native library (DLL/SO/DYLIB) between the last legitimate entry and the Central Directory without adding it to the Central Directory. The signature verifier never sees the injected entry, but the extractor writes it to the temp directory with no hash check, enabling remote code execution.

MitigationUpgrade to SzafirHost version 1.2.2 or later. As a temporary workaround, verify all extracted native libraries against known-good hashes before execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SzafirHost is installed
    Search for SzafirHost binaries or services using system package managers, directory listings, or process enumeration tools
    Affected if SzafirHost is present and running on the system
  2. Determine the installed SzafirHost version
    Run version command or check version metadata files (such as version.txt, about dialog, or --version flag)
    Affected if The version is earlier than 1.2.2 (the vulnerability is present in versions before the fix)
  3. Confirm JAR extraction feature is in use
    Review application logs, configuration files, or runtime behavior to see if the system processes JAR archives
    Affected if The application processes JAR files from external or untrusted sources
  4. Inspect temp directory write behavior
    Monitor or review configuration for temp directory usage during archive extraction (look for settings that control where extracted files are written)
    Affected if The application writes extracted files to temp directories without hash verification enabled

The environment is affected if SzafirHost versions before 1.2.2 are installed and configured to extract JAR archives from untrusted sources, as this enables the parser inconsistency attack to inject malicious native libraries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to SzafirHost version 1.2.2 or later. As a temporary workaround, verify all extracted native libraries against known-good hashes before execution.

Recommended fix Moderate confidence

SzafirHost version 1.2.2

  1. Upgrade SzafirHost to version 1.2.2 or later to resolve the vulnerability
  2. Verify the upgrade by checking the application version after installation
  3. Ensure the new version uses consistent JAR parsing for both verification and extraction to prevent the described attack vector

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA1.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13165 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13165 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data