Monthly
Local privilege escalation in Android 16 and 17 exploits a confused deputy (CWE-441) vulnerability present across multiple system locations, allowing a low-privileged local process to read and write files it is not authorized to access. An attacker with basic application execution on the device can trigger a privileged system intermediary to operate on restricted files using its own elevated credentials, achieving full local privilege escalation without any user interaction. No public exploit exists at time of analysis, and CISA SSVC assessment confirms no observed active exploitation.
Local privilege escalation in Android 16 through 17 exploits incorrect authorization (CWE-863) across multiple URI access control locations, allowing a low-privileged process to bypass permissions checks and achieve full read/write/execute access on the device without requiring user interaction. Reported by security@android.com and addressed in the September 2026 Android Security Bulletin, the flaw affects Android 16, Android 16-QPR2, and Android 17. No public exploit has been identified and EPSS sits at the 2nd percentile, though SSVC rates the technical impact as total.
Heap buffer overflow in Android's OAPV video codec decoder (oapv.c) enables remote code execution on Android 16 and 17 without requiring user interaction. The flaw resides in dec_frm_prepare(), where insufficient bounds checking during frame decoding preparation allows an attacker to overwrite heap memory via crafted video content. EPSS sits at 0.18% (8th percentile) with SSVC exploitation status rated 'none', but technical impact is classified as 'total' and no public exploit has been identified at time of analysis.
Local privilege escalation in Android's Setup Wizard allows a low-privileged attacker to force the device to connect to a malicious network by exploiting a confused deputy relationship (CWE-441), achieving full C:H/I:H/A:H compromise without any user interaction. The flaw is addressed in the September 2026 Android Security Bulletin (patch level 2026-09-01) and requires only an existing low-privilege foothold on the device. No public exploit code has been identified, and EPSS sits at 0.11% (2nd percentile), indicating negligible observed exploitation probability at time of analysis.
Local privilege escalation in Android's Slice permission subsystem allows a low-privileged installed application to bypass permission checks via a confused deputy flaw in SlicePermissionActivity.java's onCreate method. Affecting Android 14 through 17 (including the 16-QPR2 branch), the vulnerability requires no user interaction and grants full C:H/I:H/A:H impact on a successful device. No public exploit has been identified at time of analysis, and EPSS scoring (0.12%, 2nd percentile) reflects low current exploitation activity.
Local privilege escalation in Android's ChannelImpl.java allows a low-privileged installed application to launch arbitrary intents by exploiting improper input validation in the initAppLinkTypeAndIntent method. Affected versions span Android 14 through 17, including 16-QPR2. Exploitation requires user interaction, limiting automated attack at scale - SSVC confirms no observed exploitation and EPSS sits at 0.11% (2nd percentile), consistent with the local-access, user-interaction gating.
Local privilege escalation in Android 16, 16-QPR2, and 17 is possible via Intent Redirection by exploiting a logic error in ActivityStarter.java's resolveActivity method. A locally-installed malicious application with basic user privileges can craft or intercept Intents to gain unauthorized access to protected system components, achieving full confidentiality, integrity, and availability compromise of the device without requiring any user interaction after installation. EPSS is 0.12% (2nd percentile) and no active exploitation or public POC has been identified at time of analysis.
Silent NFC payment session hijacking in Android 15 and 16 allows a locally-installed low-privilege application to exploit missing permission checks in NfcService.java, enabling unauthorized manipulation of NFC payment sessions without any user interaction. The flaw is a missing authorization gate (CWE-862) across multiple functions in the NFC service, permitting a malicious app to hijack, enable, or redirect contactless payment flows targeting the device. No public exploit has been identified and CISA SSVC rates exploitation as none, though the financial-fraud potential elevates practical risk beyond what the EPSS score of 0.11% suggests.
Remote code execution in Android's MatroskaExtractor component (MatroskaExtractor.cpp) affects Android 14, 15, 16, and 16-qpr2 via an improper type cast during Matroska/MKV media container parsing. A low-privileged remote attacker can exploit this flaw without user interaction to achieve full confidentiality, integrity, and availability compromise on the target device. No public exploit has been identified at time of analysis, and EPSS stands at 0.15%, though the zero-interaction requirement and full-impact CVSS 8.8 rating warrant prompt patching.
Background activity launch (BAL) restrictions in Android 15, 16, 16-qpr2, and 17 can be bypassed by a locally installed application exploiting a confused deputy pattern spanning multiple framework functions. A low-privileged app manipulates one or more privileged Android system components into launching background activities on its behalf, circumventing protections designed to block unauthorized UI intrusion and enabling local privilege escalation with full confidentiality, integrity, and availability impact. No public exploit has been identified at time of analysis; EPSS at 0.12% (2nd percentile) reflects low observed exploitation activity despite the 7.8 CVSS score.
Remote privilege escalation in the Android Bluetooth stack (AdapterService.java) allows an attacker to bypass device pairing entirely. A logic error in handleBondStateChanged lets a bond be treated as established without the normal pairing/consent flow, granting the attacker elevated privileges on Android 15, 16, 16-qpr2, and 17 with no user interaction. Google rates it CVSS 9.8; no public exploit is identified and CISA's SSVC framework records exploitation status as none, and EPSS is very low (0.16%).
Remote code execution across Android versions 14 through 17 is possible via a use-after-free condition triggered by a race condition in multiple OS locations. The CVSS vector (AV:N/AC:H/PR:L/UI:N) places this as a network-reachable, low-privilege attack requiring no user interaction but demanding precise timing due to the race condition mechanics, with full confidentiality, integrity, and availability impact on successful exploitation. No public exploit code has been identified at time of analysis, and the EPSS score of 0.16% (6th percentile) reflects low current observed exploitation pressure despite the broad attack surface spanning essentially all actively supported Android versions.
Local privilege escalation in Android's AppRestrictionsFragment allows a low-privileged app to gain unauthorized read/write access to private files via a confused deputy in the assertSafeToStartCustomActivity method. Affected versions span Android 14, 15, 16, 16-QPR2, and 17, making this a broad-surface vulnerability across the current Android ecosystem. With PR:L/UI:N, a malicious installed app can silently exploit this without user interaction to achieve full local C:H/I:H/A:H impact. No public exploit identified at time of analysis; EPSS is 0.11% (2nd percentile).
Multi-user isolation breaks in Android's ClipboardService framework layer (CWE-284 Improper Access Control) across Android 14 through 17, enabling a locally-executed low-privileged process to cross user-profile boundaries and escalate privileges with full confidentiality, integrity, and availability impact. The logic error in setClipboardAccessNotificationsEnabledForUser fails to correctly enforce per-user access checks, allowing one user context to manipulate clipboard access notification state for other user profiles on the same device. No public exploit has been identified at time of analysis, and EPSS of 0.12% places this at the 2nd percentile for near-term exploitation probability.
Local privilege escalation in Android's PaymentDefaultDialog allows an attacker with standard app-level execution to silently replace the device's default NFC payment application via a confused deputy in the component's onCreate method. Affecting Android 15, 16, 16-qpr2, and 17, the flaw is patched in the September 2026 Android Security Bulletin. No public exploit has been identified at time of analysis, and EPSS sits at 0.11%, consistent with SSVC's 'Exploitation: none' designation despite the high technical impact potential.
Intent redirection bypass in Android's ActivityManagerService enables a low-privileged local app to escalate privileges and gain full device access without any user interaction. The logic error in addCreatorToken of ActivityManagerService.java corrupts the creator-token mechanism that governs Intent origin and authority, allowing a malicious app to redirect Intents to system-protected components that should be inaccessible to it. EPSS at 0.13% (3rd percentile) and no CISA KEV listing indicate limited observed exploitation; no public exploit has been identified at time of analysis.
Local privilege escalation via use-after-free in Android 16-QPR2 and Android 17 allows a low-privileged local attacker to gain full system access with no user interaction required. The vulnerability arises from a logic error present at multiple code locations within the Android codebase, triggering a use-after-free condition that corrupts memory and enables privilege elevation to system or root level. No public exploit has been identified at the time of analysis, and EPSS sits at 0.12% (2nd percentile), consistent with no observed active exploitation.
Local privilege escalation in Android's Settings app (SettingsFragment.java) affects Android 14 through 17, including 16-qpr2, allowing a low-privileged local attacker to gain full device control via misleading or insufficient UI in the getItemList method. No victim interaction is required - the attacker's own low-privileged app or session is sufficient to trigger the UI bypass. EPSS is 0.12% (2nd percentile) and SSVC records no active exploitation, but SSVC simultaneously rates technical impact as total, reflecting the severity of a successful attack despite limited observed real-world activity.
Local privilege escalation in Android 14, 15, and 16 stems from improper encryption key validation caused by a logic error (CWE-347) present across multiple code locations. A low-privileged local attacker can exploit the flawed key verification path to gain full confidentiality, integrity, and availability impact over the device without requiring user interaction or elevated starting privileges. No public exploit has been identified at time of analysis, and EPSS probability sits at 0.11% (2nd percentile), but the vulnerability spans multiple Android versions in active deployment.
Out-of-bounds write in Android's camera metadata validation logic (validate_camera_metadata_structure in camera_metadata.c) allows a local low-privileged attacker to escalate privileges to a higher-privileged context with full confidentiality, integrity, and availability impact. Affects Android 14 through 16-qpr2, patched in the September 2026 Android Security Bulletin. No public exploit code or active exploitation has been identified; EPSS sits at the 2nd percentile and SSVC rates exploitation as none.
Tapjacking and UI overlay exploitation in Android 16-QPR2's `InstallLaunch.kt` `onCreate` method allows a locally-installed malicious application to present a deceptive interface over the package installation workflow, leading to local privilege escalation with full confidentiality, integrity, and availability impact. Fixed in Google's September 2026 Android Security Bulletin, the flaw requires no additional execution privileges and - per the CVSS vector - no user interaction beyond what occurs during the overlay setup phase. No public exploit code and no active exploitation have been identified at time of analysis; EPSS sits at 0.11% (2nd percentile).
Local privilege escalation in Android 16 and 16-QPR2 allows a low-privileged app to escalate to full device control by exploiting a logic error in HostEmulationManager.java that permits unauthorized background activity launches. The flaw stems from CWE-693 (Protection Mechanism Failure) in the activity-launch gating logic, enabling an installed malicious app to bypass Android's background activity restrictions without requiring additional permissions or user interaction. No public exploit has been identified and CISA has not added this to KEV, but SSVC rates the technical impact as total given that successful exploitation yields C:H/I:H/A:H on the device.
Local privilege escalation in Android's BackgroundLaunchProcessController allows a low-privileged app or user process to launch background activities beyond its permitted scope due to a logic error in the areBackgroundActivityStartsAllowed gating function. Affected versions span Android 14 through Android 16-QPR2, covering the vast majority of modern Android devices in active use. With PR:L and UI:N, exploitation requires only a foothold as a regular user-space app - no user interaction or elevated permissions - making it a reliable post-installation escalation primitive. No public exploit exists and CISA SSVC rates exploitation as none at time of analysis.
Privilege escalation in Google Cloud Integration Connectors (HTTP Connector component) allows an authenticated low-privilege user to attach an unauthorized service account to a connector, effectively taking over the associated Google Cloud Project. Affected versions are those deployed prior to the 2025-12-11 server-side patch, which Google applied automatically with no customer action required. No public exploit has been identified at time of analysis, but the CVSS 4.0 vector reflects high subsequent-system impact across confidentiality, integrity, and availability - matching a full project compromise scenario.
Path traversal in Google Cloud Agent Development Kit (ADK) Python versions 1.9.0 through 1.21.0 exposes arbitrary server files to unauthenticated remote attackers via a crafted `file_path` query parameter on the builder endpoint. The root cause, confirmed by the upstream commit diff, is that `fast_api.py` passed the user-supplied path directly into filesystem operations without sanitization or boundary enforcement, allowing `../` sequences to escape the agents directory. No public exploit code or active exploitation has been identified; vendor-released fix is available in v1.22.0.
Analysis complete. The JSON synthesis is above. Key findings for **CVE-2026-78745** (Weyon/HiDPT HiDPTAndroid on Hi3751V350): - **Vulnerability**: Unauthenticated RCE via a network-reachable ADB daemon (adbd) with authorization bypassed/disabled — CWE-284, an exposed privileged debug interface, not a memory bug. - **Signals cross-referenced**: CVSS 9.8 is technically defensible on affected devices, but EPSS is low (0.42%, 35th pct), it's not in KEV, and a public PoC exists (`n0c71v3x/CVE-2026-78745`). Real-world exposure is bounded by whether adbd is reachable beyond the LAN — consumer TVs typically sit behind NAT. - **Metadata problems flagged**: wrong "Google" vendor tag (Android-based ≠ Google product), "N A" placeholder tag, and an `n/a:n/a` CPE. No prompt-injection note was present in this input (it was clean). Saved to memory as `cve-2026-78745.md` with an index entry.
Sandbox-escape remote code execution affects Google Chrome on iOS prior to 152.0.7977.82, where improper input validation (CWE-20) in the browser's Transactions Platform component lets a remote attacker potentially run arbitrary code outside the renderer sandbox when a victim loads a crafted HTML page. Google shipped a fix in the stable channel and Chromium rated the underlying issue Medium severity, though the supplied CVSS vector scores it 9.6. There is no public exploit identified and CISA's SSVC framework records exploitation status as none.
Type confusion (CWE-843) in the Compositing subsystem of Google Chrome prior to 152.0.7977.82 enables unauthenticated remote attackers to execute arbitrary code within the renderer sandbox by delivering a crafted HTML page to a victim. Execution is confined to Chrome's renderer process rather than the underlying OS - a full host compromise would require chaining with a separate sandbox escape primitive. No public exploit or active exploitation (KEV) has been identified at time of analysis; SSVC rates Exploitation: none and Automatable: no.
Use-after-free in Skia, Chrome's 2D graphics rendering engine, allows remote attackers to execute arbitrary code within the Chrome renderer sandbox by luring a user to a crafted HTML page. Affected versions are all Chrome releases prior to 152.0.7977.82 across desktop platforms. The sandbox confinement means this vulnerability alone does not yield full system compromise - a chained sandbox escape would be required for that - but the renderer-process code execution is rated high impact by Chromium's internal severity team. No public exploit or CISA KEV listing is present at time of analysis; SSVC labels exploitation as none and the attack as non-automatable due to the required user interaction.
Remote code execution in Google Chrome's DevTools component before 152.0.7977.82 lets a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and carries a CVSS 9.6 with scope change, reflecting sandbox escape. Google has shipped a fix; per CISA's SSVC assessment there is no evidence of active exploitation and no public exploit identified at time of analysis.
Sandboxed remote code execution in Google Chrome's CacheStorage API (prior to 152.0.7977.82) allows a remote attacker to execute arbitrary code inside the Chrome renderer sandbox by luring a user to visit a specially crafted HTML page. The root cause is CWE-668 (Exposure of Resource to Wrong Sphere), where CacheStorage improperly exposes resources to an unintended security context. No public exploit code has been identified and SSVC reports exploitation status as none, though the patch is available and update is strongly recommended.
Remote code execution in Google Chrome for Android before 152.0.7977.82 stems from an out-of-bounds write in the WebGL implementation, letting a remote attacker escape the browser sandbox and run arbitrary code simply by luring a victim to a crafted HTML page. Rated Chromium severity High and CVSS 9.6, the flaw is notable because exploitation breaks out of the renderer sandbox rather than being contained by it. There is no public exploit identified at time of analysis, and CISA SSVC lists exploitation status as none.
In-sandbox arbitrary code execution in Google Chrome's V8 JavaScript engine (all versions prior to 152.0.7977.82) is achievable by a remote unauthenticated attacker who tricks a user into visiting a specially crafted HTML page. The underlying flaw is a CWE-367 Time-of-Check Time-of-Use (TOCTOU) race condition within V8, allowing the attacker to win a memory-access race and redirect execution flow inside the Chrome renderer sandbox. No public exploit code has been identified and CISA SSVC rates exploitation as 'none' at time of analysis, though the technical impact is rated 'total' within the sandbox boundary.
Use-after-free in Chrome's Compositing component (versions prior to 152.0.7977.82) enables a sandbox escape when chained with a renderer-process compromise - an attacker who has already gained control of the renderer can corrupt memory in the Compositing layer and execute arbitrary code outside Chrome's sandbox boundary on the host operating system. The CVSS S:C (scope changed) metric confirms this is a privilege-escalation-across-boundary primitive, delivering full C:H/I:H/A:H impact against the underlying OS. A vendor patch is available in Chrome 152.0.7977.82, and no public exploit has been identified at time of analysis.
System access-restriction bypass in Google Chrome's Network component (versions prior to 152.0.7977.82) lets a remote attacker use crafted network traffic to circumvent enforced access controls, stemming from incomplete resource cleanup (CWE-459). The flaw carries a Chromium-rated High severity and a CVSS of 9.1 reflecting high confidentiality and availability impact; no public exploit is identified at time of analysis and EPSS is low (0.22%). Google fixed it in the 2026-09 stable desktop channel update.
Type confusion in V8 (Chrome's JavaScript engine) in versions prior to 152.0.7977.82 enables unauthenticated remote attackers to execute arbitrary code within Chrome's renderer sandbox by enticing a user to visit a specially crafted HTML page. The flaw exploits V8's type system, allowing an attacker to manipulate object type metadata in the JavaScript heap to gain controlled memory access and code execution inside the renderer process. No public exploit or CISA KEV listing has been identified at time of analysis, though V8 type confusion vulnerabilities in Chrome have historically attracted rapid weaponization given the browser's enormous attack surface and attacker interest.
Sandbox escape and out-of-sandbox arbitrary code execution in Google Chrome (desktop) before 152.0.7977.75, rooted in an incorrect authorization flaw in the FileSystem component. A remote attacker who lures a victim into opening a crafted HTML page can break out of the renderer sandbox and run code with the privileges of the browser process. Rated High by Chromium and CVSS 9.6; the vendor has shipped a stable-channel patch, though no public exploit code or active exploitation has been identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in the Shared Tab Groups feature (CWE-416). A remote attacker who lures a victim into visiting a crafted HTML page can corrupt freed memory to execute arbitrary code outside the renderer sandbox. Chromium rates the severity Critical (CVSS 9.6); the vendor has shipped a fix, but no public exploit has been identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in the WebGL implementation, letting a remote attacker who lures a victim to a crafted HTML page execute arbitrary code OUTSIDE the renderer sandbox. Rated Critical by Chromium with a CVSS 9.6 (scope-changed) vector; a vendor patch shipped in the September 2026 Stable channel update. No public exploit identified at time of analysis, though the tracker bug (issues.chromium.org/546260492) and Google's own reporting indicate the flaw is well characterized.
Stack-based buffer overflow in the GPU component of Google Chrome on Windows (prior to 152.0.7977.75) enables full sandbox escape and arbitrary code execution on the host operating system. Exploitation is a two-stage chained attack: an attacker must first compromise the renderer process (via a separate vulnerability or exploit), then leverage this GPU flaw to break out of Chrome's sandbox and execute code with elevated host privileges. Google has released a patch in the stable channel update for desktop; no public exploit code or CISA KEV listing has been identified at time of analysis.
Use-after-free in Chrome's TabStrip component enables remote code execution outside the renderer sandbox in Google Chrome versions prior to 152.0.7977.75. An attacker must social-engineer a user into a specific UI interaction to trigger the memory-corruption primitive, after which arbitrary code executes at browser-process privilege - a full sandbox escape. Google has issued a stable channel patch; no public exploit or CISA KEV listing has been identified at time of analysis.
Use-after-free in Google Chrome's Browser process prior to version 152.0.7977.75 enables sandbox escape, allowing an attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The CVSS vector (AV:N/AC:H/S:C/C:H/I:H/A:H) reflects both the network-reachable delivery and the scope change from renderer to host-level execution. No public exploit or CISA KEV listing has been identified at time of analysis, but sandbox-escape primitives of this class are highly valued in exploit chains.
Remote code execution inside Chrome's sandbox is achievable via a use-after-free in WebRTC, triggered when a victim visits a specially crafted HTML page. Affected versions are all Chrome releases prior to 152.0.7977.75 across desktop platforms. No public exploit code or CISA KEV listing has been identified at time of analysis, though the sandboxed execution boundary limits the practical impact compared to the raw CVSS 8.8 score - Google's own Chromium severity rating of 'Medium' reflects this containment.
Sandbox escape in Google Chrome's TabStrip component (versions prior to 152.0.7977.75) allows a remote attacker who has already achieved renderer process compromise to execute arbitrary code outside the Chrome sandbox via incorrect authorization in tab management IPC. The attack chain requires two conditions to be met simultaneously: a prior renderer exploit and social engineering to deliver a crafted HTML page - placing this firmly in the chained-exploit category despite the high CVSS base score. A vendor-released patch is available in Chrome 152.0.7977.75; no public exploit code or active exploitation has been identified at time of analysis.
Sandbox escape in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows allows a local attacker to execute arbitrary code outside the Chrome sandbox via a crafted local program, affecting all Chrome for Windows versions prior to 152.0.7977.75. The root cause is incorrect authorization (CWE-863) within the Chromoting subsystem, where flawed authorization logic fails to restrict a local program from interacting with Chromoting in a way that crosses the sandbox boundary. Google has released a patched version (152.0.7977.75), and no public exploit has been identified at time of analysis, though the full post-sandbox C:H/I:H/A:H impact warrants prompt remediation.
Remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in Dawn, Chrome's WebGPU/GPU graphics abstraction layer, and - per Google's advisory - allows a crafted HTML page to execute arbitrary code outside the renderer sandbox. Exploitation only requires an unauthenticated victim to visit a malicious page, giving the attacker high-impact code execution on the device. No public exploit has been identified at time of analysis and the issue is not in CISA KEV, though the sandbox-escape framing makes it a high-priority browser patch.
Remote code execution within the browser sandbox is possible in Google Chrome versions prior to 152.0.7977.75 due to a use-of-uninitialized-resource flaw (CWE-908) in the V8 JavaScript engine. An attacker can trigger the vulnerability by luring a user to a crafted HTML page, with no authentication or special privileges required beyond normal web browsing. Google has released the patched build 152.0.7977.75; SSVC rates exploitation status as none and no CISA KEV listing has been identified at time of analysis.
Access-restriction bypass in Google Chrome desktop prior to 152.0.7977.75 lets a remote attacker who first tricks a user via social engineering leverage a co-installed application to escape Chrome's system access boundaries. The flaw is an improper input validation (CWE-20) issue in the browser's DataTransfer component, rated High by Chromium and fixed in the September 2026 Stable channel. EPSS is low (0.16%, 5th percentile), no public exploit or CISA KEV listing exists, so realistic risk is bounded by the required user interaction and the presence of a malicious co-installed app.
Remote code execution in Google Chrome desktop before 152.0.7977.75 stems from a use-after-free in the Proxy component that a remote attacker can trigger with crafted network traffic to run arbitrary code OUTSIDE the browser sandbox. Google rates the Chromium severity High and a patched Stable channel build is available; no public exploit code has been identified at time of analysis. Because the flaw yields a sandbox escape rather than a contained renderer bug, successful exploitation gives attacker-controlled code on the host at browser-process privilege.
Unauthenticated arbitrary file upload in the WPLP Cookie Consent (GDPR/CCPA cookie banner) plugin for WordPress, versions up to and including 4.4.1, allows remote attackers to plant executable files on the server and potentially achieve remote code execution. The flaw stems from missing file-type validation in the saas_upload_logo() function combined with an authorization bypass on the WPLP connector REST endpoints, so no login is required. Reported by Wordfence and carrying a CVSS of 9.8; no public exploit identified at time of analysis.
Unreviewed code execution in Google Cloud Build (GitHub-triggered builds prior to the 2026-06-24 fix) allowed a remote attacker to bypass the GitHub Trigger Comment Control approval gate via webhook suppression and run attacker-supplied code inside the build environment. The Comment Control feature is meant to require a maintainer's approval comment before a pull request from an outside contributor triggers a build; the flaw let that check be evaded so unapproved code executed. No public exploit identified at time of analysis, and Google states the issue was patched server-side with no customer action required.
Server-side request forgery in jina-ai reader allows unauthenticated remote attackers to reach cloud metadata services and internal HTTP endpoints by supplying publicly resolvable hostnames that map to private IP addresses. The private-address guard - intended to block RFC 1918 and metadata service IPs - is only enforced when the service runs inside Google Cloud, leaving all other deployment environments (AWS, Azure, on-premises) completely unprotected by this control. Successful exploitation in cloud-hosted deployments can yield instance metadata including IAM credentials and access tokens. No public exploit code has been identified at time of analysis, and this CVE is not currently listed in CISA KEV.
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.
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).
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.
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.
Server-side request forgery in the GitLab AI Gateway (Duo Agent Platform) lets an authenticated user redirect outbound model requests to an attacker-controlled endpoint by supplying a crafted inline flow configuration that overrides the HTTP Host header, exfiltrating Google Cloud Vertex service credentials and private signing keys. It affects AI Gateway 18.10 through 19.0.11, 19.1 through 19.1.6, and 19.2 through 19.2.1. Publicly available exploit code exists (HackerOne #3945100); EPSS is low at 0.19% and it is not in CISA KEV.
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.
Remote code execution in Time4Popcorn - a Popcorn Time media-streaming fork - affects the Windows client (<= 6.2.1.18), macOS client (<= 6.2.1.17), and Android client (<= 3.5.0.173) through the application's auto-update mechanism (updater.exe on Windows, the PT.updd component on macOS). Because the updater fetches and executes update payloads without verifying their integrity (CWE-494), an attacker able to influence the update channel can deliver and run arbitrary code on the victim host. No CISA KEV listing, no public exploit is identified at time of analysis, and EPSS is low at 0.26% (18th percentile).
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.
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.
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.
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%).
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.
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.
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.
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.
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.
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.
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.
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.
Remote code execution inside the Chrome sandbox is possible through a race condition in the Extensions component, exploitable via crafted network traffic against Google Chrome versions prior to 152.0.7977.65. Despite a CVSS score of 8.1, Chrome's own team rates this vulnerability Low severity - a notable divergence explained by the sandbox constraint: successful exploitation yields in-sandbox code execution rather than full OS-level compromise. No public exploit identified at time of analysis, and SSVC confirms no known active exploitation and that the attack cannot be automated reliably.
Use-after-free in Google Chrome's DevTools component (all versions prior to 152.0.7977.65) enables remote attackers to execute arbitrary code inside the Chrome sandbox by distributing a crafted extension through social engineering. The CVSS 8.8 score reflects high confidentiality, integrity, and availability impact within the process scope, though exploitation is constrained by the mandatory user interaction required to install the malicious extension. No public exploit code exists and SSVC rates active exploitation as none at time of analysis, placing real-world urgency below what the raw score implies.
Improper state validation in Google Chrome's HTML parser (all versions prior to 152.0.7977.65) enables remote code execution within the browser's renderer sandbox when a user visits a crafted HTML page. The flaw (CWE-754) requires no authentication and minimal user interaction - simply loading malicious HTML is sufficient - but execution is constrained to the renderer sandbox (scope unchanged, S:U). Despite an 8.8 CVSS score, EPSS sits at 0.21% (12th percentile) and CISA SSVC confirms no current exploitation, with no public exploit or KEV listing identified at time of analysis.
Remote code execution in Google Chrome prior to 152.0.7977.65 stems from improper input validation in the browser's Media component, enabling a remote attacker to potentially execute arbitrary code outside the sandbox when a user visits a crafted HTML page. The vulnerability carries a CVSS base score of 8.8, affects all desktop Chrome builds below 152.0.7977.65 across Windows, macOS, and Linux, and is classified under CWE-20. No public exploit has been identified at time of analysis, and CISA SSVC rates current exploitation as none despite a total technical impact rating.
Remote code execution outside the browser sandbox is achievable in Google Chrome prior to 152.0.7977.65 via improper input validation in the Media component, triggered by visiting a crafted HTML page. The sandbox escape aspect is the critical differentiator here - Chrome's multi-process sandbox is its primary defense-in-depth layer, so bypassing it yields native OS-level code execution under the victim's account. No public exploit identified at time of analysis, and SSVC classifies exploitation as none with the attack non-automatable due to required user interaction.
Sandbox escape in Google Chrome's Media component on Windows allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox via a crafted HTML page. Affected versions are all Chrome releases on Windows prior to 152.0.7977.65. No public exploit code or active exploitation has been identified at time of analysis; SSVC assessment confirms exploitation status as none, and EPSS probability is low at 0.26% (17th percentile), though SSVC technical impact is rated total given full sandbox bypass capability.
Insufficient control flow management in Google Chrome's DevTools component (versions prior to 152.0.7977.65) enables remote attackers to execute arbitrary code inside the browser sandbox by tricking a user into loading a crafted HTML page via social engineering. The flaw is rooted in CWE-691 and permits attacker-controlled code paths within the DevTools subsystem, with execution constrained to within the Chrome sandbox (S:U). No public exploit code has been identified at time of analysis, and both EPSS (0.21%, 12th percentile) and SSVC (exploitation: none, automatable: no) indicate low current exploitation probability despite the high CVSS 8.8 base score.
Type confusion in Google Chrome's DevTools component prior to version 152.0.7977.65 enables remote code execution within the browser sandbox when a victim is social-engineered into visiting a crafted HTML page. The flaw affects all Chrome platforms where DevTools is accessible and results in high confidentiality, integrity, and availability impact to the sandboxed process. No public exploit code has been identified at time of analysis, and SSVC assessment confirms no observed active exploitation, though the technical impact rating is classified as total.
Use-after-free in V8, Google Chrome's JavaScript engine, prior to version 152.0.7977.65 enables remote attackers to execute arbitrary code within the Chrome sandbox by luring a user to a crafted HTML page. The CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R) confirms low-complexity, unauthenticated network delivery requiring only a single user visit, with high confidentiality, integrity, and availability impact scoped to the renderer process. No public exploit code has been identified at time of analysis, and SSVC rates exploitation as none with a non-automatable attack path, though technical impact is assessed as total within the sandbox.
Remote code execution within the Chrome sandbox is achievable via a race condition in the V8 JavaScript engine, affecting all Google Chrome versions prior to 152.0.7977.65. An unauthenticated remote attacker (per CVSS PR:N) can trigger the vulnerability by luring a user to a crafted HTML page, exploiting a timing window in V8's memory management to execute arbitrary code. No public exploit code or active exploitation has been identified at time of analysis; EPSS sits at 0.24th percentile and CISA SSVC records exploitation status as none, classifying this as a theoretical-but-patched risk for organizations that deploy promptly.
Use-after-free in Chrome's Chromoting (remote desktop) component allows a remote, unauthenticated attacker to potentially execute arbitrary code outside the browser sandbox via crafted network traffic, affecting all Chrome versions prior to 152.0.7977.65. The sandbox-escape dimension elevates this beyond a typical renderer vulnerability, as successful exploitation could yield code execution in a broader process context. No public exploit identified at time of analysis and SSVC indicates no observed exploitation, but the technical impact is rated total.
Sandbox-escaping remote code execution affects Google Chrome on macOS before 152.0.7977.65 through a use-after-free in the browser's Bluetooth component (CVE-2026-79091). A remote attacker who lures a victim into opening a crafted HTML page can trigger the freed-memory reuse to run arbitrary code outside the renderer sandbox, giving control of the host process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the sandbox-escape scope change drives a 9.6 CVSS base score despite Chromium's own Medium severity rating.
Sandbox-escaping remote code execution affects Google Chrome desktop before 152.0.7977.65, where a use-after-free in the ServiceWorker component lets a remote attacker run arbitrary code outside the renderer sandbox when a victim opens a crafted HTML page. The CVSS 3.1 score of 9.6 reflects the scope change (sandbox escape) and full CIA impact, though Google rated the Chromium severity only Medium and CISA's SSVC framework marks exploitation as none. No public exploit or CISA KEV listing exists at time of analysis, so risk is currently theoretical but high-impact.
Sandbox-escaping remote code execution affects Google Chrome on macOS prior to 152.0.7977.65, where a use-after-free in the Network component lets a remote attacker who convinces a victim to install a crafted extension run arbitrary code outside the renderer sandbox. Google rates the Chromium severity Medium, but the CVSS 9.6 reflects the scope-changing sandbox escape. No public exploit is identified at time of analysis and it is not on CISA KEV; EPSS is low at 0.24%.
Local privilege escalation in Android 16 and 17 exploits a confused deputy (CWE-441) vulnerability present across multiple system locations, allowing a low-privileged local process to read and write files it is not authorized to access. An attacker with basic application execution on the device can trigger a privileged system intermediary to operate on restricted files using its own elevated credentials, achieving full local privilege escalation without any user interaction. No public exploit exists at time of analysis, and CISA SSVC assessment confirms no observed active exploitation.
Local privilege escalation in Android 16 through 17 exploits incorrect authorization (CWE-863) across multiple URI access control locations, allowing a low-privileged process to bypass permissions checks and achieve full read/write/execute access on the device without requiring user interaction. Reported by security@android.com and addressed in the September 2026 Android Security Bulletin, the flaw affects Android 16, Android 16-QPR2, and Android 17. No public exploit has been identified and EPSS sits at the 2nd percentile, though SSVC rates the technical impact as total.
Heap buffer overflow in Android's OAPV video codec decoder (oapv.c) enables remote code execution on Android 16 and 17 without requiring user interaction. The flaw resides in dec_frm_prepare(), where insufficient bounds checking during frame decoding preparation allows an attacker to overwrite heap memory via crafted video content. EPSS sits at 0.18% (8th percentile) with SSVC exploitation status rated 'none', but technical impact is classified as 'total' and no public exploit has been identified at time of analysis.
Local privilege escalation in Android's Setup Wizard allows a low-privileged attacker to force the device to connect to a malicious network by exploiting a confused deputy relationship (CWE-441), achieving full C:H/I:H/A:H compromise without any user interaction. The flaw is addressed in the September 2026 Android Security Bulletin (patch level 2026-09-01) and requires only an existing low-privilege foothold on the device. No public exploit code has been identified, and EPSS sits at 0.11% (2nd percentile), indicating negligible observed exploitation probability at time of analysis.
Local privilege escalation in Android's Slice permission subsystem allows a low-privileged installed application to bypass permission checks via a confused deputy flaw in SlicePermissionActivity.java's onCreate method. Affecting Android 14 through 17 (including the 16-QPR2 branch), the vulnerability requires no user interaction and grants full C:H/I:H/A:H impact on a successful device. No public exploit has been identified at time of analysis, and EPSS scoring (0.12%, 2nd percentile) reflects low current exploitation activity.
Local privilege escalation in Android's ChannelImpl.java allows a low-privileged installed application to launch arbitrary intents by exploiting improper input validation in the initAppLinkTypeAndIntent method. Affected versions span Android 14 through 17, including 16-QPR2. Exploitation requires user interaction, limiting automated attack at scale - SSVC confirms no observed exploitation and EPSS sits at 0.11% (2nd percentile), consistent with the local-access, user-interaction gating.
Local privilege escalation in Android 16, 16-QPR2, and 17 is possible via Intent Redirection by exploiting a logic error in ActivityStarter.java's resolveActivity method. A locally-installed malicious application with basic user privileges can craft or intercept Intents to gain unauthorized access to protected system components, achieving full confidentiality, integrity, and availability compromise of the device without requiring any user interaction after installation. EPSS is 0.12% (2nd percentile) and no active exploitation or public POC has been identified at time of analysis.
Silent NFC payment session hijacking in Android 15 and 16 allows a locally-installed low-privilege application to exploit missing permission checks in NfcService.java, enabling unauthorized manipulation of NFC payment sessions without any user interaction. The flaw is a missing authorization gate (CWE-862) across multiple functions in the NFC service, permitting a malicious app to hijack, enable, or redirect contactless payment flows targeting the device. No public exploit has been identified and CISA SSVC rates exploitation as none, though the financial-fraud potential elevates practical risk beyond what the EPSS score of 0.11% suggests.
Remote code execution in Android's MatroskaExtractor component (MatroskaExtractor.cpp) affects Android 14, 15, 16, and 16-qpr2 via an improper type cast during Matroska/MKV media container parsing. A low-privileged remote attacker can exploit this flaw without user interaction to achieve full confidentiality, integrity, and availability compromise on the target device. No public exploit has been identified at time of analysis, and EPSS stands at 0.15%, though the zero-interaction requirement and full-impact CVSS 8.8 rating warrant prompt patching.
Background activity launch (BAL) restrictions in Android 15, 16, 16-qpr2, and 17 can be bypassed by a locally installed application exploiting a confused deputy pattern spanning multiple framework functions. A low-privileged app manipulates one or more privileged Android system components into launching background activities on its behalf, circumventing protections designed to block unauthorized UI intrusion and enabling local privilege escalation with full confidentiality, integrity, and availability impact. No public exploit has been identified at time of analysis; EPSS at 0.12% (2nd percentile) reflects low observed exploitation activity despite the 7.8 CVSS score.
Remote privilege escalation in the Android Bluetooth stack (AdapterService.java) allows an attacker to bypass device pairing entirely. A logic error in handleBondStateChanged lets a bond be treated as established without the normal pairing/consent flow, granting the attacker elevated privileges on Android 15, 16, 16-qpr2, and 17 with no user interaction. Google rates it CVSS 9.8; no public exploit is identified and CISA's SSVC framework records exploitation status as none, and EPSS is very low (0.16%).
Remote code execution across Android versions 14 through 17 is possible via a use-after-free condition triggered by a race condition in multiple OS locations. The CVSS vector (AV:N/AC:H/PR:L/UI:N) places this as a network-reachable, low-privilege attack requiring no user interaction but demanding precise timing due to the race condition mechanics, with full confidentiality, integrity, and availability impact on successful exploitation. No public exploit code has been identified at time of analysis, and the EPSS score of 0.16% (6th percentile) reflects low current observed exploitation pressure despite the broad attack surface spanning essentially all actively supported Android versions.
Local privilege escalation in Android's AppRestrictionsFragment allows a low-privileged app to gain unauthorized read/write access to private files via a confused deputy in the assertSafeToStartCustomActivity method. Affected versions span Android 14, 15, 16, 16-QPR2, and 17, making this a broad-surface vulnerability across the current Android ecosystem. With PR:L/UI:N, a malicious installed app can silently exploit this without user interaction to achieve full local C:H/I:H/A:H impact. No public exploit identified at time of analysis; EPSS is 0.11% (2nd percentile).
Multi-user isolation breaks in Android's ClipboardService framework layer (CWE-284 Improper Access Control) across Android 14 through 17, enabling a locally-executed low-privileged process to cross user-profile boundaries and escalate privileges with full confidentiality, integrity, and availability impact. The logic error in setClipboardAccessNotificationsEnabledForUser fails to correctly enforce per-user access checks, allowing one user context to manipulate clipboard access notification state for other user profiles on the same device. No public exploit has been identified at time of analysis, and EPSS of 0.12% places this at the 2nd percentile for near-term exploitation probability.
Local privilege escalation in Android's PaymentDefaultDialog allows an attacker with standard app-level execution to silently replace the device's default NFC payment application via a confused deputy in the component's onCreate method. Affecting Android 15, 16, 16-qpr2, and 17, the flaw is patched in the September 2026 Android Security Bulletin. No public exploit has been identified at time of analysis, and EPSS sits at 0.11%, consistent with SSVC's 'Exploitation: none' designation despite the high technical impact potential.
Intent redirection bypass in Android's ActivityManagerService enables a low-privileged local app to escalate privileges and gain full device access without any user interaction. The logic error in addCreatorToken of ActivityManagerService.java corrupts the creator-token mechanism that governs Intent origin and authority, allowing a malicious app to redirect Intents to system-protected components that should be inaccessible to it. EPSS at 0.13% (3rd percentile) and no CISA KEV listing indicate limited observed exploitation; no public exploit has been identified at time of analysis.
Local privilege escalation via use-after-free in Android 16-QPR2 and Android 17 allows a low-privileged local attacker to gain full system access with no user interaction required. The vulnerability arises from a logic error present at multiple code locations within the Android codebase, triggering a use-after-free condition that corrupts memory and enables privilege elevation to system or root level. No public exploit has been identified at the time of analysis, and EPSS sits at 0.12% (2nd percentile), consistent with no observed active exploitation.
Local privilege escalation in Android's Settings app (SettingsFragment.java) affects Android 14 through 17, including 16-qpr2, allowing a low-privileged local attacker to gain full device control via misleading or insufficient UI in the getItemList method. No victim interaction is required - the attacker's own low-privileged app or session is sufficient to trigger the UI bypass. EPSS is 0.12% (2nd percentile) and SSVC records no active exploitation, but SSVC simultaneously rates technical impact as total, reflecting the severity of a successful attack despite limited observed real-world activity.
Local privilege escalation in Android 14, 15, and 16 stems from improper encryption key validation caused by a logic error (CWE-347) present across multiple code locations. A low-privileged local attacker can exploit the flawed key verification path to gain full confidentiality, integrity, and availability impact over the device without requiring user interaction or elevated starting privileges. No public exploit has been identified at time of analysis, and EPSS probability sits at 0.11% (2nd percentile), but the vulnerability spans multiple Android versions in active deployment.
Out-of-bounds write in Android's camera metadata validation logic (validate_camera_metadata_structure in camera_metadata.c) allows a local low-privileged attacker to escalate privileges to a higher-privileged context with full confidentiality, integrity, and availability impact. Affects Android 14 through 16-qpr2, patched in the September 2026 Android Security Bulletin. No public exploit code or active exploitation has been identified; EPSS sits at the 2nd percentile and SSVC rates exploitation as none.
Tapjacking and UI overlay exploitation in Android 16-QPR2's `InstallLaunch.kt` `onCreate` method allows a locally-installed malicious application to present a deceptive interface over the package installation workflow, leading to local privilege escalation with full confidentiality, integrity, and availability impact. Fixed in Google's September 2026 Android Security Bulletin, the flaw requires no additional execution privileges and - per the CVSS vector - no user interaction beyond what occurs during the overlay setup phase. No public exploit code and no active exploitation have been identified at time of analysis; EPSS sits at 0.11% (2nd percentile).
Local privilege escalation in Android 16 and 16-QPR2 allows a low-privileged app to escalate to full device control by exploiting a logic error in HostEmulationManager.java that permits unauthorized background activity launches. The flaw stems from CWE-693 (Protection Mechanism Failure) in the activity-launch gating logic, enabling an installed malicious app to bypass Android's background activity restrictions without requiring additional permissions or user interaction. No public exploit has been identified and CISA has not added this to KEV, but SSVC rates the technical impact as total given that successful exploitation yields C:H/I:H/A:H on the device.
Local privilege escalation in Android's BackgroundLaunchProcessController allows a low-privileged app or user process to launch background activities beyond its permitted scope due to a logic error in the areBackgroundActivityStartsAllowed gating function. Affected versions span Android 14 through Android 16-QPR2, covering the vast majority of modern Android devices in active use. With PR:L and UI:N, exploitation requires only a foothold as a regular user-space app - no user interaction or elevated permissions - making it a reliable post-installation escalation primitive. No public exploit exists and CISA SSVC rates exploitation as none at time of analysis.
Privilege escalation in Google Cloud Integration Connectors (HTTP Connector component) allows an authenticated low-privilege user to attach an unauthorized service account to a connector, effectively taking over the associated Google Cloud Project. Affected versions are those deployed prior to the 2025-12-11 server-side patch, which Google applied automatically with no customer action required. No public exploit has been identified at time of analysis, but the CVSS 4.0 vector reflects high subsequent-system impact across confidentiality, integrity, and availability - matching a full project compromise scenario.
Path traversal in Google Cloud Agent Development Kit (ADK) Python versions 1.9.0 through 1.21.0 exposes arbitrary server files to unauthenticated remote attackers via a crafted `file_path` query parameter on the builder endpoint. The root cause, confirmed by the upstream commit diff, is that `fast_api.py` passed the user-supplied path directly into filesystem operations without sanitization or boundary enforcement, allowing `../` sequences to escape the agents directory. No public exploit code or active exploitation has been identified; vendor-released fix is available in v1.22.0.
Analysis complete. The JSON synthesis is above. Key findings for **CVE-2026-78745** (Weyon/HiDPT HiDPTAndroid on Hi3751V350): - **Vulnerability**: Unauthenticated RCE via a network-reachable ADB daemon (adbd) with authorization bypassed/disabled — CWE-284, an exposed privileged debug interface, not a memory bug. - **Signals cross-referenced**: CVSS 9.8 is technically defensible on affected devices, but EPSS is low (0.42%, 35th pct), it's not in KEV, and a public PoC exists (`n0c71v3x/CVE-2026-78745`). Real-world exposure is bounded by whether adbd is reachable beyond the LAN — consumer TVs typically sit behind NAT. - **Metadata problems flagged**: wrong "Google" vendor tag (Android-based ≠ Google product), "N A" placeholder tag, and an `n/a:n/a` CPE. No prompt-injection note was present in this input (it was clean). Saved to memory as `cve-2026-78745.md` with an index entry.
Sandbox-escape remote code execution affects Google Chrome on iOS prior to 152.0.7977.82, where improper input validation (CWE-20) in the browser's Transactions Platform component lets a remote attacker potentially run arbitrary code outside the renderer sandbox when a victim loads a crafted HTML page. Google shipped a fix in the stable channel and Chromium rated the underlying issue Medium severity, though the supplied CVSS vector scores it 9.6. There is no public exploit identified and CISA's SSVC framework records exploitation status as none.
Type confusion (CWE-843) in the Compositing subsystem of Google Chrome prior to 152.0.7977.82 enables unauthenticated remote attackers to execute arbitrary code within the renderer sandbox by delivering a crafted HTML page to a victim. Execution is confined to Chrome's renderer process rather than the underlying OS - a full host compromise would require chaining with a separate sandbox escape primitive. No public exploit or active exploitation (KEV) has been identified at time of analysis; SSVC rates Exploitation: none and Automatable: no.
Use-after-free in Skia, Chrome's 2D graphics rendering engine, allows remote attackers to execute arbitrary code within the Chrome renderer sandbox by luring a user to a crafted HTML page. Affected versions are all Chrome releases prior to 152.0.7977.82 across desktop platforms. The sandbox confinement means this vulnerability alone does not yield full system compromise - a chained sandbox escape would be required for that - but the renderer-process code execution is rated high impact by Chromium's internal severity team. No public exploit or CISA KEV listing is present at time of analysis; SSVC labels exploitation as none and the attack as non-automatable due to the required user interaction.
Remote code execution in Google Chrome's DevTools component before 152.0.7977.82 lets a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and carries a CVSS 9.6 with scope change, reflecting sandbox escape. Google has shipped a fix; per CISA's SSVC assessment there is no evidence of active exploitation and no public exploit identified at time of analysis.
Sandboxed remote code execution in Google Chrome's CacheStorage API (prior to 152.0.7977.82) allows a remote attacker to execute arbitrary code inside the Chrome renderer sandbox by luring a user to visit a specially crafted HTML page. The root cause is CWE-668 (Exposure of Resource to Wrong Sphere), where CacheStorage improperly exposes resources to an unintended security context. No public exploit code has been identified and SSVC reports exploitation status as none, though the patch is available and update is strongly recommended.
Remote code execution in Google Chrome for Android before 152.0.7977.82 stems from an out-of-bounds write in the WebGL implementation, letting a remote attacker escape the browser sandbox and run arbitrary code simply by luring a victim to a crafted HTML page. Rated Chromium severity High and CVSS 9.6, the flaw is notable because exploitation breaks out of the renderer sandbox rather than being contained by it. There is no public exploit identified at time of analysis, and CISA SSVC lists exploitation status as none.
In-sandbox arbitrary code execution in Google Chrome's V8 JavaScript engine (all versions prior to 152.0.7977.82) is achievable by a remote unauthenticated attacker who tricks a user into visiting a specially crafted HTML page. The underlying flaw is a CWE-367 Time-of-Check Time-of-Use (TOCTOU) race condition within V8, allowing the attacker to win a memory-access race and redirect execution flow inside the Chrome renderer sandbox. No public exploit code has been identified and CISA SSVC rates exploitation as 'none' at time of analysis, though the technical impact is rated 'total' within the sandbox boundary.
Use-after-free in Chrome's Compositing component (versions prior to 152.0.7977.82) enables a sandbox escape when chained with a renderer-process compromise - an attacker who has already gained control of the renderer can corrupt memory in the Compositing layer and execute arbitrary code outside Chrome's sandbox boundary on the host operating system. The CVSS S:C (scope changed) metric confirms this is a privilege-escalation-across-boundary primitive, delivering full C:H/I:H/A:H impact against the underlying OS. A vendor patch is available in Chrome 152.0.7977.82, and no public exploit has been identified at time of analysis.
System access-restriction bypass in Google Chrome's Network component (versions prior to 152.0.7977.82) lets a remote attacker use crafted network traffic to circumvent enforced access controls, stemming from incomplete resource cleanup (CWE-459). The flaw carries a Chromium-rated High severity and a CVSS of 9.1 reflecting high confidentiality and availability impact; no public exploit is identified at time of analysis and EPSS is low (0.22%). Google fixed it in the 2026-09 stable desktop channel update.
Type confusion in V8 (Chrome's JavaScript engine) in versions prior to 152.0.7977.82 enables unauthenticated remote attackers to execute arbitrary code within Chrome's renderer sandbox by enticing a user to visit a specially crafted HTML page. The flaw exploits V8's type system, allowing an attacker to manipulate object type metadata in the JavaScript heap to gain controlled memory access and code execution inside the renderer process. No public exploit or CISA KEV listing has been identified at time of analysis, though V8 type confusion vulnerabilities in Chrome have historically attracted rapid weaponization given the browser's enormous attack surface and attacker interest.
Sandbox escape and out-of-sandbox arbitrary code execution in Google Chrome (desktop) before 152.0.7977.75, rooted in an incorrect authorization flaw in the FileSystem component. A remote attacker who lures a victim into opening a crafted HTML page can break out of the renderer sandbox and run code with the privileges of the browser process. Rated High by Chromium and CVSS 9.6; the vendor has shipped a stable-channel patch, though no public exploit code or active exploitation has been identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in the Shared Tab Groups feature (CWE-416). A remote attacker who lures a victim into visiting a crafted HTML page can corrupt freed memory to execute arbitrary code outside the renderer sandbox. Chromium rates the severity Critical (CVSS 9.6); the vendor has shipped a fix, but no public exploit has been identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in the WebGL implementation, letting a remote attacker who lures a victim to a crafted HTML page execute arbitrary code OUTSIDE the renderer sandbox. Rated Critical by Chromium with a CVSS 9.6 (scope-changed) vector; a vendor patch shipped in the September 2026 Stable channel update. No public exploit identified at time of analysis, though the tracker bug (issues.chromium.org/546260492) and Google's own reporting indicate the flaw is well characterized.
Stack-based buffer overflow in the GPU component of Google Chrome on Windows (prior to 152.0.7977.75) enables full sandbox escape and arbitrary code execution on the host operating system. Exploitation is a two-stage chained attack: an attacker must first compromise the renderer process (via a separate vulnerability or exploit), then leverage this GPU flaw to break out of Chrome's sandbox and execute code with elevated host privileges. Google has released a patch in the stable channel update for desktop; no public exploit code or CISA KEV listing has been identified at time of analysis.
Use-after-free in Chrome's TabStrip component enables remote code execution outside the renderer sandbox in Google Chrome versions prior to 152.0.7977.75. An attacker must social-engineer a user into a specific UI interaction to trigger the memory-corruption primitive, after which arbitrary code executes at browser-process privilege - a full sandbox escape. Google has issued a stable channel patch; no public exploit or CISA KEV listing has been identified at time of analysis.
Use-after-free in Google Chrome's Browser process prior to version 152.0.7977.75 enables sandbox escape, allowing an attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The CVSS vector (AV:N/AC:H/S:C/C:H/I:H/A:H) reflects both the network-reachable delivery and the scope change from renderer to host-level execution. No public exploit or CISA KEV listing has been identified at time of analysis, but sandbox-escape primitives of this class are highly valued in exploit chains.
Remote code execution inside Chrome's sandbox is achievable via a use-after-free in WebRTC, triggered when a victim visits a specially crafted HTML page. Affected versions are all Chrome releases prior to 152.0.7977.75 across desktop platforms. No public exploit code or CISA KEV listing has been identified at time of analysis, though the sandboxed execution boundary limits the practical impact compared to the raw CVSS 8.8 score - Google's own Chromium severity rating of 'Medium' reflects this containment.
Sandbox escape in Google Chrome's TabStrip component (versions prior to 152.0.7977.75) allows a remote attacker who has already achieved renderer process compromise to execute arbitrary code outside the Chrome sandbox via incorrect authorization in tab management IPC. The attack chain requires two conditions to be met simultaneously: a prior renderer exploit and social engineering to deliver a crafted HTML page - placing this firmly in the chained-exploit category despite the high CVSS base score. A vendor-released patch is available in Chrome 152.0.7977.75; no public exploit code or active exploitation has been identified at time of analysis.
Sandbox escape in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows allows a local attacker to execute arbitrary code outside the Chrome sandbox via a crafted local program, affecting all Chrome for Windows versions prior to 152.0.7977.75. The root cause is incorrect authorization (CWE-863) within the Chromoting subsystem, where flawed authorization logic fails to restrict a local program from interacting with Chromoting in a way that crosses the sandbox boundary. Google has released a patched version (152.0.7977.75), and no public exploit has been identified at time of analysis, though the full post-sandbox C:H/I:H/A:H impact warrants prompt remediation.
Remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in Dawn, Chrome's WebGPU/GPU graphics abstraction layer, and - per Google's advisory - allows a crafted HTML page to execute arbitrary code outside the renderer sandbox. Exploitation only requires an unauthenticated victim to visit a malicious page, giving the attacker high-impact code execution on the device. No public exploit has been identified at time of analysis and the issue is not in CISA KEV, though the sandbox-escape framing makes it a high-priority browser patch.
Remote code execution within the browser sandbox is possible in Google Chrome versions prior to 152.0.7977.75 due to a use-of-uninitialized-resource flaw (CWE-908) in the V8 JavaScript engine. An attacker can trigger the vulnerability by luring a user to a crafted HTML page, with no authentication or special privileges required beyond normal web browsing. Google has released the patched build 152.0.7977.75; SSVC rates exploitation status as none and no CISA KEV listing has been identified at time of analysis.
Access-restriction bypass in Google Chrome desktop prior to 152.0.7977.75 lets a remote attacker who first tricks a user via social engineering leverage a co-installed application to escape Chrome's system access boundaries. The flaw is an improper input validation (CWE-20) issue in the browser's DataTransfer component, rated High by Chromium and fixed in the September 2026 Stable channel. EPSS is low (0.16%, 5th percentile), no public exploit or CISA KEV listing exists, so realistic risk is bounded by the required user interaction and the presence of a malicious co-installed app.
Remote code execution in Google Chrome desktop before 152.0.7977.75 stems from a use-after-free in the Proxy component that a remote attacker can trigger with crafted network traffic to run arbitrary code OUTSIDE the browser sandbox. Google rates the Chromium severity High and a patched Stable channel build is available; no public exploit code has been identified at time of analysis. Because the flaw yields a sandbox escape rather than a contained renderer bug, successful exploitation gives attacker-controlled code on the host at browser-process privilege.
Unauthenticated arbitrary file upload in the WPLP Cookie Consent (GDPR/CCPA cookie banner) plugin for WordPress, versions up to and including 4.4.1, allows remote attackers to plant executable files on the server and potentially achieve remote code execution. The flaw stems from missing file-type validation in the saas_upload_logo() function combined with an authorization bypass on the WPLP connector REST endpoints, so no login is required. Reported by Wordfence and carrying a CVSS of 9.8; no public exploit identified at time of analysis.
Unreviewed code execution in Google Cloud Build (GitHub-triggered builds prior to the 2026-06-24 fix) allowed a remote attacker to bypass the GitHub Trigger Comment Control approval gate via webhook suppression and run attacker-supplied code inside the build environment. The Comment Control feature is meant to require a maintainer's approval comment before a pull request from an outside contributor triggers a build; the flaw let that check be evaded so unapproved code executed. No public exploit identified at time of analysis, and Google states the issue was patched server-side with no customer action required.
Server-side request forgery in jina-ai reader allows unauthenticated remote attackers to reach cloud metadata services and internal HTTP endpoints by supplying publicly resolvable hostnames that map to private IP addresses. The private-address guard - intended to block RFC 1918 and metadata service IPs - is only enforced when the service runs inside Google Cloud, leaving all other deployment environments (AWS, Azure, on-premises) completely unprotected by this control. Successful exploitation in cloud-hosted deployments can yield instance metadata including IAM credentials and access tokens. No public exploit code has been identified at time of analysis, and this CVE is not currently listed in CISA KEV.
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.
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).
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.
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.
Server-side request forgery in the GitLab AI Gateway (Duo Agent Platform) lets an authenticated user redirect outbound model requests to an attacker-controlled endpoint by supplying a crafted inline flow configuration that overrides the HTTP Host header, exfiltrating Google Cloud Vertex service credentials and private signing keys. It affects AI Gateway 18.10 through 19.0.11, 19.1 through 19.1.6, and 19.2 through 19.2.1. Publicly available exploit code exists (HackerOne #3945100); EPSS is low at 0.19% and it is not in CISA KEV.
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.
Remote code execution in Time4Popcorn - a Popcorn Time media-streaming fork - affects the Windows client (<= 6.2.1.18), macOS client (<= 6.2.1.17), and Android client (<= 3.5.0.173) through the application's auto-update mechanism (updater.exe on Windows, the PT.updd component on macOS). Because the updater fetches and executes update payloads without verifying their integrity (CWE-494), an attacker able to influence the update channel can deliver and run arbitrary code on the victim host. No CISA KEV listing, no public exploit is identified at time of analysis, and EPSS is low at 0.26% (18th percentile).
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.
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.
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.
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%).
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.
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.
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.
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.
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.
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.
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.
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.
Remote code execution inside the Chrome sandbox is possible through a race condition in the Extensions component, exploitable via crafted network traffic against Google Chrome versions prior to 152.0.7977.65. Despite a CVSS score of 8.1, Chrome's own team rates this vulnerability Low severity - a notable divergence explained by the sandbox constraint: successful exploitation yields in-sandbox code execution rather than full OS-level compromise. No public exploit identified at time of analysis, and SSVC confirms no known active exploitation and that the attack cannot be automated reliably.
Use-after-free in Google Chrome's DevTools component (all versions prior to 152.0.7977.65) enables remote attackers to execute arbitrary code inside the Chrome sandbox by distributing a crafted extension through social engineering. The CVSS 8.8 score reflects high confidentiality, integrity, and availability impact within the process scope, though exploitation is constrained by the mandatory user interaction required to install the malicious extension. No public exploit code exists and SSVC rates active exploitation as none at time of analysis, placing real-world urgency below what the raw score implies.
Improper state validation in Google Chrome's HTML parser (all versions prior to 152.0.7977.65) enables remote code execution within the browser's renderer sandbox when a user visits a crafted HTML page. The flaw (CWE-754) requires no authentication and minimal user interaction - simply loading malicious HTML is sufficient - but execution is constrained to the renderer sandbox (scope unchanged, S:U). Despite an 8.8 CVSS score, EPSS sits at 0.21% (12th percentile) and CISA SSVC confirms no current exploitation, with no public exploit or KEV listing identified at time of analysis.
Remote code execution in Google Chrome prior to 152.0.7977.65 stems from improper input validation in the browser's Media component, enabling a remote attacker to potentially execute arbitrary code outside the sandbox when a user visits a crafted HTML page. The vulnerability carries a CVSS base score of 8.8, affects all desktop Chrome builds below 152.0.7977.65 across Windows, macOS, and Linux, and is classified under CWE-20. No public exploit has been identified at time of analysis, and CISA SSVC rates current exploitation as none despite a total technical impact rating.
Remote code execution outside the browser sandbox is achievable in Google Chrome prior to 152.0.7977.65 via improper input validation in the Media component, triggered by visiting a crafted HTML page. The sandbox escape aspect is the critical differentiator here - Chrome's multi-process sandbox is its primary defense-in-depth layer, so bypassing it yields native OS-level code execution under the victim's account. No public exploit identified at time of analysis, and SSVC classifies exploitation as none with the attack non-automatable due to required user interaction.
Sandbox escape in Google Chrome's Media component on Windows allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox via a crafted HTML page. Affected versions are all Chrome releases on Windows prior to 152.0.7977.65. No public exploit code or active exploitation has been identified at time of analysis; SSVC assessment confirms exploitation status as none, and EPSS probability is low at 0.26% (17th percentile), though SSVC technical impact is rated total given full sandbox bypass capability.
Insufficient control flow management in Google Chrome's DevTools component (versions prior to 152.0.7977.65) enables remote attackers to execute arbitrary code inside the browser sandbox by tricking a user into loading a crafted HTML page via social engineering. The flaw is rooted in CWE-691 and permits attacker-controlled code paths within the DevTools subsystem, with execution constrained to within the Chrome sandbox (S:U). No public exploit code has been identified at time of analysis, and both EPSS (0.21%, 12th percentile) and SSVC (exploitation: none, automatable: no) indicate low current exploitation probability despite the high CVSS 8.8 base score.
Type confusion in Google Chrome's DevTools component prior to version 152.0.7977.65 enables remote code execution within the browser sandbox when a victim is social-engineered into visiting a crafted HTML page. The flaw affects all Chrome platforms where DevTools is accessible and results in high confidentiality, integrity, and availability impact to the sandboxed process. No public exploit code has been identified at time of analysis, and SSVC assessment confirms no observed active exploitation, though the technical impact rating is classified as total.
Use-after-free in V8, Google Chrome's JavaScript engine, prior to version 152.0.7977.65 enables remote attackers to execute arbitrary code within the Chrome sandbox by luring a user to a crafted HTML page. The CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R) confirms low-complexity, unauthenticated network delivery requiring only a single user visit, with high confidentiality, integrity, and availability impact scoped to the renderer process. No public exploit code has been identified at time of analysis, and SSVC rates exploitation as none with a non-automatable attack path, though technical impact is assessed as total within the sandbox.
Remote code execution within the Chrome sandbox is achievable via a race condition in the V8 JavaScript engine, affecting all Google Chrome versions prior to 152.0.7977.65. An unauthenticated remote attacker (per CVSS PR:N) can trigger the vulnerability by luring a user to a crafted HTML page, exploiting a timing window in V8's memory management to execute arbitrary code. No public exploit code or active exploitation has been identified at time of analysis; EPSS sits at 0.24th percentile and CISA SSVC records exploitation status as none, classifying this as a theoretical-but-patched risk for organizations that deploy promptly.
Use-after-free in Chrome's Chromoting (remote desktop) component allows a remote, unauthenticated attacker to potentially execute arbitrary code outside the browser sandbox via crafted network traffic, affecting all Chrome versions prior to 152.0.7977.65. The sandbox-escape dimension elevates this beyond a typical renderer vulnerability, as successful exploitation could yield code execution in a broader process context. No public exploit identified at time of analysis and SSVC indicates no observed exploitation, but the technical impact is rated total.
Sandbox-escaping remote code execution affects Google Chrome on macOS before 152.0.7977.65 through a use-after-free in the browser's Bluetooth component (CVE-2026-79091). A remote attacker who lures a victim into opening a crafted HTML page can trigger the freed-memory reuse to run arbitrary code outside the renderer sandbox, giving control of the host process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the sandbox-escape scope change drives a 9.6 CVSS base score despite Chromium's own Medium severity rating.
Sandbox-escaping remote code execution affects Google Chrome desktop before 152.0.7977.65, where a use-after-free in the ServiceWorker component lets a remote attacker run arbitrary code outside the renderer sandbox when a victim opens a crafted HTML page. The CVSS 3.1 score of 9.6 reflects the scope change (sandbox escape) and full CIA impact, though Google rated the Chromium severity only Medium and CISA's SSVC framework marks exploitation as none. No public exploit or CISA KEV listing exists at time of analysis, so risk is currently theoretical but high-impact.
Sandbox-escaping remote code execution affects Google Chrome on macOS prior to 152.0.7977.65, where a use-after-free in the Network component lets a remote attacker who convinces a victim to install a crafted extension run arbitrary code outside the renderer sandbox. Google rates the Chromium severity Medium, but the CVSS 9.6 reflects the scope-changing sandbox escape. No public exploit is identified at time of analysis and it is not on CISA KEV; EPSS is low at 0.24%.