CVE-2026-54550: Izpack installer Path Traversal Vulnerability

HIGH
Advisory Identifier: GHSA-f63g-88cj-hjf9
CVSS 7.4
CWE-22
Published
Advisory Summary

CVE-2026-54550 is a HIGH (CVSS 7.4) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Izpack installer libraries in the Maven ecosystem. The issue involves izpack has path traversal in unpackerbase that allows writing files outside the installation directory via malicious pack entries. Remediation is available in the latest vendor maintenance releases.

CVE-2026-54550 at a Glance

CVE Identifier CVE-2026-54550
GHSA Identifier GHSA-f63g-88cj-hjf9
Severity HIGH
CVSS v3.1 Base Score 7.4
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Izpack installer
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-54550

To remediate this vulnerability, upgrade all affected Izpack installer dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.codehaus.izpack:izpack-installer fixed: Latest secure release
<dependency>
    <groupId>org.codehaus.izpack</groupId>
    <artifactId>izpack-installer</artifactId>
    <version>Latest secure release</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.codehaus.izpack

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-54550, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.codehaus.izpack

Analyze the terminal output to locate any version of Izpack installer in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.codehaus.izpack command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Izpack installer, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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: ```java 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 installer with malicious `PackFile` entries. The file format is a standard ZIP with serialised resources — no integrity protection. **Confirmed unpatched in HEAD (fetched from GitHub, 2025):** ``` git show HEAD:izpack-installer/src/main/java/com/izforge/izpack/installer/unpacker/UnpackerBase.java \ | grep -n 'getCanonicalPath\|startsWith.*install\|traversal' # (no output — fix not present) ``` ### PoC ```bash # 1. Clone IzPack source and view the vulnerable code directly git clone --depth=1 --branch izpack-5.2.4 https://github.com/izpack/izpack.git sed -n '615,650p' izpack/izpack-installer/src/main/java/com/izforge/izpack/installer/unpacker/UnpackerBase.java # 2. Compile and run the following Java reproducer (no IzPack classpath needed): ``` ```java // TestPathTraversal.java import java.io.*; public class TestPathTraversal { // Exact replication of IoHelper.translatePath() — separator swap, no security static String translatePath(String destination) { return destination.replace('/', File.separatorChar); } public static void main(String[] args) throws Exception { String installDir = "/tmp/izpack_install"; String maliciousPath = installDir + "/../../../tmp/ESCAPED_FILE"; // This is what UnpackerBase does: String path = translatePath(maliciousPath); File target = new File(path); // resolves traversal target.getParentFile().mkdirs(); try (FileWriter fw = new FileWriter(target)) { fw.write("Written outside install dir via IzPack path traversal\n"); } System.out.println("File written to: " + target.getCanonicalPath()); System.out.println("Inside installDir: " + target.getCanonicalPath().startsWith(new File(installDir).getCanonicalPath())); } } ``` ```bash javac TestPathTraversal.java && java TestPathTraversal # Output: File written to: /tmp/ESCAPED_FILE # Inside installDir: false ``` ### Impact Any user who runs an IzPack-generated installer is affected. The attacker only needs to distribute a repackaged installer — a common social-engineering vector. On Windows (the primary IzPack platform) the victim typically runs the installer as a local administrator, so the attacker can write to `%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup`, `%SystemRoot%\System32`, or any other location reachable by the victim user. On Linux/macOS the same applies for user-writable locations. No authentication, no special privileges and no interaction beyond running the installer are required on the victim side. ### Credits This issue was identified by Michał Majchrowicz, Marcin Wyczechowski, and Paweł Zdunek, members of the AFINE Team.

CVE-2026-54550 Affected Izpack installer Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
org.codehaus.izpack:izpack-installer
Maven
≤ 5.2.6

References

Frequently Asked Questions

What is CVE-2026-54550?
CVE-2026-54550 is a security vulnerability in Izpack installer involving IzPack has Path Traversal in UnpackerBase that allows writing files outside the installation directory via malicious pack entries under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Izpack installer versions are affected?
Affected versions include releases prior to current release patches across affected packages: org.codehaus.izpack:izpack-installer.
What version fixes CVE-2026-54550?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is izpack-installer affected?
Yes, org.codehaus.izpack:izpack-installer is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-54550?
CVE-2026-54550 has a CVSS v3.1 base score of 7.4 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N.
What CWE is associated with CVE-2026-54550?
CVE-2026-54550 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check Maven dependencies for CVE-2026-54550?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.codehaus.izpack'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f63g-88cj-hjf9",
  "modified" : "2026-08-26T14:24:40Z",
  "published" : "2026-08-26T14:24:40Z",
  "aliases" : [ "CVE-2026-54550" ],
  "summary" : "IzPack has Path Traversal in UnpackerBase that allows writing files outside the installation directory via malicious pack entries",
  "details" : "### Summary\n\nIzPack's `UnpackerBase.unpack()` resolves pack-file target paths without any\ncanonical-path or directory-containment check. An attacker who distributes a\ntrojanized installer JAR (the format is unsigned) can include pack entries whose\n`targetPath` contains `../` sequences. When a victim runs the installer the\nfile is written to an attacker-chosen location on disk under the victim's\nprivileges — including startup folders, PATH directories, or system locations.\n\n### Details\n\n**Vulnerable method:** `com.izforge.izpack.installer.unpacker.UnpackerBase.unpack()`\n**Source file:** `izpack-installer/src/main/java/com/izforge/izpack/installer/unpacker/UnpackerBase.java`\n**Vulnerable lines (5.2.4):** ~618–627\n\nThe relevant code path is:\n\n```java\nString targetPath = packFile.getTargetPath();             // attacker-controlled\nString path       = IoHelper.translatePath(targetPath, variables); // separator swap ONLY\nFile   target     = new File(path);                       // no canonical check\n// ... mkdirs() then file is written to `target`\n```\n\n`IoHelper.translatePath()` (source: `izpack-util/.../IoHelper.java`) performs\n**only** file-separator character conversion (`'/'` ↔ `File.separatorChar`) and\ncontains no security validation whatsoever. There is no call to\n`getCanonicalPath()`, no `startsWith(installDir)` containment check, and no\nnormalisation of `..` segments.\n\nBecause IzPack installer JARs carry **no digital signature**, an attacker can\nrepack any legitimate installer with malicious `PackFile` entries. The file\nformat is a standard ZIP with serialised resources — no integrity protection.\n\n**Confirmed unpatched in HEAD (fetched from GitHub, 2025):**\n```\ngit show HEAD:izpack-installer/src/main/java/com/izforge/izpack/installer/unpacker/UnpackerBase.java \\\n  | grep -n 'getCanonicalPath\\|startsWith.*install\\|traversal'\n# (no output — fix not present)\n```\n\n### PoC\n\n```bash\n# 1. Clone IzPack source and view the vulnerable code directly\ngit clone --depth=1 --branch izpack-5.2.4 https://github.com/izpack/izpack.git\nsed -n '615,650p' izpack/izpack-installer/src/main/java/com/izforge/izpack/installer/unpacker/UnpackerBase.java\n\n# 2. Compile and run the following Java reproducer (no IzPack classpath needed):\n```\n\n```java\n// TestPathTraversal.java\nimport java.io.*;\n\npublic class TestPathTraversal {\n    // Exact replication of IoHelper.translatePath() — separator swap, no security\n    static String translatePath(String destination) {\n        return destination.replace('/', File.separatorChar);\n    }\n\n    public static void main(String[] args) throws Exception {\n        String installDir   = \"/tmp/izpack_install\";\n        String maliciousPath = installDir + \"/../../../tmp/ESCAPED_FILE\";\n\n        // This is what UnpackerBase does:\n        String path   = translatePath(maliciousPath);\n        File   target = new File(path);           // resolves traversal\n        target.getParentFile().mkdirs();\n        try (FileWriter fw = new FileWriter(target)) {\n            fw.write(\"Written outside install dir via IzPack path traversal\\n\");\n        }\n        System.out.println(\"File written to: \" + target.getCanonicalPath());\n        System.out.println(\"Inside installDir: \" +\n            target.getCanonicalPath().startsWith(new File(installDir).getCanonicalPath()));\n    }\n}\n```\n\n```bash\njavac TestPathTraversal.java && java TestPathTraversal\n# Output: File written to: /tmp/ESCAPED_FILE\n#         Inside installDir: false\n```\n\n### Impact\n\nAny user who runs an IzPack-generated installer is affected. The attacker only\nneeds to distribute a repackaged installer — a common social-engineering vector.\nOn Windows (the primary IzPack platform) the victim typically runs the installer\nas a local administrator, so the attacker can write to `%APPDATA%\\Microsoft\\Windows\\Start Menu\\Programs\\Startup`,\n`%SystemRoot%\\System32`, or any other location reachable by the victim user.\nOn Linux/macOS the same applies for user-writable locations.\n\nNo authentication, no special privileges and no interaction beyond running the\ninstaller are required on the victim side.\n\n### Credits\nThis issue was identified by Michał Majchrowicz, Marcin Wyczechowski, and Paweł Zdunek, members of the AFINE Team.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.codehaus.izpack:izpack-installer"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.2.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/izpack/izpack/security/advisories/GHSA-f63g-88cj-hjf9"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/izpack/izpack/pull/1193"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/izpack/izpack/commit/4233ba38d0f1825f9cf3e0204e5261a5498e29d8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/izpack/izpack/commit/8b7c6792c4fe85e3b1759c106aae39b904848466"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/izpack/izpack"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-26T14:24:40Z",
    "nvd_published_at" : null
  }
}