Google

Stored XSS in PrivateBin versions up to 2.0.4 allows an anonymous attacker to attach a text/html file to a paste such that, when a victim opens the download link in a new tab, the attacker's inline JavaScript executes in the PrivateBin instance's web origin with full same-origin capability including localStorage access and same-origin fetch. This is an incomplete fix for CVE-2022-24833: the 2022 patch only sanitized the preview blob for SVG files but never updated the download link's blob, leaving all non-SVG active content types-including text/html-completely bypassing DOMPurify. A detailed proof-of-concept demonstrating exploitation with Playwright/Chromium automation is publicly available in GitHub Security Advisory GHSA-f2xf-7x3g-4272; no public exploit identified as confirmed actively exploited per CISA KEV.

Origin validation failure in Microsoft Edge (Chromium-based) enables unauthenticated remote attackers to bypass browser security features, resulting in limited cross-origin confidentiality and integrity impacts. The vulnerability (CWE-346) exploits improper validation of request origins within the Chromium-based browser engine and requires user interaction to trigger. No public exploit code has been identified at time of analysis, and Microsoft has released a patch via the MSRC update guide.

Remote code execution in Microsoft Edge (Chromium-based) is enabled by a type confusion vulnerability (CWE-843) that can be triggered when a user visits attacker-controlled web content. All versions of Edge (Chromium-based) are affected per the wildcard CPE, with full confidentiality, integrity, and availability impact at a CVSS 8.8. A vendor patch is available via the Microsoft Security Response Center; no active exploitation has been confirmed and no public exploit code has been identified at time of analysis.

Use-after-free (CWE-416) in Microsoft Edge (Chromium-based) allows a remote, unauthenticated attacker to crash the browser through a crafted webpage, resulting in a denial-of-service condition. Critically, the CVE description claims code execution capability, but the CVSS vector (C:N/I:N/A:L, score 4.3) directly contradicts this - a genuine RCE would produce C:H/I:H impact in the 8-9+ range; this discrepancy should be verified against the full MSRC advisory. No active exploitation has been confirmed and no public POC has been reported; a vendor patch is available via the Microsoft Security Response Center.

Spoofing via external file path control in Microsoft Edge (Chromium-based) enables a network-based, unauthenticated attacker to deceive users about the origin or content of resources rendered by the browser. The CVSS score of 6.5 (Medium) reflects a network-reachable attack requiring user interaction but no attacker privileges, with high confidentiality impact and no integrity or availability impact. No public exploit code has been identified and this CVE is not listed in the CISA KEV catalog; a vendor patch is available through Microsoft MSRC.

Parameter/argument delimiter injection in Microsoft Edge (Chromium-based) enables network-based code execution by an unauthenticated remote attacker who can induce a user to interact with malicious content. The flaw, classified under CWE-141, stems from insufficient sanitization of delimiter characters in parameter or argument handling within the browser, potentially allowing injected values to alter command or function execution semantics. Tags associated with this CVE include 'Authentication Bypass', suggesting the delimiter injection may also facilitate circumventing browser-level or web-application authentication controls in certain contexts. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch is available.

Incorrect authorization in Microsoft Edge (Chromium-based) allows a remote, unauthenticated attacker to disclose limited information and cause minor integrity impact by luring a user to attacker-controlled web content. The flaw stems from CWE-863, where Edge's authorization logic fails to correctly enforce access boundaries, permitting content-triggered data exposure within the browser's security context. No public exploit has been identified at time of analysis, and Microsoft has released a patch via the MSRC advisory.

NF registration poisoning in free5GC's Network Repository Function (NRF) lets attackers with SBI network access register forged Network Function profiles containing arbitrary, attacker-controlled service endpoint IPs, because the RegisterNFInstance handler performs no field validation against 3GPP TS 29.510. Legitimate NFs (AMF, SMF, AUSF, UDM, PCF, NSSF) then discover the fake profiles via NFDiscover and route control-plane signaling to the attacker, enabling interception, OAuth2 credential harvesting, and denial of service across the entire 5G core service mesh. Publicly available exploit code exists and the vendor has released a patch; the flaw is CWE-20 with a vendor CVSS 4.0 base score of 9.3 (Critical).

In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Treat zero-length cert chain as query for blob lengths When handling a PDH export, treat a zero-length userspace cert chain buffer as a request to query the length of the relevant blobs. Failure to account for the zero-length buffer trips a BUG_ON() when running with CONFIG_DEBUG_VIRTUAL=y due to trying to get the physical address of the ZERO_SIZE_PTR (returned by kzalloc() on the bogus allocation). kernel BUG at arch/x86/mm/physaddr.c:28 ! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 30 UID: 0 PID: 28580 Comm: syz.2.18 Kdump: loaded Tainted: G W 6.18.16-smp-DEV #1 NONE Tainted: [W]=WARN Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025 RIP: 0010:__phys_addr+0x16a/0x180 arch/x86/mm/physaddr.c:28 RSP: 0018:ffffc9008329fc80 EFLAGS: 00010293 RAX: ffffffff8179110a RBX: 0000778000000010 RCX: ffff8884e6992600 RDX: 0000000000000000 RSI: 0000000080000010 RDI: 0000778000000010 RBP: ffffc9008329fdf0 R08: 0000000000000dc0 R09: 00000000ffffffff R10: dffffc0000000000 R11: fffffbfff126d297 R12: dffffc0000000000 R13: 1ffff92010653fc8 R14: 0000000080000010 R15: dffffc0000000000 FS: 0000555556bec9c0(0000) GS:ffff88aa4ce1c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fd3159e7000 CR3: 00000004fbc44000 CR4: 0000000000350ef0 Call Trace: <TASK> [<ffffffff853d3869>] sev_ioctl_do_pdh_export+0x559/0x7a0 drivers/crypto/ccp/sev-dev.c:2308 [<ffffffff853d1fdd>] sev_ioctl+0x2cd/0x480 drivers/crypto/ccp/sev-dev.c:2556 [<ffffffff82549ebc>] vfs_ioctl fs/ioctl.c:52 [inline] [<ffffffff82549ebc>] __do_sys_ioctl fs/ioctl.c:598 [inline] [<ffffffff82549ebc>] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:584 [<ffffffff8630115f>] do_syscall_x64 arch/x86/entry/syscall_64.c:64 [inline] [<ffffffff8630115f>] do_syscall_64+0x9f/0xf40 arch/x86/entry/syscall_64.c:98 [<ffffffff81000136>] entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fd3158eac39 </TASK> Thankfully, the bug is benign outside of CONFIG_DEBUG_VIRTUAL=y as getting the physical address is just arithmetic, and the PSP errors out before trying to write to the garbage address (which it must, otherwise querying the blob lengths would clobber memory at pfn=0).

Cross-site scripting in the wallabag Android application (fr.gaulupeau.apps.InThePoche) through version 2.6.0 allows execution of attacker-controlled JavaScript within the app's WebView. Article content fetched from the /api/entries endpoint is rendered in a WebView without sanitization, meaning malicious markup embedded in saved articles executes in the application's security context. A publicly available proof-of-concept references the specific vulnerable source files in the upstream repository; no CISA KEV listing exists at time of analysis, but the CVSS 4.0 score of 8.8 with scope change indicators reflects elevated real-world risk.

Path traversal in flutter_file_picker's Android implementation (all versions through 10.3.10) allows a malicious Android app on the same device to write arbitrary files into the victim app's internal storage directories. The openFileStream() method in FileUtils.kt constructs file paths using the DISPLAY_NAME value returned by ContentResolver.query() without sanitization, making it trivially exploitable by a crafted ContentProvider that returns filenames containing ../ sequences. No public exploit has been identified at time of analysis; SSVC classifies exploitation as none and the attack is not automatable, keeping real-world risk constrained despite the clear code-level flaw.

Out-of-bounds read in V8, Chrome's JavaScript engine, enables remote code execution confined within the renderer sandbox on all platforms running Chrome prior to 151.0.7922.72. The flaw is triggered by a specially crafted HTML page, requiring only that a user visit a malicious site - no authentication or elevated privileges are needed from the attacker. No public exploit code has been identified and no active exploitation is confirmed; EPSS probability stands at 0.30%, aligning with SSVC's 'exploitation: none' classification despite the high CVSS score.

Reflected XSS in Netron desktop application versions 9.1.2 and earlier enables arbitrary JavaScript execution within the Electron/Chromium renderer by injecting payloads into unsanitized model node names, types, and attribute descriptions. Reported by HiddenLayer, the vulnerability allows an attacker who can deliver a crafted ML model file to hide graph nodes, conduct local network port scanning, and - when chained with a Chrome n-day exploit - escalate to full Remote Code Execution on the victim's machine. No public exploit has been identified at time of analysis, and the CVE is not currently listed in the CISA KEV catalog.

Reflected XSS in Netron ≤9.1.2 desktop application executes attacker-controlled JavaScript when a user opens a specially crafted ML model file containing malicious node names, descriptions, or type labels. Because Netron is Electron-based, XSS runs in a privileged Chromium renderer context - enabling SSRF-style local port scanning and, when chained with an unspecified Chrome n-day vulnerability, potential remote code execution on the host. No public exploit confirmed at time of analysis, but HiddenLayer published a security advisory documenting the impact chain.

Reflected XSS in Netron desktop application versions ≤9.1.2 executes attacker-controlled JavaScript when a victim opens a crafted neural network model file containing malicious node names, type labels, or value descriptions. Because Netron runs on Electron (a Chromium-based runtime), the injected script operates within a privileged renderer process capable of port-scanning local networks and, with a separately-acquired Chrome n-day, achieving full remote code execution on the host machine. HiddenLayer reported the vulnerability and a vendor fix is available via GitHub commit cd14bad8c91; no public standalone exploit has been confirmed and this CVE does not appear in CISA KEV.

Server-Side Request Forgery (SSRF) in GitLab's AI Gateway component allows an authenticated user with Duo Agent Platform access to redirect outbound model requests to an attacker-controlled endpoint by injecting a crafted inline flow configuration that overrides the HTTP Host header. Exploitation results in exfiltration of Google Cloud Vertex cloud service credentials and private signing keys held by the AI Gateway, enabling an adversary to subsequently authenticate to GCP services outside GitLab's control. No public exploitation (CISA KEV) has been confirmed, but a publicly available exploit exists via a disclosed HackerOne report, materially increasing real-world risk.

Server-Side Request Forgery (SSRF) in GitLab AI Gateway allows authenticated users with Duo Agent Platform access to exfiltrate Google Vertex AI or AWS Bedrock cloud service credentials by injecting a malicious endpoint into crafted model metadata, causing the gateway to proxy requests - including cloud credentials - to an attacker-controlled server. All AI Gateway releases from 18.9.0 through 19.2.2 are affected across three version branches; GitLab has confirmed remediation. A public exploit exists per the HackerOne reference, and the CVSS Scope Change metric (S:C) reflects that successful exploitation extends compromise to external cloud infrastructure beyond the GitLab instance itself.

An issue in Time4 Popcorn for Windows <= 6.2.1.18 and Time4Popcorn for MacOS <= 6.2.1.17 and Time4Popcorn for Android <= 3.5.0.173 allows a remote attacker to execute arbitrary code via the updater.exe for windows, PT.updd on MacOS components

An issue in EcoOnline EHS (com.airsweb.v10) application for Android, version 0.2.499 allows a remote attacker to obtain sensitive information and execute arbitrary code via the AndroidManifest.xml component

Cross-tenant data exposure in Google Cloud Vertex AI Search for Commerce (versions prior to 2026-04-27) allowed an authenticated attacker who knew a victim's Google Cloud project number to read from and write to the Cloud Storage buckets used for BigQuery Import staging, because those bucket names were predictably derived rather than randomized. An attacker could reach another tenant's staged catalog data and import error logs, breaching data confidentiality and integrity across project boundaries. There is no public exploit identified at time of analysis, and Google fixed the issue server-side so no customer action is required.

Remote code execution in Google langfun before 0.1.2 arises because the default lf.query Python protocol evaluates model-generated Python expressions with no sandbox, letting remote unauthenticated attackers run arbitrary code in the host application by supplying crafted prompt inputs that steer the model into emitting executable code. Because langfun embeds directly in LLM-driven Python applications, any deployment that pipes untrusted prompt content through lf.query is exposed. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the CVSS 4.0 base score of 9.2 (CRITICAL) reflects full confidentiality, integrity, and availability impact.

Remote code execution in Google Cloud BigQuery Data Transfer Service (versions prior to the 2026-05-01 service release) allows an authenticated tenant user to run arbitrary code inside the managed connector container and escalate privileges within the tenant project by supplying crafted parameters in a JDBC connection string routed through the bundled CData JDBC driver. Rated CVSS 4.0 9.4 (Critical) with a scope change to subsequent systems, the flaw was fixed server-side by Google on 1 May 2026 and requires no customer action. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV.

Stored Cross-Site Scripting in the Reviews and Rating - Google Reviews WordPress plugin (all versions through 5.10) allows authenticated Contributors to inject arbitrary JavaScript via the wp_display() shortcode handler's unsanitized html_tags parameter. The malicious script persists server-side and executes in the browsers of any users who subsequently load the affected page, enabling session hijacking, credential theft, or unauthorized actions under the victim's identity. No confirmed active exploitation or public exploit code has been identified at time of analysis; the primary risk driver is the low privilege bar required - Contributor-level access - which is commonly available on multi-author or open-registration WordPress sites.

Improper authorization in Myna Point's Android Intent handler allows a co-installed malicious application to invoke the app's custom URL scheme handler without caller validation, triggering arbitrary JavaScript execution within the app's WebView context. All versions of the Japanese government digital identity application (Digital Agency, CPE wildcard) appear affected per JVN advisory JVN67155805. No public exploit identified at time of analysis, though the attack surface is inherently local and requires a malicious app on the same device.

Sandbox-escaping remote code execution is possible in Google Chrome for iOS before 152.0.7977.65, where a use-after-free in the Sync component can be triggered by a victim visiting a crafted HTML page, potentially letting a remote attacker run arbitrary code outside the renderer sandbox. Google has shipped a fixed stable build, and there is no public exploit identified at time of analysis; the flaw is not listed in CISA KEV and SSVC records exploitation status as none. Notably, Chromium's own severity rating for this bug is Low, which stands in sharp contrast to the 9.6 CVSS score in the input.

Skia, the 2D graphics rendering library embedded in Google Chrome's renderer process, contains an uninitialized resource flaw that allows remote attackers to read stale sandbox memory contents by inducing a victim to visit a crafted HTML page. All Chrome versions prior to 152.0.7977.65 are affected across desktop platforms, with confidentiality impact confined to the renderer sandbox. The EPSS score of 0.19% (9th percentile) and absence from CISA KEV reflect low observed exploitation pressure, though such memory-read primitives are classically useful as components in multi-stage exploit chains targeting browser memory.

Incorrect reference resolution in the CustomTabs component of Google Chrome for Android (all versions prior to 152.0.7977.65) allows a remote, unauthenticated attacker to bypass Android system access restrictions by delivering a crafted HTML page. The integrity impact is limited (I:L, S:U) with no confidentiality or availability consequence. No public exploit code exists and exploitation status is confirmed as none by SSVC assessment, placing this squarely in standard patch-cycle priority rather than emergency response.

Cookie input validation bypass in Google Chrome prior to 152.0.7977.65 enables an attacker who has already compromised the renderer process to circumvent web origin policy restrictions. Exploitation requires a second-stage attack where a separately compromised renderer is leveraged via a crafted HTML page, making this a chained exploit component rather than a standalone initial-access vulnerability. No public exploit code has been identified and CISA has not listed this in the KEV catalog; EPSS at 0.18% (8th percentile) and a 'Low' Chromium-internal severity rating reflect limited real-world exploitation risk.

Sensitive information disclosure in Google Chrome on Windows prior to 152.0.7977.65 exposes confidential browser or system data to remote attackers who trick users into visiting a crafted HTML page. The root cause is improper input validation in Chrome's Network component (CWE-20), enabling a network-accessible attacker to exploit the flaw without privileges, though social engineering is required to achieve user interaction. No public exploit code or CISA KEV listing is confirmed, and the EPSS score of 0.17% (7th percentile) reflects low current exploitation probability despite the High confidentiality impact in the CVSS rating.

Race condition in Google Chrome Enterprise on Windows prior to version 152.0.7977.65 enables an adjacent network attacker to potentially escape the browser sandbox and execute arbitrary code on the host system via crafted network traffic. No public exploit code has been identified and CISA has not listed this in the Known Exploited Vulnerabilities catalog. Despite a CVSS base score of 7.5, Google's Chromium team assigned an internal severity of Low, and SSVC analysis independently rates exploitation as none with non-automatable attack conditions - together suggesting constrained real-world impact relative to raw score.

Proxy functionality in Google Chrome on Windows prior to 152.0.7977.65 incorrectly implements specified behavior, enabling an adjacent-network attacker to intercept or infer sensitive information by sending crafted network traffic. The flaw is Windows-platform-specific and is classified by the Chromium security team as Low severity, consistent with the high attack complexity and adjacency requirement that constrain realistic exploitation. No public exploit code or active exploitation has been identified at time of analysis; EPSS probability is 0.13%, placing this in the 3rd percentile of exploitability.

Information disclosure in Google Chrome's Mobile component on iOS (all versions prior to 152.0.7977.65) allows a local attacker to read sensitive information by inducing the user to open a crafted file. Exploitation requires physical or logical local access to the device and user interaction, limiting the practical attack surface significantly. No public exploit code has been identified at time of analysis, and CISA SSVC rates exploitation as none with only partial technical impact.

Information disclosure in Google Chrome's Mobile component on iOS exposes sensitive data to local attackers operating via a local program, affecting all Chrome for iOS versions prior to 152.0.7977.65. The vulnerability is classified CWE-200 (Exposure of Sensitive Information) and carries a Chromium internal severity of Low, which aligns with SSVC's assessment of partial technical impact and non-automatable exploitation. No public exploit code exists and no active exploitation has been confirmed; the EPSS score of 0.18% (7th percentile) reflects minimal real-world exploitation pressure.

Web origin policy bypass in Google Chrome for Android before 152.0.7977.65 lets a malicious co-installed app abuse the CustomTabs component to escape same-origin restrictions and access content it should not. The flaw is a local privilege/authorization issue (Chromium-rated Low severity) requiring a second attacker-controlled app already present on the device; no public exploit has been identified and EPSS probability is very low (0.11%).

Incorrect DOM authorization in Google Chrome prior to 152.0.7977.65 enables remote unauthenticated attackers to potentially leak sensitive information by serving a crafted HTML page to a victim. The flaw is classified as CWE-863 (Incorrect Authorization), meaning Chrome's DOM implementation fails to properly enforce access controls for certain document-level resources. No public exploit code has been identified and EPSS sits at 0.17% (6th percentile), consistent with Chrome's own 'Low' severity rating despite the medium CVSS 6.5 score driven by the C:H metric.

Incorrect authorization in the Forms component of Google Chrome prior to version 152.0.7977.65 enables a remote unauthenticated attacker to obtain sensitive browser-held form data by directing a victim to a crafted HTML page. The CVSS 6.5 score reflects high confidentiality impact (C:H) with no integrity or availability consequence, consistent with a pure information disclosure primitive. No public exploit identified at time of analysis; EPSS of 0.17% at the 6th percentile and Chromium's own 'Low' internal severity rating together suggest low near-term exploitation likelihood despite the meaningful CVSS base score.

Missing authorization in Chrome's InterestGroups API allows a renderer-compromised attacker to bypass system access restrictions via a crafted PDF file. Affected are all Google Chrome versions prior to 152.0.7977.65 across desktop platforms. This is a chained exploit: a prerequisite renderer-process compromise must already exist before the InterestGroups flaw can be leveraged to escalate beyond sandbox constraints and achieve high integrity impact. No public exploit or CISA KEV listing exists; EPSS stands at 0.23% (13th percentile), reflecting very low exploitation probability in the wild.

Incorrect authorization (CWE-863) in Chrome's Browser component on Android allows remote attackers to bypass system access restrictions through social engineering and UI interaction. Affected versions are all Chrome releases for Android prior to 152.0.7977.65. The flaw carries only a limited integrity impact with no confidentiality or availability consequence, and Chromium's own severity rating of 'Low' is consistent with the very low EPSS score of 0.17% (7th percentile). No public exploit code exists and the vulnerability has not been added to the CISA KEV catalog.

System access restriction bypass in Google Chrome Mobile on iOS prior to version 152.0.7977.65 enables a remote attacker to circumvent platform-level security controls by luring a victim to a specially crafted HTML page. The flaw stems from improper input validation (CWE-20) in Chrome's iOS mobile implementation and results in a low-integrity impact with no confidentiality or availability consequence. No public exploit code or active exploitation has been identified at time of analysis; EPSS probability is 0.22% (12th percentile), and CISA SSVC classifies exploitation as none and technical impact as partial, consistent with a low-priority patching posture for most organizations.

Race condition in Chrome's Extensions subsystem (versions prior to 152.0.7977.65) enables a remote attacker to bypass system access restrictions via a crafted Chrome extension, achieving high integrity impact with no confidentiality or availability effect. User interaction is required, and Chromium's own internal severity rating is Low - notably lower than the NVD CVSS Medium score of 6.5 - consistent with EPSS of 0.22% (12th percentile) and SSVC's 'none' exploitation status. No public exploit exists and the vulnerability is not in CISA KEV at time of analysis.

The Passwords (built-in credential manager) component of Google Chrome on iOS prior to version 152.0.7977.65 leaks sensitive password data to a local attacker who can supply a crafted file, enabling unauthorized retrieval of stored credentials. Only the iOS platform is affected, and the Chromium security team rates this as Low severity internally. No public exploit code exists and EPSS stands at 0.11% (1st percentile), indicating very low near-term exploitation likelihood despite the high confidentiality impact of the exposed data.

Information leak in Google Chrome's XR (WebXR) subsystem allows unauthenticated remote attackers to obtain sensitive browser-context information when a victim visits a crafted HTML page. All Chrome desktop versions prior to 152.0.7977.65 are affected, with the vendor classifying severity as Low internally despite a CVSS 3.1 base score of 6.5 driven by high confidentiality impact. No public exploit has been identified and EPSS exploitation probability is very low at 0.17% (7th percentile), suggesting real-world risk remains limited; however, the zero-friction delivery vector - a single malicious page visit - warrants prompt patching given Chrome's ubiquitous deployment.

Information disclosure in Google Chrome's DevTools (versions prior to 152.0.7977.65) lets a remote attacker who convinces a user to install a crafted Chrome extension read adjacent memory inside the renderer sandbox via an off-by-one error. Chromium rates the security severity as Low, and there is no public exploit identified at time of analysis; SSVC lists exploitation status as none and EPSS is negligible (0.16%, 6th percentile).

Remote code execution within the Chrome sandbox is achievable in Google Chrome prior to 152.0.7977.65 through a use-after-free vulnerability in V8, Chrome's JavaScript engine, triggered by a crafted HTML page. Any unauthenticated remote attacker who can induce a user to visit a malicious URL can exploit this flaw; however, execution is confined to the Chrome sandbox, meaning a chained sandbox escape would be required for full host-system compromise. No public exploit code or confirmed active exploitation is documented at time of analysis, and SSVC assessment lists exploitation as none, tempering urgency despite the high CVSS base score.

Type confusion in Chrome's V8 JavaScript engine exposes memory contents within the browser sandbox to remote attackers who can socially engineer victims into visiting a crafted HTML page. All Chrome desktop releases prior to 152.0.7977.65 are affected, confirmed by the Chrome Stable Channel advisory linked in references. Despite the vendor-assigned CVSS 8.8, Chromium's own security team rated this 'Low' severity - reflecting the sandboxed scope of the memory disclosure and the required social engineering step - and EPSS probability stands at only 0.26% (18th percentile) with no CISA KEV listing, consistent with SSVC 'Exploitation: none'.

Integer overflow (CWE-190) in Chromium's file-processing code exposes all desktop Google Chrome versions prior to 152.0.7977.65 to in-sandbox memory disclosure when a user opens a specially crafted file, requiring no authentication (PR:N) but requiring user interaction (UI:R). A critical data conflict across sources warrants attention: the NVD CVSS score is 8.8 with C:H/I:H/A:H, yet Google's Chromium team rates this Low severity, and the EPSS is 0.16% (5th percentile) with SSVC Exploitation:none - collectively suggesting the attack impact is bounded to memory readable within the sandboxed renderer, without sandbox escape. No public exploit identified at time of analysis.

Information disclosure via Chrome's DataTransfer API in versions prior to 152.0.7977.65 allows remote attackers to obtain sensitive information when a victim visits and interacts with a crafted HTML page. Chromium's own Low severity classification creates a notable tension with the CVSS C:H rating, likely indicating that the scope of leaked data is constrained despite the high confidentiality label. No public exploit code or active exploitation has been confirmed; EPSS at 0.21% (11th percentile) places this firmly in the routine patching category.

Out-of-bounds read in Chrome's Skia graphics library exposes sandbox memory to attackers who have already compromised the renderer process. Exploitation requires a prior renderer compromise plus user interaction with a crafted HTML page, making this a chained second-stage information disclosure rather than a standalone critical flaw. Chromium's own severity rating is Low; no public exploit or CISA KEV listing exists, and EPSS sits at just 0.17%.

Use-after-free in the Animation component of Google Chrome prior to 152.0.7977.65 enables arbitrary code execution within the browser's renderer sandbox when a user visits a crafted HTML page. The flaw scores 8.8 CVSS HIGH, though Google's own internal Chromium severity rating is Low - a notable discrepancy that reflects the sandboxed containment of the impact. No public exploit code has been identified, SSVC indicates no active exploitation, and a vendor patch is confirmed available in Chrome 152.0.7977.65.

Web origin policy bypass in Google Chrome prior to 152.0.7977.65 allows a remote attacker to violate the browser's same-origin isolation guarantees through a crafted Chrome extension delivered via social engineering. The CWE-459 incomplete cleanup root cause means residual state is left after a browsing or extension context transition, enabling a malicious extension to interact with origins it should not have access to - resulting in a High integrity impact per the CVSS vector. No public exploit code and no CISA KEV listing are confirmed at time of analysis; the EPSS score of 0.24% (14th percentile) reflects low observed exploitation pressure, consistent with the social-engineering prerequisite and the Chromium team's own Low severity designation.

Web origin policy bypass in Google Chrome's ReaderMode feature prior to version 152.0.7977.65 allows a remote attacker to inject content into a privileged browser page context via a crafted HTML page, requiring social engineering to achieve user interaction. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) limits impact to integrity only, with no confidentiality or availability consequences. No public exploit code or CISA KEV listing exists; EPSS at 0.26% (17th percentile) confirms very low observed exploitation probability.

Cross-origin information leakage in the FoldableAPIs component of Google Chrome prior to 152.0.7977.65 enables a remote attacker to read sensitive device-geometry data from foldable-form-factor devices by luring a user to a crafted HTML page. The affected API fails to enforce origin isolation, exposing data that should be inaccessible to untrusted cross-origin scripts. No public exploit has been identified and SSVC rates exploitation status as none; Chromium's own internal severity classification of 'Low' contrasts with the NVD-assigned 6.5 Medium, reflecting the bounded real-world impact.

Remote code execution in Google Chrome desktop before 152.0.7977.65 arises from a use-after-free in the ServiceWorker subsystem that a crafted HTML page can trigger to run attacker code outside the renderer sandbox. Any user browsing to a malicious page with a vulnerable build is exposed, and successful exploitation yields full compromise of the host user context. No public exploit identified at time of analysis and the issue is not in CISA KEV; notably, Chromium's own severity rating is Low even though the NVD CVSS base score is 9.6, a discrepancy defenders should weigh.

UI misrepresentation in Google Chrome's Web Authentication (WebAuthn) subsystem - covering both Passkeys and hardware Security Keys - prior to version 152.0.7977.65 allows remote attackers to manipulate authentication dialog presentation via a crafted HTML page, enabling bypass of system access restrictions through social engineering. The CVSS vector rates Integrity impact as High (I:H) with no privileges required (PR:N), yet Chromium's own team assigned Low severity, and EPSS exploitation probability is just 0.22% (12th percentile), reflecting the social engineering dependency. No public exploit has been identified and no CISA KEV listing exists at time of analysis.

ServiceWorker improper input validation in Google Chrome prior to 152.0.7977.65 enables a remote attacker to bypass system access restrictions by directing a user to a crafted HTML page. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) confirms no authentication is required from the attacker but user interaction is necessary, limiting the scope of practical exploitation. No public exploit has been identified at time of analysis, and EPSS is low at 0.30% (23rd percentile), consistent with the internal Chromium severity rating of Low.

Out-of-bounds memory read in Chrome's Tint graphics library on Android exposes sandbox-contained memory to remote attackers. Google Chrome for Android prior to 152.0.7977.65 is affected; an attacker who lures a user to a crafted HTML page can trigger the flaw and read arbitrary memory within the Chrome sandbox. No active exploitation has been identified - Chromium's own security team rates this as Low severity, consistent with the 0.17% EPSS score and the absence of a CISA KEV listing.

Type confusion in Chrome's V8 JavaScript engine (versions prior to 152.0.7977.65) enables remote code execution within the browser sandbox when a victim is socially engineered into visiting a crafted HTML page. The vulnerability arises from a CWE-843 type confusion flaw in V8, allowing an attacker to manipulate object type assumptions at runtime to achieve arbitrary code execution. Importantly, execution is constrained to the Chrome sandbox, which Chromium's own severity rating of 'Low' reflects; no public exploit code or CISA KEV listing has been identified at time of analysis.

Incorrect authorization in Google Chrome's Media component on Windows enables a remote attacker who has already compromised the renderer process to bypass OS-level system access restrictions via a crafted HTML page. Affected are all Chrome versions prior to 152.0.7977.65 on Windows. No public exploit code has been identified and EPSS probability is very low at 0.21% (11th percentile), though the sandbox-escape nature of this flaw makes it a meaningful chaining risk in multi-stage attacks.

StorageAccessAPI incorrect authorization in Google Chrome prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to bypass web origin policy via a crafted HTML page, achieving high-integrity impact against cross-origin resources. The flaw (CWE-863) is a post-exploitation second-stage primitive: it cannot be leveraged without a preceding renderer compromise, substantially narrowing its realistic threat scope beyond what the CVSS 6.5 score implies. No public exploit code has been identified, EPSS stands at 0.19%, Chromium's own internal severity rating is Low, and there is no CISA KEV listing at time of analysis.

UI spoofing in Google Chrome prior to 152.0.7977.65 allows unauthenticated remote attackers to misrepresent browser interface elements through a crafted HTML page, requiring only that a user visit the malicious content. Classified as CWE-451 (UI Misrepresentation of Critical Information), the flaw breaks the trust contract between the browser and user by rendering deceptive interface states - a classic phishing-enabler primitive. No public exploit code has been identified and EPSS stands at 0.22% (12th percentile), consistent with Chromium's own Low severity rating; real-world exploitation impact is constrained by its dependence on social engineering and user interaction.

UI spoofing in Google Chrome's Passwords component (versions prior to 152.0.7977.65) lets a remote attacker who has already compromised the renderer process present forged interface elements via a crafted HTML page, enabling deception such as credential phishing. Chromium rated this severity Low, and no public exploit or active exploitation has been identified; EPSS is low at 0.23% (14th percentile). The headline NVD CVSS of 9.1 substantially overstates the practical impact given the required renderer compromise.

Cross-origin data exposure in Google Chrome's StorageAccessAPI implementation allows a remote attacker to read data across origin boundaries by directing a victim to a specially crafted HTML page. All Chrome desktop releases prior to 152.0.7977.65 are affected across all platforms. No public exploit code has been identified and CISA SSVC classifies current exploitation status as none, consistent with the Chromium team's own Low severity rating.

UI spoofing in Google Chrome on macOS prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to forge browser UI elements via a crafted HTML page, potentially deceiving users into believing they are interacting with a trusted interface. The vulnerability is macOS-specific and requires renderer process compromise as an explicit prerequisite, significantly limiting its standalone exploitability. No public exploit code or active exploitation (CISA KEV) has been identified; an EPSS score of 0.21% (11th percentile) reflects negligible likelihood of independent exploitation.

Missing authorization in Google Chrome's Browser component on macOS (versions prior to 152.0.7977.65) enables remote attackers to bypass the web origin policy and reach privileged browser pages via a crafted HTML page, contingent on social engineering the victim into visiting the page. Impact is limited to integrity (CVSS I:L) with no confidentiality or availability consequences; EPSS at 0.26% (18th percentile) signals negligible current exploitation probability. No public exploit identified at time of analysis, and the vendor-released patch is available as of version 152.0.7977.65.

Address bar spoofing in Google Chrome prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to deceive users about the current page origin via a crafted HTML page. The root cause is missing authorization (CWE-862) in Chrome Core, where the renderer can influence address bar state without proper permission checks. No public exploit code or CISA KEV listing exists at time of analysis; EPSS is very low at 0.28%, consistent with the chained exploitation requirement.

Web origin policy bypass in Google Chrome prior to 152.0.7977.65 allows a remote attacker to circumvent same-origin restrictions via a crafted HTML page, achieving limited integrity impact in the user's browsing context. The flaw is rooted in incorrect authorization logic (CWE-863) within Chrome's Select component, as confirmed by the vendor's stable channel advisory. No public exploit has been identified at time of analysis, and EPSS signals very low exploitation probability at 0.26% (18th percentile), consistent with Chromium's own Low severity rating.

Privilege-management weakness in Google Chrome's Actor component (versions prior to 152.0.7977.65) lets a remote attacker who successfully socially-engineers a user into loading a crafted HTML page bypass system access restrictions. Chromium rates the underlying severity as Low, and no public exploit or active exploitation has been identified; EPSS is 0.21% (11th percentile). Note a sharp signal conflict: the NVD-style CVSS base score is 9.8 (critical) while the vendor's own severity rating is Low and the description requires user interaction.

Incorrect authorization in Chrome's StorageAccessAPI (versions prior to 152.0.7977.65) enables a renderer-compromised attacker to bypass the web origin policy via a crafted HTML page. This is a chained vulnerability - exploitation is contingent on a prior renderer process compromise, making it a second-stage component in a multi-bug attack chain rather than a standalone threat. No public exploit identified at time of analysis; EPSS at 0.23% (14th percentile) confirms low independent exploitation probability, consistent with Chromium's own 'Low' internal severity rating despite the NVD-assigned 6.5 CVSS score.

Web origin policy bypass in Google Chrome on Windows (prior to 152.0.7977.65) via improper input validation in the New Tab Page (NTP) Footer component enables integrity compromise without confidentiality loss. Exploitation is contingent on the attacker having already achieved renderer process compromise, making this a chained, post-exploitation primitive rather than a standalone vector. No public exploit code exists and EPSS sits at the 8th percentile, consistent with Chromium's own Low severity rating - though the integrity impact is rated High under CVSS.

Web origin policy bypass in Google Chrome's ReadingList component on Windows enables a renderer-compromised attacker to cross origin boundaries via a crafted HTML page. Affected are all Chrome for Windows versions prior to 152.0.7977.65. No public exploit code or active exploitation has been identified; EPSS sits at 0.18% (8th percentile), and Chromium's own security team rates this as Low severity despite the NVD CVSS score of 6.5.

Incorrect reference resolution in the WebView component of Google Chrome on Android (versions prior to 152.0.7977.65) enables a remote attacker to potentially bypass the web origin policy by delivering a crafted HTML page. The flaw carries a Chromium-internal severity of Low, consistent with the limited confidentiality-only impact (C:L/I:N/A:N) reflected in the CVSS 4.3 score. No public exploit has been identified at time of analysis, and the EPSS score of 0.20% (10th percentile) confirms negligible current exploitation probability.

Memory disclosure via uninitialized GPU resource in Google Chrome on Android (prior to 152.0.7977.65) allows a remote attacker to read memory outside the browser sandbox by directing a user to a crafted HTML page. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) reflects a low-complexity network attack requiring no privileges but dependent on user interaction. No public exploit code has been identified at time of analysis, and the low EPSS score of 0.31% corroborates a currently low exploitation probability despite Chrome's enormous Android deployment footprint.

Memory disclosure in Google Chrome for Android (prior to 152.0.7977.65) exposes sandbox-contained memory via an uninitialized GPU resource, triggered when a victim loads a crafted HTML page. The flaw is platform-specific to Android and carries confidentiality-only impact bounded by Chrome's GPU sandbox isolation - no integrity or availability exposure. No public exploit code is identified at time of analysis, and EPSS at 0.31% (24th percentile) aligns with the vendor's own 'Low' Chromium severity rating, indicating low near-term exploitation probability.

Incorrect authorization in the Controls component of Google Chrome prior to version 152.0.7977.65 enables web origin policy bypass via a crafted HTML page, requiring only that a user visit the attacker-controlled page. The flaw (CWE-863) allows limited cross-origin integrity manipulation with no confidentiality or availability impact, as reflected in the CVSS integrity-only impact score. No public exploit has been identified at time of analysis, EPSS stands at 0.19% (8th percentile), and the Chromium team internally rated severity as Low - all signals consistent with a narrow-impact, user-interaction-dependent authorization gap.

Address bar spoofing in Google Chrome for Android's CustomTabs feature enables remote unauthenticated attackers to misrepresent the displayed URL to users through a crafted HTML page. All Chrome for Android versions prior to 152.0.7977.65 are affected on the Android platform only; desktop Chrome is not impacted. No public exploit identified at time of analysis, and the EPSS score of 0.17% (7th percentile) combined with Chromium's own 'Low' severity rating reflect limited real-world exploitation probability, though the phishing-enablement potential makes it worth patching promptly.

UI spoofing in Google Chrome's Transactions Platform prior to version 152.0.7977.65 enables remote attackers to misrepresent UI elements - such as payment confirmation dialogs or security indicators - through a crafted HTML page, relying on social engineering for delivery. Classified under CWE-451 (UI Misrepresentation of Critical Information), the flaw requires user interaction and carries no confidentiality or availability impact, confining harm to integrity via deception. No active exploitation is confirmed and EPSS probability is very low (0.29%), but the ubiquitous deployment footprint of Chrome means the absolute population of potential targets is large.

Chrome's PermissionElement component can be visually spoofed via a crafted HTML page, allowing a remote attacker to mislead users into granting browser permissions they did not intend to approve. All Chrome desktop versions prior to 152.0.7977.65 are affected, as confirmed by the vendor's Stable Channel advisory and EUVD-2026-66037. No public exploit code has been identified at time of analysis, and EPSS at 0.17% reflects negligible observed exploitation interest.

Skia, the 2D graphics library embedded in Google Chrome prior to 152.0.7977.65, leaks sensitive information when an attacker who has already compromised the renderer process delivers a crafted HTML page to a victim. This CWE-200 flaw functions as a chaining component in a multi-stage exploit rather than a standalone entry point - it amplifies the impact of a prior renderer compromise rather than providing initial access. No public exploit code exists, EPSS is 0.17% (7th percentile), and Chrome's own severity classification is Low, all consistent with the mandatory pre-condition of a pre-compromised renderer.

Race condition in Google Chrome's Transactions Platform on Android (prior to 152.0.7977.65) enables remote attackers to bypass system access restrictions with high integrity impact. Exploitation requires social engineering the victim into visiting a crafted HTML page, and the race window makes reliable triggering difficult (AC:H per CVSS). Chromium's own severity rating is Low; EPSS at 0.18% (7th percentile) confirms minimal real-world exploitation pressure, and no public exploit or KEV listing has been identified.

Use-after-free in Google Chrome's PDF rendering subsystem (all versions prior to 152.0.7977.65) allows a remote attacker to execute arbitrary code confined within the Chrome sandbox by delivering a crafted PDF file. The vulnerability is triggered through normal user interaction - opening a malicious PDF - requiring no privileges or authentication. While CVSS scores this 8.8 (High), Chrome's own severity rating is 'Low', reflecting the critical nuance that code execution is sandboxed and does not directly achieve host-level compromise. No public exploit exists and SSVC confirms no known exploitation at time of analysis.

Missing authorization in the BrowserTag component of Google Chrome prior to 152.0.7977.65 enables remote attackers to extract sensitive information by distributing a crafted Chrome extension via social engineering. The flaw bypasses authorization checks within BrowserTag, allowing the malicious extension to access data it should not be permitted to read. No active exploitation has been identified (CISA KEV absent), EPSS sits at 0.23% (13th percentile), and Chromium's own severity classification is 'Low' - all consistent with the UI:R prerequisite of tricking a user into installing a hostile extension.

Out-of-bounds memory read in Google Chrome's FileSystem component (versions prior to 152.0.7977.65) allows a remote unauthenticated attacker to leak memory contents from outside the browser's renderer sandbox by directing a victim to a specially crafted HTML page via social engineering. Exploitation is contingent on user interaction, limiting opportunistic or automated mass exploitation. No public exploit code exists and EPSS sits at 0.17% (7th percentile), though the Confidentiality impact is rated High, meaning successful exploitation could expose sensitive data from browser memory. Vendor-released patch is available in Chrome 152.0.7977.65.

Web origin policy bypass in Google Chrome Extensions affects all desktop versions prior to 152.0.7977.65, exploitable only by an attacker who has already compromised the renderer process. The incorrect authorization flaw (CWE-863) in the Extensions subsystem allows the renderer-level attacker to cross Same-Origin Policy boundaries via a specially crafted HTML page, potentially reading data from origins the renderer should not access. No public exploit code and no CISA KEV listing exist; EPSS is 0.19% (8th percentile), consistent with Chromium's own 'Low' severity rating for this issue.

Observable discrepancy in Chrome's Glic component allows remote information disclosure against users running versions prior to 152.0.7977.65. An attacker who persuades a victim to visit a crafted HTML page can exploit a behavioral or timing side-channel in the Glic AI-integration subsystem to extract sensitive information with high confidentiality impact, despite the medium overall CVSS score. No public exploit identified at time of analysis, and EPSS at 0.17% (7th percentile) indicates very low current exploitation probability.

Race condition in Google Chrome's Core component on Windows (all versions prior to 152.0.7977.65) enables a remote attacker to bypass the browser's web origin policy via a crafted HTML page, requiring social engineering to induce user interaction. Exploitation allows partial cross-origin data disclosure (C:L), with no integrity or availability impact. No public exploit code has been identified and no active exploitation is confirmed; EPSS sits at 0.24% (15th percentile), consistent with Chromium's own 'Low' severity rating for this issue.

Improper input validation in Chrome's DeviceBoundSessionCredentials (DBSC) component allows remote attackers to bypass the web origin policy by delivering crafted network traffic, contingent on social engineering the user into triggering the request. All Chrome versions prior to 152.0.7977.65 are affected across desktop platforms. No public exploit code has been identified and EPSS sits at 0.28% (20th percentile), consistent with the low-to-medium CVSS 4.3 rating and the user-interaction prerequisite.

Race condition in Google Chrome's Editing component prior to version 152.0.7977.65 enables remote attackers who successfully socially engineer a victim to visit a crafted HTML page to extract sensitive information from the browser. The CVSS vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N) shows the attack is network-delivered but requires high complexity timing and explicit user interaction, limiting real-world exploitability. No public exploit identified at time of analysis, and the extremely low EPSS score of 0.14% (4th percentile) corroborates the vendor's own Low Chromium severity designation.

Integer overflow in the WebRTC component of Google Chrome prior to 152.0.7977.65 enables remote code execution confined to the browser's sandbox via a crafted HTML page. The flaw requires no authentication (PR:N) and no special browser configuration, as WebRTC is enabled by default, but it does require the victim to visit an attacker-controlled page (UI:R). No public exploit code has been identified and EPSS places exploitation probability at 0.35%, consistent with SSVC's assessment of no current exploitation; notably, Google's own internal Chromium severity rating for this issue is 'Low,' suggesting the sandbox boundary and exploit reliability considerations factor into their triage.

Incorrect authorization in Chrome's WebProtect component (CWE-863) allows a remote attacker to bypass system access restrictions via a crafted HTML page, affecting all Chrome versions prior to 152.0.7977.65. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) confirms impact is limited to partial integrity loss with no confidentiality or availability consequence, and exploitation is gated on the victim actively navigating to attacker-controlled content. No active exploitation is confirmed - CISA KEV status is absent and EPSS stands at 0.19% (8th percentile), consistent with the Low severity rating assigned by the Chromium security team.

Bluetooth information disclosure in Google Chrome on macOS (versions prior to 152.0.7977.65) enables a remote attacker - who has already compromised the renderer process - to extract sensitive Bluetooth-related information by combining a crafted HTML page with social engineering. This is a chained, multi-prerequisite vulnerability: successful exploitation requires a prior renderer compromise and active victim interaction, which the CVSS AC:H rating reflects. No public exploit code exists and no active exploitation has been observed (SSVC: Exploitation none; EPSS 0.29%), placing real-world risk substantially below what the C:H confidentiality impact alone might suggest. A vendor patch is available in Chrome 152.0.7977.65.