CVE-2026-58128 · Other
NO FIX YET
The Alan Android app (com.alanmobile version 1.450.0) exports a share receiver activity that builds a file path from an unsanitized display name, so a malicious co-installed app can write files outside the intended directory. An attacker can overwrite databases, preferences and WebView data inside the app's sandbox, enabling state tampering or code execution in the app's context.
first public Nov 4, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Users of the Alan Android app version 1.450.0 are exposed when another app installed on the same device sends a crafted share intent to the exported ShareReceiverActivity. Installs of other versions and devices without a malicious co-resident app are not shown to be affected by the sources. unknown for any fixed version.
Not affected if no-malicious-coresident-app, other-app-versions
Who cares alan, android, mobile
com.alanmobile 1.450.0No fix yet, per the sources.
Alan: Health Insurance for Android (com.alanmobile) 1.450.0 contains a path traversal vulnerability that allows a co-resident malicious application to write attacker-controlled files outside the intended directory via the exported ShareReceiverActivity, which uses an unsanitized _display_name value from a shared content URI to construct the destination file path. Attackers can send a crafted ACTION_SEND intent with a _display_name containing directory traversal sequences to overwrite sensitive files within the app's sandbox such as databases, shared_prefs, and WebView data, enabling state tampering or code execution in the app's context without authentication or user interaction.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.