Path Traversal in org.codehaus.izpack:izpack-installer (CVE-2026-54550)
Summary
Path traversal in org.codehaus.izpack:izpack-installer (CVE-2026-54550). Data can be tampered with by attackers. Exploitable via targetPath.
Original description
The description as published by the source.
Summary
IzPack's UnpackerBase.unpack() resolves pack-file target paths without any
canonical-path or directory-containment check. An attacker who distributes a
trojanized installer JAR (the format is unsigned) can include pack entries whose
targetPath contains ../ sequences. When a victim runs the installer the
file is written to an attacker-chosen location on disk under the victim's
privileges — including startup folders, PATH directories, or system locations.
Details
Vulnerable method: com.izforge.izpack.installer.unpacker.UnpackerBase.unpack()
Source file: izpack-installer/src/main/java/com/izforge/izpack/installer/unpacker/UnpackerBase.java
Vulnerable lines (5.2.4): ~618–627
The relevant code path is:
String targetPath = packFile.getTargetPath(); // attacker-controlled
String path = IoHelper.translatePath(targetPath, variables); // separator swap ONLY
File target = new File(path); // no canonical check
// ... mkdirs() then file is written to `target`
IoHelper.translatePath() (source: izpack-util/.../IoHelper.java) performs
only file-separator character conversion ('/' ↔ File.separatorChar) and
contains no security validation whatsoever. There is no call to
getCanonicalPath(), no startsWith(installDir) containment check, and no
normalisation of .. segments.
Because IzPack installer JARs carry no digital signature, an attacker can
repack any legitimate instal…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54550 has been found in org.codehaus.izpack:izpack-installer.
Attackers can target a specific entry point like targetPath over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "org.codehaus.izpack:izpack-installer CVE-2026-54550" on the vendor's site.
CVE-2026-54550 (org.codehaus.izpack:izpack-installer) — CWE-22 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: targetPath / target / File.separatorChar / PackFile
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in org.codehaus.izpack:izpack-installer. Attackers reach the vulnerable code path via targetPath without authentication.
Check the vendor advisory for the affected versions of org.codehaus.izpack:izpack-installer. Attack surface: targetPath / target / File.separatorChar / PackFile.
Severity: High (CVSS 7.4/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.codehaus.izpack:izpack-installer を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com