Unauthenticated network attackers can read and modify a subset of data held in Oracle Communications Billing and Revenue Management (BRM) Server, affecting versions 15.0.0.0.0, 15.0.1.0.0, 15.1.0.0.0 and 15.2.0.0.0. The flaw is reachable over TLS with no credentials or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, 6.5 Medium), and impact is bounded to low confidentiality and low integrity loss with no availability effect. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied, so real-world risk is driven mainly by whether the BRM TLS interface is reachable from untrusted networks. Because BRM is back-office telecom infrastructure normally segmented from the internet, practical exploitation generally presupposes an attacker already positioned on the hosting network segment, in a partner-connected environment, or against an improperly exposed deployment.
Unauthenticated remote attackers can cause limited unauthorized data modification and partial denial of service in Oracle Java SE and GraalVM deployments by supplying crafted data to APIs in the Utility component. Affected releases include Oracle Java SE 8u503, 8u503-perf, and 11.0.32.1; Oracle GraalVM for JDK 17.0.20.1 and 21.0.12.1; and Oracle GraalVM Enterprise Edition 21.3.19.1.1. Oracle disclosed the issue in its October 2026 Critical Patch Update, and no public exploit has been identified at time of analysis.
Authenticated low-privileged users can create, modify, or delete critical data in the Siebel CRM Deployment Server Infrastructure component of Oracle Siebel CRM versions 17.0 through 26.9 by sending crafted requests over the HTTP interface. The flaw is rated CVSS 3.1 6.5 with an integrity-only impact (C:N/I:H/A:N) and is easily exploitable once a valid low-privilege credential or session is obtained - it is not confirmed as unauthenticated despite the 'Authentication Bypass' tag attached to the report. No public exploit code or confirmed active exploitation (CISA KEV) is identified at time of analysis, making this a moderate-priority integrity risk concentrated on internet-facing Siebel application servers.
Unauthenticated HTTP requests can modify some data and cause a partial denial of service in the QAS component of PeopleSoft Enterprise PeopleTools 8.61 through 8.63. The CVSS 3.1 score is 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L), reflecting low integrity and availability impact with no confidentiality impact. No public exploit was identified at time of analysis, and real-world exposure depends on whether the QAS HTTP interface is reachable from untrusted networks.
Untrusted input that reaches Java's JGSS (GSS-API / Kerberos) security services can hang or repeatedly crash a JVM and, to a limited degree, alter data the component handles, affecting Oracle Java SE 8u503, 8u503-perf and 11.0.32.1, Oracle GraalVM for JDK 17.0.20.1 and 21.0.12.1, and Oracle GraalVM Enterprise Edition 21.3.19.1.1. Oracle scores this 6.5 on an AV:N/AC:H/PR:N/UI:N vector with C:N/I:L/A:H - no credentials or user interaction are needed, but the high attack complexity means successful exploitation depends on crafted tokens combined with timing or state conditions rather than one deterministic request, and realistic exposure is confined to deployments that actually feed attacker-controlled data into the JGSS path (for example a web service supplying data to those APIs, or sandboxed Web Start/JApplet code loading untrusted content). No public exploit code and no CISA KEV entry were identified at time of analysis, so this reads as a lower-priority, difficult-to-exploit hardening item - availability-weighted but not an urgent, actively exploited threat.
Oracle Payroll in Oracle E-Business Suite 12.2.3 through 12.2.15 allows an authenticated low-privilege attacker with network access to the Payroll HTTP interface to create, delete, or modify critical payroll data through the Element Types, Links, and Entries component. This is a moderate-priority integrity flaw: confidentiality and availability are unaffected, and exploitation requires valid EBS credentials rather than anonymous access. No public exploit was identified at time of analysis.
Improper bounds handling in the Skia graphics library lets a remote attacker who convinces a Chrome-for-Android user to open a crafted HTML page corrupt memory and read data from inside the renderer sandbox. The flaw affects Chrome on Android builds prior to 156.0.8078.47 and requires user interaction (UI:R) but no credentials or non-default configuration (PR:N), with the assessed impact limited to confidentiality loss (C:H) rather than code execution or sandbox escape. Google rates the underlying bug Critical internally and has shipped a fixed build; EPSS is low at 0.24% (14th percentile) and there is no KEV listing and no public exploit code identified at time of analysis.
Adjacent-network attackers can trigger a hang or repeatable full crash of the Oracle Database Server RDBMS component in versions 23.4.0 through 23.26.3, producing a complete denial of service. The flaw is easily exploitable - low complexity, no authentication, and no user interaction - but is gated by a network-adjacency precondition: the attacker must sit on the same physical communication segment (Layer-2/local network) as the database hardware, so it is not reachable across routed or internet boundaries. Impact is availability-only (CVSS 3.1 6.5, AV:A/AC:L/PR:N/UI:N/C:N/I:N/A:H); no public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS or KEV data was supplied.
Denial of service in Oracle MySQL Server and MySQL Cluster Group Replication allows an unauthenticated attacker on the same Layer-2 network segment to hang or repeatedly crash the database service. The flaw affects Group Replication GCS deployments in MySQL Server 8.4.0-8.4.12, 9.7.0-9.7.3, and 26.7.0-26.7.1 and MySQL Cluster 8.0.0-8.0.49, 8.4.0-8.4.12, 9.7.0-9.7.3, and 26.7.0-26.7.1; standalone instances without Group Replication enabled are not exposed. No public exploit was identified at time of analysis, and impact is limited to availability with no confidentiality or integrity effect.
Memory corruption in ANGLE within Google Chrome on Windows prior to 156.0.8078.47 can allow a remote attacker to potentially read memory inside the browser sandbox when a victim loads a crafted HTML page. The issue is medium severity (CVSS 6.5) and requires user interaction, with confidentiality impact only and no indicated sandbox escape or code execution; no public exploit identified at time of analysis and EPSS is low at 0.23% (13th percentile). Google has released a vendor patch in Chrome 156.0.8078.47.
Memory corruption in Google Chrome's Extensions component before version 156.0.8078.47 can let a remote attacker read memory inside the browser sandbox when a victim loads a crafted HTML page. Exploitation requires user interaction - the victim must visit or be redirected to the malicious page - and the assessed impact is confidentiality-only, with no code execution, data modification, or crash from this bug alone, making it most relevant as a chaining primitive. No public exploit code was identified at time of analysis, EPSS is low at 0.23%, and Google rates the Chromium security severity as Medium.
Chrome Installer on macOS before 156.0.8078.47 contains an out-of-bounds read that can be triggered when a victim opens a crafted HTML page, potentially exposing memory inside the browser sandbox. Exploitation requires user interaction and no privileges, but the independent assessment limits confidentiality impact to Low because readable data remains inside the sandbox and no sandbox escape is demonstrated. No public exploit identified at time of analysis and no CISA KEV entry appears in the supplied data; EPSS is 0.23% (13th percentile) and the vendor has released Chrome 156.0.8078.47.
Out-of-bounds memory read in Google Chrome on Windows before 156.0.8078.47 allows an unauthenticated remote attacker who convinces a victim to load a crafted HTML page to read memory inside the renderer sandbox. Chromium rates it Medium (CVSS 6.5, C:H/I:N/A:N), and the impact is strictly a confidentiality leak bounded by the sandbox, with no integrity or availability impact, no code execution, and no sandbox escape described. Exploitation requires user interaction, EPSS is low at 0.23% (13th percentile), no public exploit or CISA KEV entry was identified at time of analysis, and a vendor patch is available.
Memory disclosure inside the browser sandbox in Google Chrome for iOS versions prior to 156.0.8078.47 allows a remote attacker to read memory via a crafted HTML page that exercises the SignIn code path. Attackers must convince a victim to navigate to an attacker-controlled page (UI:R), but no authentication or special configuration is needed; the impact is limited to confidentiality of memory within the renderer sandbox, with no sandbox escape or code execution. Exploitation risk is currently low - EPSS is 0.23% (13th percentile), no public exploit code has been identified at time of analysis, and the issue is not in CISA KEV; a vendor patch (156.0.8078.47) is available.
An out-of-bounds memory read in Chrome's Dawn WebGPU implementation (CVE-2026-113322) lets a remote attacker who convinces a victim to open a crafted HTML page read memory inside the renderer sandbox. Only Chrome builds earlier than 156.0.8078.47 are affected, and exploitation requires user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, 6.5), with impact limited to confidentiality - no memory write, code execution, or sandbox escape is described. At time of analysis there is no confirmed active exploitation and no public exploit code identified, and EPSS is low at 0.23% (13th percentile); a vendor patch is already available, which materially reduces real-world exposure.
Out-of-bounds memory read in Google Chrome's Bluetooth component (all builds prior to 156.0.8078.47) allows remote attackers to disclose memory contents from inside the renderer sandbox by getting a victim to load a crafted HTML page. Exploitation is remote, low-complexity, unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, base 6.5), but requires the target to visit or render the attacker's page, and grants only confidentiality impact - no memory write, code execution, or service disruption on its own. Chromium rates the issue High severity; EPSS is 0.23% (13th percentile) and no public exploit code or confirmed active exploitation was identified at time of analysis. Affected users are those on Chrome builds older than 156.0.8078.47, including ChromeOS devices tracked by the parallel stable-channel advisory.
Out-of-bounds read in Google Chrome's Media component (fixed in 156.0.8078.47) lets a remote attacker read memory inside the renderer sandbox by convincing a user to open a crafted HTML page that feeds malformed media data to Chrome's parsing pipeline. Exploitation is unauthenticated (PR:N) but requires user interaction (UI:R), and the information leak is bounded by the renderer sandbox, so a separate sandbox escape would be required to reach host memory; confidentiality impact is rated High while integrity and availability are unaffected. No public exploit code or active exploitation was identified at time of analysis (EPSS 0.23%, 13th percentile), and the vendor has released a fixed build, so exposure is largely limited to browsers that have not yet auto-updated.
Out-of-bounds read in the Offline component of Google Chrome on Android allows a remote attacker who convinces a user to open a crafted HTML page to read memory inside the renderer sandbox, exposing potentially sensitive process data. Only Android builds prior to 156.0.8078.47 are affected; the CVSS 3.1 score is 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), so exploitation requires user interaction with attacker-controlled content and yields information disclosure only - no code execution or sandbox escape is described. EPSS is low at 0.23% (13th percentile) and no public exploit code was identified at time of analysis; this is a routine patch-management item, not an emergency, with a vendor fix already shipped in Chrome 156.0.8078.47.
Memory corruption in the PDF component of Google Chrome on Android (versions prior to 156.0.8078.47) allows a remote, unauthenticated attacker to potentially read memory inside the browser sandbox by enticing a victim to open a crafted HTML page that renders a malicious PDF. The impact is confined to information disclosure within the existing sandbox - there is no sandbox escape, memory write, or code execution described - and exploitation requires user interaction, which together with Android-only platform specificity keeps this at medium severity. No public exploit code or confirmed active exploitation was identified at time of analysis, and EPSS is low at 0.23% (13th percentile); Google rates the Chromium security severity as Medium and a vendor patch is available.
Unauthorized access to critical data in Oracle Siebel CRM's Siebel Apps - Financial Services (Financial Accounts component) is possible for unauthenticated remote attackers in versions 17.0 through 26.9, although Oracle rates exploitation as difficult due to AC:H. Successful attacks could expose all accessible Financial Services data and permit limited unauthorized inserts, updates, or deletes, producing a CVSS 3.1 score of 6.5. No public exploit identified at time of analysis, and no CISA KEV entry was provided; risk is materially higher where the Financial Accounts HTTP interface is internet-facing rather than restricted to internal or VPN access.
Oracle Siebel CRM Deployment 17.0 through 26.9 contains a hard-to-exploit, unauthenticated HTTP-exposed weakness in the Server Infrastructure component that can give an attacker high confidentiality access and limited integrity impact. With CVSS 3.1 score 6.5 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N), the issue is constrained by high attack complexity and has no availability impact. No public exploit identified at time of analysis, and no CISA KEV entry was provided; Oracle's October 2026 Critical Patch Update is the vendor fix.
Stored cross-site scripting in the Brizy WordPress plugin 2.8.23 allows authenticated low-privilege users to inject script content that executes when another user views or renders the affected Brizy page content. Exploitation requires a WordPress account with at least low-level content-creation privileges and a second victim user who opens the crafted content; impact is limited to browser-context script execution rather than server compromise. This is a moderate, not top-priority issue, and no public exploit is identified at time of analysis, with no CISA KEV status indicated in the provided data.
Improper access control in Chrome's Ozone platform windowing/graphics layer (CWE-284) allows a remote attacker to leak sensitive browser information by getting a victim to load a crafted HTML page. All desktop Chrome builds prior to 156.0.8078.47 are affected and require user interaction (UI:R) with no authentication (PR:N), yielding confidentiality-only impact (C:H/I:N/A:N) for a CVSS 3.1 score of 6.5. Google confirmed and patched the issue in the 156.0.8078.47 stable channel release; no public exploit code or CISA KEV entry is associated with the CVE at time of analysis.
Memory corruption in the GPU component of Google Chrome on Android allows a remote attacker to read memory inside the GPU sandbox if a victim loads a crafted HTML page, with impact limited to confidentiality (out-of-bounds read) rather than code execution. Only Chrome for Android builds prior to 156.0.8078.47 are affected; the flaw requires user interaction (UI:R) and content must reach the GPU rendering/compositing path, such as WebGL. There is no public exploit identified at time of analysis despite the classic buffer overflow tag, and EPSS is low at 0.22% (12th percentile), making this a moderate-priority patch-and-move-on issue.
Out-of-bounds read in Google Chrome's CustomTabs component on Android (versions prior to 156.0.8078.47) lets a remote attacker who convinces a user to open a crafted HTML page read memory inside the renderer sandbox. Exploitation requires the victim to render attacker-controlled content in an in-app Custom Tab (UI:R) and there is no authentication requirement (PR:N), but the leak is confined to the sandboxed renderer and has no integrity or availability impact. There is no confirmed active exploitation (no CISA KEV listing) and no public exploit code identified at time of analysis; EPSS is 0.22% (12th percentile), consistent with a low operational priority, and a vendor patch exists in Chrome 156.0.8078.47.
Memory corruption in Google Chrome on Android before version 156.0.8078.47 lets a remote, unauthenticated attacker who convinces a victim to open a crafted HTML page potentially read memory from inside the browser sandbox. The flaw is an out-of-bounds memory access (CWE-119) scored CVSS 6.5 with C:H/I:N/A:N, so the demonstrated impact is information disclosure confined to the sandbox rather than code execution or a confirmed sandbox escape, and exploitation is gated by mandatory user interaction (UI:R) on an unpatched Android build. No public exploit code or active exploitation has been identified at time of analysis, EPSS is low at 0.22% (12th percentile), and Google has released a fixed build.
Memory corruption in the DevTools component of Google Chrome before 156.0.8078.47 permits a remote attacker to read memory within the renderer sandbox when a victim loads a crafted HTML page. Exploitation requires user interaction (the victim must navigate to the attacker's page) and no authentication, but the impact is bounded to disclosure inside the sandbox with no escape, no data modification, and no availability loss - which is why Chromium assigned a Low severity. There is no public exploit identified at time of analysis, and EPSS is very low at 0.22% (12th percentile), consistent with the low-severity, interaction-dependent nature of the flaw.
Out-of-bounds read in Google Chrome's Actor component (all desktop builds prior to 156.0.8078.47) allows a remote attacker to read memory inside the renderer sandbox when a victim is lured to a crafted HTML page. Exploitation requires user interaction - the victim must navigate to attacker-controlled content - and the impact is bounded to information disclosure within the sandbox, with no code execution, no cross-origin or cross-process read, and no integrity or availability effect; our assessment scores confidentiality as Low (CVSS 3.1 base ~4.3-5.4 range, NVD lists 6.5 with C:H) rather than the higher NVD value. Google rated the issue Medium (Chromium security severity), EPSS is low at 0.22% (12th percentile), and no public exploit code or CISA KEV entry was identified at time of analysis, so this is a moderate-priority fix rather than an emergency patch.
A memory-corruption flaw in the Speech component of Google Chrome builds prior to 156.0.8078.47 lets remote attackers read out-of-bounds memory within the renderer sandbox by luring a victim to a crafted HTML page. Because the impact is confidentiality-only (C:H/I:N/A:N) and confined to the sandboxed renderer (S:U), the issue alone cannot alter data or achieve code execution and would require chaining with a separate sandbox-escape bug to reach the host. Exploitation requires user interaction (UI:R) and no authentication; no public exploit code or active exploitation is confirmed, and EPSS is low at 0.22% (12th percentile), consistent with a moderate, low-priority risk.
Memory corruption in Google Chrome's Extensions component in builds prior to 156.0.8078.47 allows an unauthenticated remote attacker to read memory inside the browser sandbox when a victim opens a crafted HTML page, with no integrity or availability impact - disclosure is bounded to data reachable by the sandboxed process. Google rates the issue Medium (Chromium severity) even though the CVSS 3.1 score reaches 6.5 on the strength of C:H; exploitation requires user interaction (UI:R) and does not by itself achieve sandbox escape or code execution. No public exploit code has been identified at time of analysis and EPSS is low at 0.22% (12th percentile), consistent with a moderate-priority rather than high-urgency issue; a vendor patch is available in 156.0.8078.47.
Memory corruption in the Loader component of Google Chrome versions prior to 156.0.8078.47 allows a remote attacker to read memory inside the renderer sandbox by convincing a victim to load a crafted HTML page. Impact is confined to information disclosure within the sandbox - there is no indicated write primitive, sandbox escape, or code execution path - and exploitation requires mandatory user interaction (UI:R) with no authentication prerequisite. No public exploit code or active exploitation has been identified at time of analysis, and EPSS is low at 0.22% (12th percentile), consistent with an independent assessment lowering the vector to confidentiality-only impact (C:L).
Google Chrome builds before 156.0.8078.47 contain an out-of-bounds read in the FileSystem component that can expose renderer-process memory to a remote attacker who convinces a user to load a crafted HTML page. The assessed vector requires user interaction (UI:R) and no privileges (PR:N), but limits impact to confidentiality inside the browser sandbox rather than sandbox escape or code execution. Patch is available from the vendor, EPSS is low at 0.22% (12th percentile), and no public exploit was identified at time of analysis.
Memory corruption in Google Chrome's CacheStorage implementation, present in versions prior to 156.0.8078.47, allows a remote attacker to potentially read memory inside the renderer sandbox when a victim loads a crafted HTML page. The flaw is unauthenticated from the target's perspective (PR:N) and needs no non-default configuration, but it hinges on user interaction (UI:R) and is scoped to the renderer (S:U), with confidentiality-only impact and no demonstrated sandbox escape. Google's Chromium severity rating is High, EPSS is low at 0.22% (12th percentile), no public exploit code has been identified at time of analysis, and this is a moderate-priority issue rather than a top-tier emergency; a vendor patch is available in 156.0.8078.47.
Out-of-bounds memory read in Google Chrome's ANGLE graphics translation layer on Windows (versions prior to 156.0.8078.47) lets a remote attacker leak memory contents from inside the renderer sandbox by getting a victim to render a crafted HTML page. The flaw is unauthenticated from the network perspective but requires user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, 6.5), and because the disclosure is contained within the Chrome sandbox it yields confidentiality impact only - no code execution, no integrity or availability effect, and no host escape. No public exploit code has been identified at time of analysis, EPSS is low at 0.22% (12th percentile), and the issue is not in CISA KEV; Google rates it High severity and has shipped a fixed build, so this is a moderate-priority patch-and-move-on item rather than an emergency.
Memory corruption in the Core component of Google Chrome on macOS (versions prior to 156.0.8078.47) allows a remote, unauthenticated attacker to read memory inside the renderer sandbox by getting a victim to render a crafted HTML page. Exploitation is user-driven (UI:R) and platform-limited to macOS; the reported impact is information disclosure bounded by the Chrome sandbox, not code execution or sandbox escape, so real-world harm would typically require chaining with a separate escape bug. There is currently no public exploit identified at time of analysis and the EPSS score is only 0.22% (12th percentile), but a vendor fix is available and Chromium rates the issue Medium severity.
Information disclosure in Google Chrome's font handling allows a remote, unauthenticated attacker to read memory inside the renderer sandbox by convincing a victim to load a crafted HTML page containing a malformed font. All desktop Chrome builds prior to 156.0.8078.47 are affected, and because font parsing is part of normal page rendering, no special configuration is required beyond the victim visiting the attacker's page (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N). There is no public exploit code identified at time of analysis and the flaw is not in CISA KEV; EPSS is 0.22% (12th percentile), consistent with a low-urgency, sandbox-confined memory leak that Google itself rated Low severity.
Out-of-bounds read in Google Chrome's SiteIsolation component affects desktop builds prior to 156.0.8078.47 and lets a remote attacker disclose memory contents confined to the renderer sandbox by convincing a victim to load a crafted HTML page. Successful exploitation requires user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) and yields confidentiality impact only - no memory corruption, code execution, or sandbox escape is established by this bug. Risk is moderate and bounded: EPSS is just 0.22% (12th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis, though a vendor patch is available.
Memory corruption in Google Chrome's BrowserTag component allows remote unauthenticated attackers to trigger a limited memory read inside the renderer sandbox by convincing a victim to load a crafted HTML page (UI:R). Versions prior to 156.0.8078.47 are affected; Google rates the issue Low, and the assessed impact is limited confidentiality (C:L) with no integrity or availability effect despite the recorded 6.5 CVSS score. EPSS is 0.22% (12th percentile), and no public exploit was identified at time of analysis.
Memory corruption in the DevTools component of Google Chrome before 156.0.8078.47 can allow a remote attacker to read memory inside the renderer sandbox when a victim loads a crafted HTML page. Exploitation requires user interaction and is confined to in-sandbox information disclosure; it does not by itself provide sandbox escape or code execution. No CISA KEV entry or public exploit was identified at time of analysis, and EPSS is low at 0.22% (12th percentile).
Out-of-bounds read in Google Chrome's Extensions component affects builds prior to 156.0.8078.47 and allows a remote, unauthenticated attacker to read memory inside the Chromium sandbox when a victim loads a crafted HTML page. Exploitation requires user interaction (UI:R) and is bounded to information disclosure within the sandbox rather than code execution or host compromise. No public exploit was identified at time of analysis, EPSS is low at 0.22% (12th percentile), and a vendor patch is available in Chrome 156.0.8078.47; this is a moderate, not urgent, priority.
Memory corruption in Google Chrome versions before 156.0.8078.47 can let remote, unauthenticated attackers read memory inside the renderer sandbox when a victim loads a crafted HTML page. The flaw is limited to information disclosure within the sandbox, with no established code execution, data modification, denial of service, or sandbox escape, and exploitation requires user interaction. Vendor-released patch: 156.0.8078.47; EPSS is 0.22% (12th percentile); no public exploit identified at time of analysis.
Editors in ApostropheCMS who can import a content type but lack that type's publish role can use the import-export module's write helpers to create, replace, or remove published document variants, bypassing normal publish-permission and lifecycle checks. The flaw is an authenticated, missing-authorization issue (CWE-862, CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) affecting ApostropheCMS core before 4.34.0 when paired with @apostrophecms/import-export before 3.7.1. It is most relevant to deployments that intentionally separate import rights from publication rights; no public exploit code or confirmed active exploitation was identified at time of analysis.
Memory disclosure inside the Chrome renderer sandbox affects Google Chrome versions prior to 156.0.8078.47; a remote attacker can trigger it only when the victim loads a crafted HTML page, yielding read access to sandboxed process memory with no integrity or availability impact. No public exploit identified at time of analysis, and EPSS is low at 0.22% (11th percentile). Google has released Chrome 156.0.8078.47 as the fixed version.
An out-of-bounds read in Chrome's ANGLE graphics backend on Windows lets a remote attacker disclose renderer memory by getting a victim to load a crafted HTML page that exercises the WebGL/GPU rendering path. Only Windows installations prior to 156.0.8078.47 are affected, and exploitation requires user interaction - the target must navigate to the attacker's page - with the leak confined to memory inside the renderer sandbox, so there is no code execution, no integrity or availability impact, and no sandbox escape by itself. Google's internal rating is High, but the practical risk is moderate (CVSS 6.5, EPSS 0.22% / 11th percentile) and no public exploit was identified at time of analysis; the flaw is fixed in the 156.0.8078.47 stable channel release.
Memory corruption in the iOSWebView component of Google Chrome for iOS (versions prior to 156.0.8078.47) allows a remote attacker who convinces a victim to load a crafted HTML page to read memory inside the renderer sandbox. Only the iOS build is affected - desktop and Android Chrome are out of scope - and the assessed impact is confidentiality-only (C:H/I:N/A:N) with no sandbox escape or code execution. No public exploit code or active exploitation is identified at time of analysis, and EPSS is low at 0.22% (11th percentile), though the vendor has released a patched build.
Memory disclosure in Google Chrome's Chromoting component allows a remote, unauthenticated attacker to read memory within the browser sandbox when a victim opens a crafted HTML page. The issue affects Chrome versions prior to 156.0.8078.47 and requires user interaction; the assessed impact is confidentiality-only, with no sandbox escape, code execution, integrity, or availability effect. EPSS is low at 0.22%, no public exploit has been identified at time of analysis, and a vendor patch is available.
Memory corruption in Google Chrome on iOS (versions prior to 156.0.8078.47) can let a remote attacker read memory inside the browser sandbox when a victim loads a crafted HTML page during Navigation processing. Exploitation requires user interaction and affects only the iOS build; it does not provide a sandbox escape, write access, or denial of service. No public exploit was identified at time of analysis, EPSS is low at 0.22% (11th percentile), and the vendor has released Chrome 156.0.8078.47 as the fix.
Information disclosure in ANGLE, the graphics translation layer bundled with Google Chrome on Windows, affects releases prior to 156.0.8078.47. A remote attacker who convinces a user to load a crafted HTML page can exercise the vulnerable rendering path and leak sensitive process memory or cross-origin data; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, 6.5) confirms confidentiality-only impact that requires user interaction, with no privileges or authentication needed and default Chrome configurations exposed because ANGLE is the standard graphics backend on Windows. No public exploit code or confirmed active exploitation was identified at time of analysis, and Google rates the issue Chromium security severity Medium.
Memory corruption in the Autofill component of Google Chrome prior to 156.0.8078.47 lets a remote, unauthenticated attacker read memory beyond intended bounds inside the renderer sandbox by convincing a victim to load a crafted HTML page. Successful exploitation requires user interaction (CVSS UI:R) and yields only information disclosure within the sandbox - confidentiality impact is high but there is no integrity or availability impact, no scope change, and no direct path to host compromise without chaining a separate sandbox escape. No public exploit code has been identified at time of analysis and EPSS is low at 0.22% (11th percentile), though vendor-released patches are available and should be applied as routine hygiene rather than emergency response.
Out-of-bounds read in Google Chrome before 156.0.8078.47 allows remote attackers to potentially read limited process memory inside the renderer sandbox when a victim navigates to a crafted HTML page. Exploitation is unauthenticated but requires user interaction (UI:R), and the assessed impact is low confidentiality only-no sandbox escape, code execution, integrity, or availability effect was assessed. No public exploit identified at time of analysis and no CISA KEV listing is present; EPSS is low at 0.22%, and Google has released a fixed build.