Loading vulnerability…
A vulnerability classified as problematic has been found in IDnow App up to 9.6.0 on Android. This affects an unknown part of the file AndroidManifest.xml of the component de.idnow. The manipulation leads to improper export of android application components. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is an Android application written in Kotlin, structured as a standard Android Studio project. The main exploit logic resides in 'app/src/main/java/com/safeapp/cutecat/MainActivity.kt'. The app presents a login form to the user, collects a username and password, and sends them as GET parameters to the hardcoded endpoint 'http://192.168.56.1:8080/'. The response from the server is displayed in a Toast message. The exploit demonstrates a proof-of-concept for CVE-2025-7892, likely targeting a vulnerability in a web application's login form at the specified IP address. The repository includes standard Android project files, build scripts, and resources, but the only network endpoint fingerprinted is the hardcoded local IP address. No payload beyond the credential submission is present, and there is no evidence of weaponization or advanced exploitation. The exploit is a POC and requires a vulnerable service running at the specified endpoint.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.