CVE-2026-54684
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 · uneditedjadx 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.
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 confidencejadx's XApkLoader has a path traversal vulnerability where malicious .xapk entries can escape the intended temporary unpack directory via tmpDir.resolve(fileName). When jadx runs from a directory that is an ancestor of the config directory, attackers can plant a JAR in plugins/dropins, which jadx auto-loads via URLClassLoader/ServiceLoader on next execution, achieving remote code execution.
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
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify jadx versionRun 'jadx --version' or check the JAR file manifest for the version numberAffected if Version is older than 1.5.6 (the patch release)
-
Locate jadx config directoryCheck for a config directory in the user's home (such as ~/.jadx or similar), or run jadx with verbose logging to see where config is storedAffected if A config directory exists and is located somewhere within the filesystem hierarchy
-
Determine directory relationshipCompare the full path where jadx is executed from versus the config directory path - check if the jadx execution path is an ancestor directory of the config directoryAffected if The jadx execution directory is a parent/ancestor of the config directory (e.g., jadx runs from /home/user and config is at /home/user/.jadx)
-
Inspect plugins/dropins directoryNavigate to the plugins or dropins subdirectory within the config directory and list all JAR files presentAffected if Any unexpected or untrusted JAR files exist in plugins/dropins that were not intentionally installed by the user
You are affected if running jadx version below 1.5.6, with the config directory nested inside the jadx execution directory, and any suspicious JAR files present in the plugins/dropins folder.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to jadx version 1.5.6 or later. Avoid opening untrusted .xapk files with jadx until patched.
jadx 1.5.6
- Check current jadx version by running `jadx --version`
- Download jadx version 1.5.6 from the official GitHub releases page
- Replace the existing jadx installation with version 1.5.6
- Verify the upgrade by running `jadx --version` and confirming it shows 1.5.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,768.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54684 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54684 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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