CVE-2026-58128
Description
A flaw was found in Alan: Health Insurance for Android. This vulnerability allows a local malicious application on the same device to achieve arbitrary code execution or tamper with application data by overwriting sensitive files in the application's private storage. An attacker can exploit this issue without authentication or user interaction by sending a crafted share request containing directory traversal sequences to an exported activity that improperly sanitizes incoming file names.
Statement
This vulnerability is rated as Moderate severity because exploitation requires an attacker to execute a co-located malicious application on the same endpoint, limiting the blast radius to local file modification within the mobile application sandbox. Red Hat does not package, distribute, or support the third-party Android application com.alanmobile across any enterprise products or platforms. As a result, no Red Hat products are impacted by this flaw.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
