CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-68922

CVE-2026-68922: Arbitrary File Read via Path Traversal in MobSF ZIP/APK Icon Extraction

Amit Schendel
Amit Schendel
Senior Security Researcher

Aug 18, 2026·6 min read·65 visits

Executive Summary (TL;DR)

An authenticated directory traversal flaw in MobSF allows attackers to extract arbitrary files via a crafted AndroidManifest.xml within a ZIP or APK archive.

CVE-2026-68922 is a path traversal vulnerability in Mobile Security Framework (MobSF) prior to version 4.5.1. The vulnerability exists within the Android icon extraction process when analyzing uploaded ZIP or APK archives, allowing an authenticated attacker to read arbitrary files from the server.

Vulnerability Overview

The Mobile Security Framework (MobSF) serves as an automated environment for conducting static and dynamic analysis on mobile applications, including Android packages (APK) and compressed archives (ZIP).

During the static analysis stage of an uploaded file, MobSF performs an analysis of application metadata, including identifying and extracting the application icon from the binary resources. The logic responsible for this operation is implemented in mobsf/StaticAnalyzer/views/android/icon_analysis.py under the function find_icon_path_zip.

The vulnerability, registered as CVE-2026-68922, belongs to the Improper Limitation of a Pathname to a Restricted Directory category (CWE-22). An authenticated remote attacker can exploit this flaw to bypass the extraction directory boundaries, mapping relative directory traversal references to files located on the host filesystem.

This behavior exposes the underlying application environment to arbitrary file readout. Because files are copied into a publicly predictable and reachable download directory, security properties relating to configuration isolation and local file security are compromised.

Root Cause Analysis

The fundamental cause of CVE-2026-68922 is the implicit trust placed in the metadata extracted from an untrusted document's manifest. When analyzing an archive, MobSF extracts the path designated by the android:icon attribute inside AndroidManifest.xml.

To construct the local file path for extraction, the application performs prefix stripping and path joining operations. The code attempts to clean the relative icon path using the following Python instruction:

stripped_relative_path = icon_path.strip('/res')

This approach introduces a systematic logical bug. In Python, the str.strip() method removes all combinations of characters defined in the arguments rather than the exact literal substring. Consequently, a string such as /res/security.png undergoes partial stripping of its actual filename (resulting in ecurity.png). More critically, this operation fails to sanitize or impede standard relative traversal sequences containing ../ segments.

Once the stripped path is obtained, the application joins it with the resource directory (res_dir) using os.path.join(). In Python, os.path.join merges path elements sequentially. If the latter part of the argument contains path traversal tokens (e.g., ../../../../etc/passwd), the output resolves to a location outside the parent directory. Without an explicit check verifying that the resolved canonical path remains within the bounds of res_dir, the application will validate the file existence and prepare it for retrieval.

Code Analysis

A review of the vulnerable implementation compared to the official fix highlights the logical gap and the remediation approach.

Vulnerable Implementation

def find_icon_path_zip(checksum, res_dir, icon_paths_from_manifest):
    # ... logs and checks ...
    for icon_path in icon_paths_from_manifest:
        if icon_path.startswith('@'):
            # ... resource handling ...
        elif icon_path.startswith(('res/', '/res/')):
            # BUG: strip() removes characters '/','r','e','s' individually, not as a string prefix
            stripped_relative_path = icon_path.strip('/res')
            # BUG: os.path.join resolves directory traversal sequences without containment checks
            full_path = os.path.join(res_dir, stripped_relative_path)
            if os.path.exists(full_path):
                return full_path

Patched Implementation

The patch introduces two critical sanitization utilities from mobsf.MobSF.security: is_path_traversal and is_safe_path. These functions ensure that arbitrary directory manipulation sequences are caught and blocked.

# From mobsf/StaticAnalyzer/views/android/icon_analysis.py
for icon_path in icon_paths_from_manifest:
    # Step 1: Detect explicit path traversal strings early
    if is_path_traversal(icon_path):
        logger.warning('Path traversal detected in icon path: %s', icon_path)
        continue
    
    # ... 
    elif icon_path.startswith(('res/', '/res/')):
        # Step 2: Safely compute the relative path without using str.strip()
        rel = icon_path.lstrip('/')
        if rel.startswith('res/'):
            rel = rel[len('res/'):]
        
        full_path = os.path.join(res_dir, rel)
        # Step 3: Validate that the resolved target path remains inside res_dir boundary
        if not is_safe_path(res_dir, full_path, icon_path):
            continue
        if os.path.exists(full_path):
            return full_path

By leveraging os.path.realpath to resolve symbolic links and canonical paths, is_safe_path ensures that all operations remain bounded to the extraction directory. The modification resolves both the fragile parsing and the directory breakout.

Exploitation

An attack targeting CVE-2026-68922 relies on an authenticated user's ability to upload a customized application package. The attacker structures a ZIP or APK payload containing a manipulated AndroidManifest.xml file.

Exploitation Walkthrough

  1. Payload Construction: The attacker compiles an archive where the android:icon attribute within the manifest points to a targeted file using relative directory traversal identifiers, e.g., res/../../../../../../etc/passwd.

  2. Analysis Submission: The attacker submits the archive to the static analysis upload API. The server receives the file, computes its MD5 checksum, and kicks off resource unpacking.

  3. Extraction & Relocation: When the backend invokes find_icon_path_zip, the traversal sequences resolve directly to the host filesystem file. Since the file exists on the filesystem and contains a matching suffix or can be resolved, the application proceeds to copy the file to the predictable public directory (DWD_DIR) named with the template format [md5_checksum]-icon.[extension].

  4. Exfiltration: The attacker fetches the exfiltrated document by making a GET request directly to /download/[md5_checksum]-icon.passwd.

Impact Assessment

The exploitation of CVE-2026-68922 enables arbitrary file reading capabilities with the system permissions of the user context running the MobSF process. If the application is deployed as root inside a container or directly on a host machine, an attacker could potentially capture configuration files, database credentials, environment variables, or private SSH keys.

> [!NOTE] > The severity is evaluated as Medium (CVSS 5.5) due to the prerequisite of user authentication. However, in environments with self-registration enabled or where API keys are widely distributed to CI/CD pipelines, this authentication requirement presents minimal barrier to entry.

File Existence Oracle

In addition to direct file download, the analysis report exposes an auxiliary side-channel. If the target file is read-protected or cannot be copied to the public downloads folder, the icon_path field in the resulting analysis metadata report still logs whether the system located the file. This creates an efficient file-existence oracle, allowing adversaries to map internal system directory hierarchies and verify the presence of security tooling, specific library packages, or administrative files.

Remediation

The primary remediation mechanism is upgrading the MobSF deployment to version 4.5.1 or later. The update introduces the path containment logic and correctly resolves the string parsing issue.

Immediate Workarounds and Mitigations

If an immediate software upgrade is not feasible, the following operational mitigations should be applied:

  • Host User Isolation: Run the MobSF service under a dedicated, low-privilege service account rather than as the root user. This limits file-read exposure exclusively to files readable by that account.

  • Network Access Restraints: Restrict the MobSF HTTP port to local network ranges or dedicated corporate VPN gateways. Disable public sign-up or registration pages on the instance.

  • Read-only Filesystems: If possible, mount critical host directories as read-only or omit them from the container mapping context altogether to prevent traverse access.

Technical Appendix

CVSS Score
5.5/ 10
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

Affected Systems

Mobile Security Framework (MobSF)
AttributeDetail
CWE IDCWE-22
Attack VectorNetwork (AV:N)
CVSS Score5.5 (Medium)
ImpactArbitrary File Read
Exploit StatusProof of Concept (PoC)
KEV StatusNot Listed
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Vulnerability Timeline

Vulnerability identified and reported to MobSF maintainers
2026-07-05
Patch commit pushed to GitHub
2026-07-05
Security advisory published (GHSA-8j49-mmcx-4mp5)
2026-08-18
CVE-2026-68922 assigned and published
2026-08-18

References & Sources

  • [1]GitHub Security Advisory GHSA-8j49-mmcx-4mp5
  • [2]Official Patch Commit 62563ca
  • [3]Pull Request #2627
  • [4]MobSF Release v4.5.1
  • [5]CVE-2026-68922 Record

More Reports

•about 1 hour ago•CVE-2026-114147
7.5

CVE-2026-114147: Denial of Service via Memory Leak in ASP.NET Core SignalR Redis Backplane

CVE-2026-114147 is a high-severity Denial of Service (DoS) vulnerability affecting ASP.NET Core and specifically the Microsoft.AspNetCore.SignalR.StackExchangeRedis scale-out provider across .NET 8.0, 9.0, 10.0, and 11.0 preview releases. The vulnerability originates from a string comparison mismatch between internal per-connection group collections and the centralized Redis channel subscription registry, compounded by a race condition during connection teardown. Remote unauthenticated attackers can exploit this flaw to leave orphaned connection contexts and active Redis pub/sub listeners pinned in memory, leading to unbounded memory exhaustion and application process termination.

Amit Schendel
Amit Schendel
0 views•10 min read
•about 2 hours ago•CVE-2026-114156
6.5

CVE-2026-114156: Path Equivalence Security Feature Bypass in Microsoft ASP.NET Core

CVE-2026-114156 is an improper resolution of path equivalence vulnerability (CWE-41) in Microsoft ASP.NET Core affecting .NET 11.0 preview releases and Microsoft Visual Studio 2026. The vulnerability stems from a discrepancy between how path prefix validation helpers (such as PathString.StartsWithSegments) and downstream routing mechanisms handle alternate path separators and percent-encoded characters. An unauthenticated remote attacker can exploit this mismatch over the network to bypass path-based authorization middleware and access restricted endpoints.

Amit Schendel
Amit Schendel
4 views•8 min read
•about 3 hours ago•CVE-2026-114157
7.5

CVE-2026-114157: Local Privilege Escalation via Race Condition in ASP.NET Core Kestrel Named Pipes Transport

CVE-2026-114157 is a high-severity local privilege escalation and security feature bypass vulnerability affecting ASP.NET Core on Microsoft Windows. The flaw resides in the Kestrel web server's Named Pipes transport layer (Microsoft.AspNetCore.Server.Kestrel.Transport.NamedPipes) and stems from a race condition (CWE-362) during broken pipe error recovery. When an active connection throws an IOException during handshake acceptance, the connection listener previously disposed of the broken NamedPipeServerStream instance before acquiring a replacement stream from its internal pool. This sequence created a momentary window where zero server instances of the named pipe existed in the Windows Named Pipe File System (NPFS). A local, low-privileged attacker can exploit this timing window to create a named pipe with the identical name and a permissive Discretionary Access Control List (DACL), hijacking subsequent inter-process communications and escalating privileges across security boundaries.

Amit Schendel
Amit Schendel
6 views•11 min read
•about 4 hours ago•CVE-2026-124194
6.5

CVE-2026-124194: Forced Authentication and NetNTLMv2 Credential Leakage in Microsoft Office Outlook

CVE-2026-124194 is a forced authentication and spoofing vulnerability in Microsoft Office Outlook caused by a missing user interface warning before dereferencing remote network paths (CWE-356). By embedding an attacker-controlled Universal Naming Convention (UNC) path within MAPI message properties such as PidLidReminderFileParameter, an unauthenticated remote attacker can force a victim's system to initiate an outbound SMB or WebDAV connection upon opening or previewing a crafted message. This automatic authentication handshake leaks the user's NetNTLMv2 hash, enabling offline password cracking or real-time NTLM relay attacks. The vulnerability was exploited in the wild as a zero-day prior to its remediation in Microsoft's November 2026 Patch Tuesday updates and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

Alon Barad
Alon Barad
16 views•10 min read
•about 4 hours ago•CVE-2026-114154
7.5

CVE-2026-114154: Denial of Service in ASP.NET Core HttpSys Request Header Processing

CVE-2026-114154 is a high-severity Denial of Service (DoS) and uncontrolled resource consumption vulnerability in the Microsoft.AspNetCore.Server.HttpSys component of ASP.NET Core. When processing an HTTP request that simultaneously contains a chunked Transfer-Encoding header, a Content-Length header, and an explicit X-Content-Length header, the server throws an unhandled ArgumentException during header normalization. In certain versions, subsequent exception handling attempts to dereference a disposed native request context, aborting error response dispatch and leaking unmanaged HTTP.sys request structures.

Amit Schendel
Amit Schendel
4 views•9 min read
•about 5 hours ago•CVE-2026-120778
7.3

CVE-2026-120778: Local Elevation of Privilege via Insecure Temporary Directory Handling and MSBuild Response File Hijacking in Microsoft .NET Aspire CLI

A local elevation of privilege vulnerability exists in the Microsoft .NET Aspire CLI (`Aspire.Cli`) versions 13.5.4 prior to 13.6.5. When executing SDK management commands (`aspire sdk generate`, `aspire sdk dump`, and `aspire sdk export`), the CLI creates temporary project directories inside the shared operating system temporary folder (such as `/tmp` on Unix-like systems) without restricting directory permissions or disabling MSBuild automatic response file resolution. A local, low-privileged attacker on a multi-user system can place a crafted `Directory.Build.rsp` file in the shared temporary directory hierarchy. When a victim user executes an affected Aspire CLI command, MSBuild traverses upward, ingests the attacker-controlled response file, and executes arbitrary commands in the security context of the victim user.

Alon Barad
Alon Barad
4 views•10 min read