dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-44088

HIGH · 8.6 CVSS v4.0 Published 2026-05-15
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

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 signature of the downloaded JAR file using class JarInputStream (reading from the beginning of the file), but loads classes using class JarFile/URLClassLoader (reading the Central Directory from the end). It can lead to remote code execution by allowing an attacker to combine a genuine, signed JAR file with a malicious ZIP file, causing the verification to pass but the malicious class to be loaded. This issue was fixed in version 1.2.1.

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 performs JAR signature verification using JarInputStream (which reads from the beginning of the file) but loads classes using JarFile/URLClassLoader (which reads the Central Directory from the end). This inconsistency allows attackers to prepend a genuine, signed JAR to a malicious ZIP archive, causing signature verification to pass on the legitimate portion while the malicious classes from the appended content are loaded at runtime, leading to remote code execution.

MitigationUpgrade SzafirHost to version 1.2.1 or later, which fixes the inconsistent JAR parsing. If immediate upgrade is not possible, implement additional integrity checks and avoid loading JARs from untrusted sources.

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 SzafirHost installation
    Locate the SzafirHost application on the system; check for jar files, installation directories, or service processes named 'SzafirHost'
    Affected if SzafirHost is not found on the system
  2. Determine installed SzafirHost version
    Check the SzafirHost version by examining the jar manifest, version file, or running 'java -jar SzafirHost.jar --version' if applicable; compare against the fixed version 1.2.1
    Affected if Installed version is lower than 1.2.1 or version cannot be determined
  3. Inspect JAR loading configuration
    Review SzafirHost configuration files or logs for JAR loading mechanisms; look for code or settings that use JarFile or URLClassLoader to load classes from JAR archives
    Affected if SzafirHost uses JarFile or URLClassLoader to load JARs
  4. Verify JAR signature verification method
    Examine SzafirHost code or documentation for JAR signature verification; look for usage of JarInputStream versus JarFile for signature validation
    Affected if Signature verification uses JarInputStream while class loading uses JarFile/URLClassLoader (inconsistent parsing)
  5. Check for external JAR sources
    Review configuration to identify if SzafirHost loads JARs from external, untrusted, or user-controlled sources such as plugins, extensions, or dynamically provided archives
    Affected if JARs are loaded from untrusted or external sources without additional integrity controls

The environment is affected if SzafirHost version is below 1.2.1 AND the application uses the vulnerable inconsistent JAR parsing pattern (JarInputStream for verification, JarFile/URLClassLoader for loading) to load JARs from any source.

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 SzafirHost to version 1.2.1 or later, which fixes the inconsistent JAR parsing. If immediate upgrade is not possible, implement additional integrity checks and avoid loading JARs from untrusted sources.

Recommended fix Moderate confidence

SzafirHost version 1.2.1

  1. Upgrade SzafirHost to version 1.2.1 to address the JAR signature verification bypass vulnerability
  2. After upgrading, verify that JarInputStream and JarFile/URLClassLoader now consistently read from the same location (either both from the beginning or both from the Central Directory)
  3. Test that legitimate signed JAR files continue to function correctly after the upgrade
  4. Confirm that the previously vulnerable behavior (where verification passes but malicious classes load) is no longer present

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44088 — 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-44088 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