# IzPack has Path Traversal in UnpackerBase that allows writing files outside the installation directory via malicious pack entries

Advisory record · `GHSA-f63g-88cj-hjf9`

- **Identifiers:** `GHSA-f63g-88cj-hjf9` · `CVE-2026-54550`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 26 Aug 2026
- **Updated:** 27 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 26 Aug 2026, 14:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.codehaus.izpack:izpack-installer` (Maven): affected `<5.2.7`; fixed in `5.2.7`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> IzPack's installer library (org.codehaus.izpack:izpack-installer) versions before 5.2.7 are vulnerable to path traversal in UnpackerBase.unpack(), which does not check that pack-file target paths stay inside the installation directory. An attacker who distributes a repackaged installer can cause the victim's installer to write files to arbitrary locations under the victim's privileges. Users should upgrade to version 5.2.7 or later.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0045, the 39th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f63g-88cj-hjf9)

## Sources

- [GitHub Advisory Database: GHSA-f63g-88cj-hjf9](https://github.com/advisories/GHSA-f63g-88cj-hjf9)
- [OSV: GHSA-f63g-88cj-hjf9](https://osv.dev/vulnerability/GHSA-f63g-88cj-hjf9)
- <https://github.com/izpack/izpack/security/advisories/GHSA-f63g-88cj-hjf9>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-54550>
- <https://github.com/izpack/izpack/pull/1193>
- <https://github.com/izpack/izpack/commit/4233ba38d0f1825f9cf3e0204e5261a5498e29d8>
- <https://github.com/izpack/izpack/commit/8b7c6792c4fe85e3b1759c106aae39b904848466>
- <https://github.com/izpack/izpack>
- <https://github.com/izpack/izpack/releases/tag/izpack-5.2.7>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f63g-88cj-hjf9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f63g-88cj-hjf9/>. Everything for agents: <https://agentprime.io/llms.txt>.