Loading story…
A high-severity vulnerability tracked as CVE-2026-42049 allows remote code execution in jadx when a user exports a malicious APK as an Android Gradle project and then opens or builds it. In versions before 1.5.6, jadx inserted the APK's AndroidManifest android:versionName value directly into the generated app/build.gradle Groovy template, letting an attacker craft metadata that breaks out of the expected string context and executes arbitrary Groovy code on the victim system.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
The CVE-2026-42049 entry was newly received by GitHub Security Advisories. The advisory describes a code execution flaw in jadx where a malicious APK can inject Groovy code through the AndroidManifest versionName during Gradle project export.
The jadx 1.5.6 release was published with multiple security fixes, including sanitizing string values used in exported Gradle scripts. This release is identified as the version that fixes CVE-2026-42049 affecting versions prior to 1.5.6.
A jadx source-code commit introduced sanitization for string values inserted into exported Gradle scripts, along with related security flags and tests. The change protects against unsafe template insertion in Groovy and Kotlin Gradle file generation.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
GitHub Security Lab reported that targeted, AI-assisted taskflows identified and disclosed 24 Android vulnerabilities in open-source applications. The workflows direct an open-source AI security agent to map mobile attack surfaces, locate entry points such as exported components and deep links, and evaluate Android-specific flaw classes; researchers emphasized that analysts must still validate findings and build proof-of-concept exploits because LLM output can overstate impact or produce false positives. In OsmAnd, an exported `MapActivity` accepted attacker-controlled intent extras that could silently import and replace application settings. A permissionless malicious app could use the issue to redirect map-tile or routing traffic and potentially infer a victim's location, routes, origin, and destination. In Wikipedia for Android, researchers found two inadequate hostname-suffix checks that could be chained through a `wikipedia://` deep link to load attacker-controlled content, expose Wikimedia cookies, and enable account takeover across Wikimedia projects.
Sep 29, 2026
Active exploitation has been observed against an Apache ActiveMQ remote code execution chain involving the Jolokia management API. VulnCheck reported canary-network hits tied to `CVE-2026-34197`, which was added to CISA's Known Exploited Vulnerabilities catalog, and said attackers are also using an unauthenticated variant that chains `CVE-2024-32114` with `CVE-2026-34197` to achieve zero-credential RCE. According to the reporting, `CVE-2024-32114` removes authentication from the Jolokia endpoint in ActiveMQ versions `6.0.0` through `6.1.1`, exposing the management interface to unauthenticated abuse. Technical details published by Horizon3.ai describe the RCE path through the Jolokia API, while VulnCheck said observed payloads invoked `addNetworkConnector` through Jolokia during exploitation. One captured payload referenced a private IP address, indicating the attacker activity may have reused a lab or proof-of-concept configuration, but the exploitation itself was confirmed in the wild. The combined reporting indicates that exposed ActiveMQ instances with vulnerable Jolokia configurations face immediate risk of unauthenticated remote compromise.
Jun 29, 2026
A bug bounty researcher chained an XML External Entity (XXE) flaw with a ZIP directory-traversal vulnerability in an unnamed Java web application that accepted a custom ZIP-based `.xyz` package. The application extracted uploaded archives and parsed an XML manifest, allowing a locally referenced external entity to expose `/etc/hosts` and support further directory enumeration. After identifying an application JSP template, the researcher used the archive extraction flaw—commonly known as **Zip Slip**—to overwrite it with a web shell, achieving remote code execution once cached content expired. The case demonstrates how unsafe XML parser defaults and insufficient archive-path validation can turn file-upload functionality into server compromise; the organization reportedly remediated the findings within 12 hours.
Sep 3, 2026