Description

Information leak in Mobile in Google Chrome on on iOS prior to 152.0.7977.65 allowed a local attacker to obtain sensitive information via a crafted file. (Chromium security severity: Low)

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.5",
  "pubDate": "2026-08-25T21:17:51.737Z",
  "pubdate": "2026-08-25T21:17:51.737Z",
  "executiveSummary": "This vulnerability is an information leak flaw affecting Google Chrome on iOS. The issue stems from insufficient validation of file handling, which could allow a local attacker to access sensitive information residing within the application's environment. The vulnerability is classified by the Chromium project as having a Low security severity, primarily due to the specific preconditions required for exploitation.\nThe vulnerability manifests when the application processes a specially crafted file, leading to an unintended disclosure of data that should otherwise remain protected. To exploit this, an attacker must have local access to the device or the ability to deliver a malicious file to the target user, necessitating user interaction to initiate the processing of the file. Successful exploitation results in the unauthorized exposure of sensitive information, potentially compromising local data privacy. The risk is limited to local exploitation, meaning remote network-based attacks are not natively supported by this vector. Users are urged to update to the latest version of Google Chrome to remediate the exposure.",
  "technicalDetails": "The vulnerability resides within the file processing logic of Google Chrome for iOS, specifically affecting versions prior to 152.0.7977.65. The root cause pertains to improper handling or parsing of crafted file formats, which creates a side-channel or direct access path to information stored within the application's container.\nFrom an attack flow perspective, the exploitation process begins with the delivery of a malicious file to the target iOS device. This file is specifically engineered to exploit edge cases in the application's file parsing routines. When the user interacts with this crafted file—typically via the application's internal file viewer or an import mechanism—the parsing engine fails to correctly isolate the processing environment or enforce appropriate access controls.\nDuring the parsing phase, the vulnerable component attempts to read or map the file's contents. If the file structure is crafted to trigger an error state or an improper reference during the read operation, the application may inadvertently include surrounding memory contents or protected local files in the returned data object or display. This memory disclosure or file system read allows the local attacker to exfiltrate sensitive data, such as cached web content, local configuration artifacts, or potentially credentials if they are transiently accessible in the application's memory space.\nBecause the application operates within the iOS sandbox, the impact is confined to the data accessible to the Chrome application process. The exploit does not allow for full system compromise or privilege escalation outside the context of the browser container. The requirement for a local attacker to place a crafted file on the device and persuade a user to process it significantly limits the exploitability of this vulnerability in typical threat scenarios. No specific network protocols are involved, as the vulnerability is purely local and dependent on the interaction between the application's parser and the malformed file input."
}