Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-113199 Overview
CVE-2026-113199 is an out-of-bounds read vulnerability in the Payments component of Google Chrome. The flaw affects Chrome versions prior to 156.0.8078.47 and allows a remote attacker to read memory inside the renderer sandbox through a crafted HTML page. Chromium categorizes the issue as Medium severity and tracks it under CWE-125.
Exploitation requires user interaction, specifically a victim visiting an attacker-controlled page. Successful exploitation does not grant code execution but exposes sandboxed memory contents to the attacker. The disclosed information can facilitate follow-on attacks that chain additional browser vulnerabilities.
Critical Impact
Remote attackers can disclose sensitive memory contents from the Chrome renderer process by inducing a user to open a malicious HTML page.
Affected Products
- Google Chrome versions prior to 156.0.8078.47
- Chromium-based browsers using the vulnerable Payments component
- Desktop channels (Windows, macOS, Linux) distributed via the Chrome Stable channel
Discovery Timeline
- 2026-10-20 - CVE-2026-113199 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113199
Vulnerability Analysis
The vulnerability resides in the Payments subsystem of Chrome, which handles Web Payments API operations such as PaymentRequest processing and merchant validation. An out-of-bounds read occurs when the component accesses memory beyond the intended buffer boundary during the parsing or handling of payment-related data structures.
Because the read happens inside the renderer process, the attacker learns memory contents that reside within the Chrome sandbox. This category of flaw [CWE-125] does not corrupt memory or alter control flow. It leaks information that attackers can use to defeat Address Space Layout Randomization (ASLR) or stage subsequent exploitation attempts.
Root Cause
The root cause is missing or insufficient bounds checking within the Payments code path. When Chrome processes a crafted payment payload supplied by a malicious page, the component dereferences memory at an offset that falls outside the allocated buffer. The condition is deterministic for specific inputs, and no authentication is required to reach the vulnerable code.
Attack Vector
The attack vector is network-based and requires user interaction. An attacker hosts a crafted HTML page that invokes the Web Payments API with malformed parameters. When a victim visits the page using an unpatched Chrome build, the renderer processes the data and returns out-of-bounds memory contents to attacker-controlled JavaScript.
The vulnerability does not require elevated privileges or prior access. Delivery vectors include phishing links, malicious advertisements, and compromised third-party content embedded in otherwise trusted sites. See the Chromium Issue Report #562226316 for upstream technical details.
No verified proof-of-concept is publicly available. Refer to the
Chromium issue tracker for technical specifics once the report is
declassified by Google.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-113199
Indicators of Compromise
- Browser crash reports or renderer process terminations referencing the Payments component on Chrome builds older than 156.0.8078.47.
- Outbound connections from end-user hosts to newly registered domains serving pages that invoke the PaymentRequest API in unusual contexts.
- Web proxy logs recording HTML content with abnormally structured payment method data payloads delivered to end users.
Detection Strategies
- Inventory installed Chrome versions across managed endpoints and flag any build earlier than 156.0.8078.47 as vulnerable.
- Correlate web traffic telemetry with endpoint process data to identify renderer crashes immediately following navigation to untrusted sites.
- Apply URL reputation and category filtering at the proxy layer to detect delivery of crafted HTML pages hosted on low-reputation infrastructure.
Monitoring Recommendations
- Monitor Chrome auto-update status and alert when endpoints remain on outdated builds beyond a defined patch window.
- Collect browser crash telemetry and investigate repeated renderer failures tied to the payments module.
- Track user navigation to domains hosting payment-related JavaScript workflows outside of known-good merchant inventories.
How to Mitigate CVE-2026-113199
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later across all managed desktop endpoints.
- Force a browser restart after the update to ensure the patched binaries are loaded by all renderer processes.
- Audit third-party Chromium-based browsers for equivalent patched builds and apply vendor updates as they become available.
Patch Information
Google released the fix in the Chrome Stable channel update documented in the Google Chrome Stable Update advisory. Administrators should validate that endpoint builds report 156.0.8078.47 or higher in chrome://settings/help. The upstream fix is tracked under Chromium Issue Report #562226316.
Workarounds
- Restrict access to untrusted sites through enterprise web filtering until all endpoints are updated to the patched build.
- Disable the Web Payments API through enterprise policy where business workflows do not depend on it.
- Enforce Site Isolation and strict same-origin policies via Chrome Enterprise policies to reduce the value of leaked memory contents.
# Verify installed Chrome version on Linux endpoints
google-chrome --version
# Example Chrome Enterprise policy to force auto-update minimum version
# /etc/opt/chrome/policies/managed/chrome_version_policy.json
{
"TargetVersionPrefix": "156.0.8078.",
"DeviceAutoUpdateDisabled": false
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

