CVE-2026-42049

jadx: RCE Via Groovy Code Injection in Gradle Export

Published Jul 14, 2026 CVSS 4.0 · 8.4 High EPSS < 1% KEV · Not listed
Description
jadx is a Dex to Java decompiler. Prior to 1.5.6, jadx inserts the android:versionName value from an AndroidManifest into the generated app/build.gradle Groovy template without proper sanitization when exporting a decompiled APK as an Android Gradle project. A malicious APK can break out of the string context so that opening or building the exported Gradle project executes attacker-controlled Groovy code on the victim machine. This issue is fixed in version 1.5.6.

Analysis

AI-generated

Technical impact

The jadx decompiler allows a malicious Android application to inject Groovy code into the Gradle build script that is generated when a user exports a decompiled APK as a Gradle project. Because the versionName value is placed into the Groovy template without sanitization, an attacker can break out of the string context and have arbitrary code executed on the machine that opens or builds the exported project. This is a remote code execution flaw that can compromise the confidentiality, integrity, and availability of the victim system. The weakness is a classic code‑injection vulnerability (CWE‑94).

Affected Systems

The flaw exists in the open‑source jadx decompiler from skylot. Versions prior to 1.5.6 are affected by the injection issue when exporting using the Gradle project feature. jadx 1.5.6 and later contain the fix.

Risk and Exploitability

The CVSS base score of 8.4 signals high severity. The EPSS score of less than 1 % indicates a very low probability of exploitation in current real‑world usage, though knowledge of the flaw remains. Because the vulnerability requires a malicious APK to be supplied to jadx and the victim to open the resulting Gradle project, it is essentially a local or convenience‑based attack rather than a widespread remote exploit. The flaw is not listed in the CISA KEV catalog, but administrators should treat it as a high‑priority issue and apply the vendor‑supplied patch promptly.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Install the latest version of jadx (v1.5.6 or newer) which contains the sanitization change.
  • Restrict the use of the Gradle export feature to trusted or verified APKs only.
  • Inspect any exported Gradle files for unexpected Groovy code before opening or building them.

Generated by OpenCVE AI on July 31, 2026 at 04:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Skylot
Skylot jadx
Vendors & Products Skylot
Skylot jadx
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description jadx is a Dex to Java decompiler. Prior to 1.5.6, jadx inserts the android:versionName value from an AndroidManifest into the generated app/build.gradle Groovy template without proper sanitization when exporting a decompiled APK as an Android Gradle project. A malicious APK can break out of the string context so that opening or building the exported Gradle project executes attacker-controlled Groovy code on the victim machine. This issue is fixed in version 1.5.6.
Title jadx: RCE Via Groovy Code Injection in Gradle Export
Weaknesses CWE-94
References
Metrics cvssV4_0

{'score': 8.4, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-94

    Improper Control of Generation of Code ('Code Injection')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 1:26 PM
Reserved
Apr 23, 2026, 4:05 PM
Status
Deferred
Published
Jul 14, 2026, 10:16 PM
Modified
Oct 24, 2026, 10:10 PM