CVE-2026-54684 skylot CVE debrief

Who should care

Defenders responsible for systems using jadx should assess exposure and prioritize verification and remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify jadx versions and system configurations to ensure the security of their environments.

Why it matters

Defenders should care about CVE-2026-54684 because it affects jadx, a Dex to Java decompiler, and has the potential for arbitrary code execution and planting of JAR files. Verification of jadx version and system configurations is necessary, and remediation priority is high.

• Potential arbitrary code execution through loading attacker-controlled plugin code
• Possible planting of JAR files in plugins/dropins directory
• Verification of jadx version and system configurations is necessary
• Remediation priority is high due to potential for exploitation

Technical summary

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.

Defensive priority

Defenders should prioritize verifying jadx versions and upgrading to 1.5.6 if necessary.

Recommended defensive actions

• Verify jadx version and upgrade to 1.5.6 if necessary
• Review system configurations and inventory for jadx usage
• Monitor for suspicious activity related to jadx
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability. However, the scope of affected versions and systems requires verification. Defenders should verify jadx versions and system configurations to assess exposure. Evidence limits and source grounding indicate that further verification is necessary to confirm affected scope and severity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.