# CVE-2026-54684: Path traversal in jadx

> A malicious XAPK file can write files outside the intended directory, allowing attackers to plant plugins that execute code on the next jadx run.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-gpvc-ccw7-744v

## What is CVE-2026-54684?

CVE-2026-54684 is a high-severity path traversal vulnerability in skylot jadx, published on 14 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

jadx is a Dex to Java decompiler. From 1.5.2 to 1.5.5, a malicious .xapk file can cause jadx to write attacker-controlled archive entry contents outside the intended XAPK plugin temporary unpack directory because XApkLoader resolves each entry name directly with tmpDir.resolve(fileName) after a CWD-based ZIP security check. When jadx is launched from a directory that is an ancestor of the config directory, the arbitrary write can plant a JAR in plugins/dropins, and the next jadx run loads the JAR with URLClassLoader and ServiceLoader, executing attacker-controlled plugin code. This issue is fixed in version 1.5.6.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-54684?


## How do I fix CVE-2026-54684?

No fix has been published for CVE-2026-54684 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54684 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54684 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54684 and fix it if it is affected.

What it is: CVE-2026-54684 is a high-severity path traversal vulnerability in skylot jadx, published on 14 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54684 exists.

Affected product: skylot jadx. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54684/ (Markdown: https://insights.sbomify.com/CVE-2026-54684/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54684
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54684
- OSV: https://osv.dev/vulnerability/CVE-2026-54684

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54684/
Summaries are generated and may contain mistakes; the official description above is the record.