dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-42049

HIGH · 8.4 CVSS v4.0 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
No privileges 5 weeks old

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 · unedited
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.

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 · moderate confidence

jadx before 1.5.6 is vulnerable to Groovy template injection when exporting decompiled APKs as Android Gradle projects. The android:versionName value from AndroidManifest is inserted into the generated app/build.gradle file without sanitization, allowing a malicious APK to break out of string context and execute arbitrary Groovy code on the victim's machine during project import or build.

MitigationUpgrade to jadx version 1.5.6 or later which implements proper sanitization. Avoid opening or processing untrusted APK files with vulnerable jadx versions until patched.

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
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check jadx version
    Run 'jadx --version' or check the jadx JAR/library version in your installation directory. Compare the version number to the affected range: versions before 1.5.6 are vulnerable.
    Affected if The installed jadx version is 1.5.5 or earlier.
  2. Verify export to Gradle project feature usage
    Check whether you have used jadx's export functionality to generate Android Gradle projects from decompiled APKs. Look for generated 'app/build.gradle' files in output directories.
    Affected if You have exported decompiled APKs as Android Gradle projects using a vulnerable jadx version.
  3. Inspect generated build.gradle for unsanitized versionName
    If you have exported Gradle projects, open the generated app/build.gradle file and locate the 'versionName' property under the 'android { defaultConfig { ... } }' block.
    Affected if The versionName value contains unexpected characters, quotes, or Groovy syntax that was not in the original intended version string, indicating unsanitized insertion.
  4. Review source APK AndroidManifest.xml
    If available, compare the android:versionName value in the original APK's AndroidManifest.xml to what appears in the generated build.gradle file.
    Affected if The versionName in build.gradle differs from or contains injection characters not present in the original AndroidManifest.xml versionName.

You are affected if jadx version is below 1.5.6 AND you have exported a decompiled APK as an Android Gradle project using a malicious APK that contains payload in the android:versionName field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to jadx version 1.5.6 or later which implements proper sanitization. Avoid opening or processing untrusted APK files with vulnerable jadx versions until patched.

Recommended fix High confidence

jadx 1.5.6

  1. Identify your current jadx installation method (e.g., downloaded binary, build from source, package manager)
  2. If using a downloaded binary, navigate to the official jadx GitHub releases page and download version 1.5.6 or later
  3. If using a package manager (e.g., Homebrew, Chocolatey), update the package to version 1.5.6 or latest available
  4. If building from source, checkout tag or branch for version 1.5.6 and rebuild
  5. Replace the old jadx executable with the updated version
  6. Verify the upgrade was successful by running 'jadx --version' and confirming it shows 1.5.6 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42049 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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