PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-113115 Google CVE debrief

A use-after-free vulnerability in Google Chrome's Transactions Platform prior to version 156.0.8078.47 allows remote attackers to execute arbitrary code within the sandbox via a crafted HTML page. This issue, classified as Medium severity by Chromium, was patched in a stable channel update. Chrome users should verify their version and update to 156.0.8078.47 or later to mitigate this vulnerability.

Vendor
Google
Product
Chrome
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-20
Original CVE updated
2026-10-20
Advisory published
2026-10-20
Advisory updated
2026-10-20

Who should care

Chrome users, particularly those with critical systems or sensitive data, should verify their version and update to 156.0.8078.47 or later to mitigate this vulnerability. IT administrators and security teams responsible for Chrome deployments should prioritize this update.

Why it matters

CVE-2026-113115 is a use-after-free vulnerability in Google Chrome's Transactions Platform that allows remote attackers to execute arbitrary code within the sandbox. Chrome users should update to version 156.0.8078.47 or later to mitigate this Medium-severity issue.

  • Remote code execution within the sandbox
  • Potential for crafted HTML page attacks
  • Medium severity classification by Chromium

Technical summary

A use-after-free vulnerability exists in Google Chrome's Transactions Platform prior to version 156.0.8078.47. This allows remote attackers to execute arbitrary code within the sandbox via a crafted HTML page. The issue is classified as Medium severity by Chromium and was patched in a stable channel update. Chrome users should verify their version and update to 156.0.8078.47 or later to mitigate this vulnerability. IT administrators and security teams should prioritize this update and review compensating controls for exposed systems.

Defensive priority

Medium

Recommended defensive actions

  • Verify Chrome version and update to 156.0.8078.47 or later
  • Monitor Chrome releases for future security updates
  • Implement sandboxing and isolation for critical systems
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and Chromium security bulletin provide details on the use-after-free vulnerability in Google Chrome's Transactions Platform. The stable channel update for desktop was released on October 20, 2026.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-113115 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-113115

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-113115 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-113115

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • CVE-2026-113115

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/113xxx/CVE-2026-113115.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://issues.chromium.org/issues/514018015

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.