Skip to main content
CVE-2025-7892VulnerabilityPublished

CVE-2025-7892: IDnow App · Improper Export of Android Application Components

Affects IDnow AppSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Alpinede.idnowpkg:apk/de.idnowOther threatsAffected
  • =9.0
  • =9.1
  • =9.2
  • =9.3
  • =9.4
  • =9.5
  • =9.6.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Restrict local device access: Enforce strict device management policies to prevent unauthorized installation of apps and limit physical access to devices running the IDnow App. 2. Use Mobile Device Management (MDM) solutions to monitor and control app permissions and detect suspicious activities related to exported components. 3. Employ application sandboxing and runtime protection tools that can detect and block unauthorized inter-app communication attempts targeting exported components. 4. Educate users about the risks of installing untrusted apps and the importance of device security hygiene. 5. Monitor for updates from IDnow and apply patches immediately once available. 6. As a temporary measure, consider isolating the IDnow App usage to dedicated devices or virtual environments where local access is tightly controlled. 7. Conduct regular security audits and penetration testing focusing on inter-app communication and exported components to identify similar risks proactively.

Description

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.

References

Community reviews

Loading reviews…