Monthly
Memory corruption via use-after-free in Microsoft Edge (Chromium-based) lets a remote attacker run arbitrary code at elevated privilege in the browser and ultimately on the host, provided the victim opens attacker-controlled content. Microsoft scores it 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), so no credentials are needed but a single user visit is — a classic one-click browser exploitation pattern rather than a zero-click worm. The intelligence feed contains no EPSS score, no CISA KEV listing, and no public exploit reference, so at time of analysis this is a high-severity but not yet observed-exploited issue.
We need to produce JSON with fields. Need to be careful about "opole" in risk_assessment only, once, lowercase, natural prose, not a factual claim about who is affected. Something like "even a mid-sized municipal IT team in opole would likely..." Hmm it's a hypothetical illustrative reference, must not be presented as factual claim about who is affected. I'll phrase: "for instance, even a mid-sized IT team in opole..." That's hypothetical illustration. Should be fine. Keep once. Data: CVE-2026-69486, Microsoft Edge Chromium-based heap buffer overflow, CVSS 8.8 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-122. Patch available from vendor. Affected versions EUVD: Microsoft Edge (Chromium-based) 1.0.0.0 <153.0.4234.32. Reference MSRC. Tags include "Google" which is likely a mislabeled tag — Edge is Chromium-based, but "Google" tag on a Microsoft Edge CVE? Could be mislabeled. Hmm. The tag "Google" might refer to Google Chrome/Chromium? The CVE is Microsoft Edge. Flag mislabeled_tag "Google" with suggested "microsoft" or maybe "chromium"? Actually tags include "Microsoft" already. The "Google" tag is probably wrong vendor for a Microsoft Edge vulnerability — although Chromium is Google's project. Is it clearly wrong? Edge is Chromium-based, so a Google tag is arguably not strictly wrong but for vendor tagging it's mislabeled — the affected product is Microsoft Edge. Confidence medium? The instruction says only emit flag when clearly wrong and verifiable. Hmm, "Google" tag on Microsoft Edge CVE — Edge is built on Chromium (Google's open source project). But the vendor is Microsoft. I'd say medium confidence mislabeled_tag. Alternatively don't flag. Given the editorial note mentions nothing about tags. I think emitting one flag with medium confidence is acceptable: target "Google", suggested null or "microsoft"? Suggested is correct/canonical slug if known: "microsoft" already exists in tags. Maybe suggested null since "Google" isn't the right vendor and Microsoft is alread
We need produce JSON only. Need analyze. We have CVE data. Need synthesize all fields. Let's parse carefully. CVE-2026-91749: Use after free in Workers in Google Chrome prior to 153.0.8010.47 allowed remote attacker potentially execute arbitrary code outside sandbox via crafted HTML page. Critical. CVSS 9.6 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. CWE-416. Patch available vendor. Tags: RCE, Denial Of Service, Google, Use After Free, Memory Corruption. SSVC exploitation none, automatable no, technical impact total. EUVD affected versions weird "Chrome 153.0.8010.47 <153.0.8010.47" probably should be < 153.0.8010.47? Maybe formatting error. References to Chrome releases and issue. Need field product_name 1-3 words: "Google Chrome". Summary: original synthesis. Mention use after free in Workers in Google Chrome before 153.0.8010.47; remote attacker via crafted HTML page could execute arbitrary code outside sandbox. Patch available. No active exploitation per SSVC/KEV? Input lacks KEV status but SSVC says exploitation none. POC? not provided. Need not say if KEV no. EPSS absent. Mention no public exploit identified? Since POC not provided but SSVC no exploitation. We can state "No active exploitation reported in available data; SSVC lists exploitation none." Do not copy description. Start with specific impact verb: "Remote code execution outside the sandbox in Google Chrome before 153.0.8010.47..." Is that ok. Mention UAF in Workers triggered by crafted HTML page. Critical severity. Could mention patch available. No KEV. EPSS not provided. Need not include. Technical_context: underlying technology: Google Chrome Workers (Web Workers/Service Workers?) Need be specific: Workers likely the browser's worker subsystem / threading implementation. UAF in Workers. CWE-416 use after free. CPE data? Input doesn't include CPE strings explicitly. EUVD affected versions. We can reference affected product version. Explain root cause: memory management error where object freed then re
A time-of-check-to-time-of-use race condition in the Extensions component of Google Chrome on macOS allows an attacker to break out of the renderer sandbox and execute arbitrary code in the browser process context. The barrier to entry is meaningful: the attacker must already have compromised the renderer process through a separate bug and then use social engineering to persuade the victim into a specific UI interaction that widens the race window. Affected builds are Chrome for macOS prior to 153.0.8010.47, and Google rates the issue High severity; no public exploit code or CISA KEV entry was identified at time of analysis.
Sandbox escape in Google Chrome prior to 153.0.8010.47 allows a remote attacker who has already compromised the browser's renderer process to execute arbitrary code outside the sandbox via a race condition (TOCTOU) triggered by a crafted HTML page; the user must visit that page for the flaw to be reachable. Google rates the issue Chromium security severity High and a vendor patch is available from the 153.0.8010.47 stable channel release. There is no public exploit code and no CISA KEV listing at time of analysis, and the high attack complexity combined with a required renderer-compromise precondition keeps realistic risk below the raw 8.3 CVSS score.
Type confusion in Chrome's CacheStorage implementation in builds prior to 153.0.8010.47 lets a remote, unauthenticated attacker execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page. The bug is rated High by Chromium and 8.8 by NVD (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), but it is a renderer-level compromise rather than a sandbox escape, so host impact requires chaining a second vulnerability. No CISA KEV listing and no public exploit code were identified at time of analysis, and no EPSS score was supplied in the input data.
Use-after-free in Chrome's DOM implementation allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page in Chrome versions prior to 153.0.8010.47. The flaw carries a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and is rated High by Chromium security severity; a vendor patch is available and no public exploit code or CISA KEV entry was identified at time of analysis.
Google Chrome versions earlier than 153.0.8010.47 contain an incorrect authorization flaw (CWE-863) in the WebUI subsystem that lets an attacker who already controls a compromised renderer process break out of the browser sandbox and run arbitrary code on the host via a crafted HTML page. Exploitation is a two-stage proposition: the attacker must first obtain renderer code execution, then chain this flaw to escape the sandbox, and the victim must load the malicious page. Google rates the Chromium security severity as High and has shipped a fix in Chrome 153.0.8010.47; no public exploit code or CISA KEV entry was identified in the available intelligence at time of analysis.
Incorrect authorization in Chrome's Core component on Windows (versions prior to 153.0.8010.47) lets a local attacker who can run a program on the machine break out of the browser sandbox and execute arbitrary code at the user's privilege level outside it. The flaw is rated High by the Chromium security team and carries CVSS 7.4 (AV:L/AC:H/PR:N/UI:N, C/I/A all High), reflecting a local-only but complete confidentiality, integrity and availability impact once the sandbox boundary is crossed. No public exploit code or CISA KEV listing was provided in the input, and Google has released a fixed stable-channel build, so this is best treated as a high-value chaining primitive rather than a currently mass-exploited issue.
Improper state validation in the Skia graphics library, as shipped in Google Chrome prior to 153.0.8010.47, lets an attacker who already controls a compromised renderer process read memory outside the browser sandbox by serving a crafted HTML page. Exploitation requires the victim to load the malicious page (UI:R) and depends on chaining with a separate renderer compromise, which is why the vector carries AC:H despite the network attack path. Vendor status is "Patch available"; no public exploit code and no CISA KEV listing were present in the supplied intelligence, so the flaw should be treated as a sandbox-escape primitive rather than an observed, widely exploited issue.
Remote code execution inside the renderer sandbox affects Google Chrome desktop builds prior to 153.0.8010.47, caused by a type confusion flaw in the browser's compositing pipeline (CWE-843) that is reachable from a crafted HTML page. An attacker needs only to convince a user to load the page: the CVSS 3.1 vector is 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), so no credentials or privileges are required, but user interaction is mandatory. Google rates the issue Chromium security severity High and has shipped a fixed stable-channel build; no public exploit code or CISA KEV listing appears in the supplied intelligence, and no EPSS score was provided, so the current exploitation picture is best described as patch-now-but-not-known-exploited.
Integer overflow in V8 in Google Chrome prior to 153.0.8010.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Let me synthesize. CVE-2026-91727: Incorrect reference resolution in Extensions in Chrome on Mac prior to 153.0.8010.47. Local attacker who compromised renderer process could execute arbitrary code outside sandbox via a local program. CWE-706 (Use of Incorrectly-Resolved Name or Reference). CVSS 8.1 AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Product: Google Chrome (macOS). Product name 1-3 words: "Google Chrome". Prevalence: ubiquitous. Now fields. Summary: must not copy description; start with impact verb and product. E.g. "Sandbox escape in Google Chrome on macOS (prior to 153.0.8010.47) lets an attacker who has already compromised the renderer process escalate to code execution outside the browser sandbox..." Technical context: CWE-706 incorrect reference resolution in Extensions — extension API resolves a reference (name/path/identifier) incorrectly, allowing a local program to be loaded/executed outside sandbox. macOS-specific. Renderer compromise prerequisite. Risk assessment: CVSS 8.1 with AV:L AC:H PR:N UI:N S:C. EPSS not provided, KEV not provided. Patch available. No POC known. Attack requires renderer compromise (two-stage). S:C indicates sandbox escape crossing security scope. Not KEV → no public exploit identified at time of analysis. Note missing EPSS/KEV data explicitly. Affected products: Google Chrome on macOS versions prior to 153.0.8010.47; EUVD lists "Chrome 153.0.8010.47 <153.0.8010.47" which is malformed/likely means before 153.0.8010.47. Reference: chromereleases blog, chromium issue 516893912. Remediation: upgrade to 153.0.8010.47 or later. Chrome auto-update. macOS-specific. Compensating controls: restrict extension installs via enterprise policy, disable extensions, etc. Trade-offs. Exploit scenario: attacker chains a renderer RCE (e.g. via malicious web content) then exploits the extension reference resolution flaw to break out of sandbox and run native code on macOS host. Exploitation conditions: requires (1) macOS platform, (2) att
Google Chrome builds prior to 153.0.8010.47 carry a use-after-free in the browser's Input component that allows an attacker who already controls a compromised renderer process to escape the Chrome sandbox and run arbitrary code with the browser's privileges. Exploitation is not remote-standalone: it requires a chained renderer compromise plus a victim who opens a crafted HTML page, which is why the flaw is scored High (8.3) rather than Critical despite total technical impact. Google has shipped a fixed stable-channel build; no public exploit code has been identified and the issue is not listed in CISA KEV at time of analysis.
A use-after-free in Google Chrome's Internals component allows a remote attacker to potentially execute arbitrary code outside the browser sandbox when a victim opens a crafted HTML page, affecting all Chrome builds prior to 153.0.8010.47 on desktop. Exploitation requires user interaction (visiting the page) but no authentication or elevated privileges, and Google rates the Chromium security severity as Critical. Vendor-released patch: 153.0.8010.47. There is no public exploit code identified at time of analysis and no confirmed actively exploited (CISA KEV) status, though the SSVC framework assigns total technical impact.
Google Chrome on macOS versions prior to 153.0.8010.47 contain a race condition (TOCTOU) in the Extensions subsystem that lets an attacker who has already compromised the browser's renderer process break out of the sandbox and execute arbitrary code on the host, triggered when a victim loads a crafted HTML page. Google rated the issue High severity and Chromium's own severity assessment drove the 8.3 CVSS base score with a Scope change (S:C), reflecting that code execution crosses the renderer/sandbox boundary rather than staying contained. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, but a vendor patch is available and should be applied promptly because sandbox escapes are the high-value second stage of any Chrome exploit chain.
Type confusion in Google Chrome's ServiceWorker implementation before version 153.0.8010.47 allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox by getting a user to open a crafted HTML page. The flaw carries a CVSS base score of 8.8 (AV:N/AC:L/PR:N/UI:R), the classic memory-corruption profile for Chrome renderer bugs, and Google rated it High in its Chromium severity scheme. A vendor patch shipped in the 153.0.8010.47 stable release, and there is no public exploit code identified and no CISA KEV entry at time of analysis, so this is a prioritise-and-patch issue rather than a confirmed active campaign.
Remote code execution inside the Apache Airflow scheduler is possible through the Apache Kafka provider (apache-airflow-providers-apache-kafka) 1.15.0 to before 2.0.0, which resolves dotted-path strings from a Kafka connection's extra field into Python callables via import_string with no allowlist and hands them to the confluent-kafka client. An authenticated user whose only privilege is editing Airflow connections can thereby execute arbitrary code in the control plane when the non-default Kafka event producer (dag_run_events_enabled or task_instance_events_enabled) is switched on, exceeding the Airflow security model that limits connection-configuration users to code execution on workers. No public exploit code or CISA KEV listing was identified at time of analysis; deployments using Google Managed Kafka are not affected because that code path overwrites any user-supplied oauth_cb, while plain brokers and Amazon MSK are exposed.
Local privilege escalation in the Android kernel's Arm SMMUv3 driver (arm-smmu-v3.c) allows an attacker holding a low-privileged local context to subvert the IOMMU's protection mechanism and reach kernel-level access on a vulnerable device. The flaw is a logic error affecting multiple functions of the driver, rated CVSS 7.8 with a local attack vector, low privileges, and no user interaction required. Google ships the fix in the September 2026 Pixel/Android security bulletin; no CISA KEV listing and no public exploit code were identified at the time of analysis.
Improper input validation in multiple locations of the Android kernel allows a locally installed application to escalate privileges on affected Pixel and Android devices, with no additional execution privileges or user interaction required. The flaw is rated 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting a local attacker who already holds low-privileged code execution but can reach high-integrity kernel operations. It is addressed in the September 2026 Android/Pixel security bulletin; at time of analysis there is no CISA KEV listing, no confirmed public exploit code, and no EPSS signal was supplied with the source data.
An out-of-bounds write reachable through a race condition in google_mba_recv_msg() in google_mba_poll.c allows a locally installed low-privilege application on an affected Android device to corrupt kernel memory and escalate to system/kernel privileges. Rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N), the flaw requires no user interaction but does need the attacker to already run code on the device and to win a timing window, which keeps it materially below a remote, unauthenticated severity. No public exploit code has been identified and the issue is not listed in CISA KEV at time of analysis; no EPSS score was supplied in the source data.
Memory corruption in the ARM64 TLB-invalidation path of the Android kernel allows a local attacker holding low privileges to win a race condition and escalate to kernel/root privileges, with no user interaction and no additional execution privileges required. Affected builds are Google Android (CPE cpe:2.3:a:google:android:*:*:*:*:*:*:*:*), specifically ARM64 devices; Google's September 2026 Pixel security bulletin is the vendor reference for the fix. No EPSS score, CISA KEV listing, or public proof-of-concept was present in the supplied intelligence, so active exploitation is unconfirmed and no public exploit code has been identified at time of analysis.
Let me build the JSON. CVE-2026-58724: Android kernel use-after-free due to race condition, local EoP requiring System execution privileges, no UI. CVSS 7.0 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Reported by Google Devices. CPE: google:android. Tags: Privilege Escalation, Google, Race Condition. Reference: Android security bulletin September 2026 Pixel. Note: "System execution privileges needed" — this is Android bulletin phrasing meaning the attacker needs System-level privileges already... Actually in Android bulletins, "System execution privileges needed" means the vulnerability requires the attacker to already have System privileges? Hmm, actually Android bulletin says "This could lead to local escalation of privilege with System execution privileges needed" — meaning the attacker needs System execution privileges? Historically it means exploitation requires the attacker to run code with System privileges already... Actually it means the vulnerability can lead to local escalation of privilege with System execution privileges needed — i.e., it requires System-level privileges to exploit. That means privilege escalation from System to... hmm, in Android, "System" is a UID (system uid 1000). So it escalates to kernel. Actually "with System execution privileges needed" means the attacker must already have System privileges. CVSS PR:L is consistent-ish. Actually PR:L. Hmm but if System privileges needed, PR:H might be more apt. Given CVSS says PR:L, I'll assess PR:L... Hmm. My own assessment: AV:L/AC:H/PR:H? Let me think. The Android phrasing "System execution privileges needed" — needed to exploit — implies significant privileges already (system UID, not just any app). That's PR:H arguably. But CVSS gives PR:L. I'll go with PR:H? Let's be careful — I should ground my assessment in the description. The description says "with System execution privileges needed" — this means the exploit requires system-level privileges. So PR:H is honest. But the vendor's own CVSS says
Let me synthesize. CVE-2026-58710: DecodeFilmGrainParams in film_grain_dec.cc — Android libavc / media codec film grain decoding. Missing bounds check → OOB write → RCE. CVSS 8.8 with AV:N/AC:L/PR:L/UI:N — note PR:L is odd but that's given. CWE-120 (buffer copy without checking size). Reported by Google Devices, references Android Security Bulletin Pixel 2026-09-01. CPE google:android. EUVD affected versions: "Android Android kernel" — weird. Tags: RCE, Buffer Overflow, Google. Missing tag maybe "android". Product name: "Android" — or "Android Film Grain Decoder"? 1-3 words. "Google Android" maybe. Let's use "Android Media Codecs"? Hmm. The vulnerability is in film_grain_dec.cc which is part of libavc (Android's AVC decoder) or a codec2 component. Probably Android's media framework. Product name should be specific: "Android". Let's pick "Google Android" (2 words). Prevalence: Android is ubiquitous. Assessed CVSS vector: Given description "remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation." But CVSS vector says PR:L. Hmm. Media decoding typically happens when processing a media file — remotely delivered via messaging, or via media server. PR:L suggests some level of privilege required — perhaps access to a media-decoding service context, or the requirement to send media to a privileged process. Actually, for Android media codecs, an app can trigger decoding with its own privileges. The vendor assigned PR:L. I should give my own assessment. Given the description says "no additional execution privileges needed" and UI:N, but AV:N with media parsing... Typically media parsing is AV:L or AV:N depending on delivery. Android media codec flaws are usually CVSS AV:N/AC:L/PR:N/UI:R for a crafted file. Here UI:N suggests it's triggered via a network media stream (e.g., RTP, video call) without user opening a file. PR:L — the attacker needs local privileges? Hmm, in Android, media codec processes (media.
A permission bypass in the Android Cellular Modem (baseband) component lets an attacker who is within radio range of the device escalate privileges inside the modem context, exposing confidentiality, integrity and availability of device data with no user interaction. Exploitation requires the attacker to already hold low-level privileges on the modem interface (CVSS PR:L) and to be network-adjacent (AV:A), which in practice points to a rogue or compromised cellular base station rather than an internet-based attacker. The flaw stems from a logic error in permission checking rather than a memory-safety bug, and at time of analysis there is no public exploit code and no CISA KEV listing, though the vendor has published a fix in the September 2026 Pixel security bulletin that should be treated as authoritative.
A race condition in the trusty_dputc() debug output path of generic-arm64-smcall.c in the Android kernel allows an out-of-bounds write that can be leveraged for local privilege escalation. The flaw is only reachable by a process already running with System execution privileges, and exploitation requires winning a timing window (AC:H, PR:L), with no user interaction. Impact is high across confidentiality, integrity and availability because the corrupted memory is kernel/secure-monitor adjacent, but no public exploit code or in-the-wild exploitation is known from the available intelligence.
An out-of-bounds write in Android's IP Multimedia Subsystem (IMS) telephony stack allows an attacker positioned on the cellular signaling path to corrupt memory and achieve code execution inside the privileged process that handles VoLTE/VoWiFi traffic. User interaction on the target is not required, and the September 2026 Pixel bulletin identifies the flaw as remotely triggerable via improperly validated input. No public exploit code or CISA KEV entry was identified at the time of analysis, and no EPSS score was supplied with the source data, so real-world exploitation activity is unconfirmed.
An out-of-bounds write in the NXP NFC hardware abstraction layer (phNxpNciHal_ext_process_nfc_init_rsp in phNxpNciHal_ext.cc) lets a local attacker corrupt memory beyond the intended buffer while the HAL processes an NFC initialization response. Affected are Android devices that ship the NXP NFC HAL, which the Android CPE lists without a version bound; the flaw requires no user interaction and, per Google's bulletin wording, no additional execution privileges, so a typical app-level foothold is enough to attempt escalation. There is no CISA KEV listing and no public exploit code reported in the supplied intelligence, so exploitation is assessed as feasible but not yet observed.
An out-of-bounds write in Av1DecodeFrameTag (vp9hwd_headers.cc) in the Android media decoding stack allows crafted AV1/VP9 media content to corrupt memory and potentially achieve remote code execution in the codec process, which runs with elevated system privileges relative to a normal app. Google's Pixel security bulletin dated 2026-09-01 lists the fix, and no user interaction is required, though the provided CVSS vector (PR:L) implies the attacker must already be able to route content into the decoder path. No EPSS score, CISA KEV entry, or public exploit code was supplied with this record, so active exploitation is unconfirmed.
An out-of-bounds write in Android's audio RTP payload encoder node (AudioRtpPayloadEncoderNode.cpp) lets a remote attacker execute arbitrary code in the media framework process by supplying a crafted audio RTP payload that the node fails to validate. Affected builds are Android/Pixel devices covered by the September 2026 Android Security Bulletin; the vendor description states user interaction is required to trigger the flaw, and an NVD/EUVD record exists alongside the source.android.com advisory. No public exploit code or CISA KEV entry was identified in the supplied intelligence, and no EPSS score was provided at time of analysis.
A heap-based buffer overflow (out-of-bounds write) exists in the Android Cellular Modem component, allowing an attacker within adjacent/proximal radio range to corrupt heap memory and potentially execute code in the modem context without user interaction. The flaw carries a CVSS base score of 8.0 (AV:A/AC:L/PR:L/UI:N) and affects Google Android devices per the Android/Google Devices CPE. No public exploit code or CISA KEV listing was provided at time of analysis, so exploitation status is unconfirmed; the vendor fix is documented in the September 2026 Pixel/Android Security Bulletin.
Local privilege escalation in Google Android's VPU (Video Processing Unit) driver lets an unprivileged app trigger an out-of-bounds write through a confused-deputy path, corrupting kernel memory and gaining root-level code execution on the device. Per the CVSS vector, the attacker must already hold local code execution (PR:L) but needs no user interaction, and the September 2026 Pixel/Android Security Bulletin confirms a vendor fix. No public exploit code or CISA KEV activity has been identified at time of analysis.
An out-of-bounds write in ReadTileInfo of vp9hwd_headers.cc lets a crafted VP9 bitstream corrupt memory inside Android's VP9 hardware-decoder header parser, which Google rates as remote escalation of privilege with no additional execution privileges and no user interaction required. Affected builds are those tracked under the Google Android CPE and addressed by the Android/Pixel security bulletin dated 2026-09-01. There is no CISA KEV listing and no public exploit code identified at time of analysis, so this is currently a patch-window issue rather than a confirmed in-the-wild campaign.
Let me synthesize. CVE-2026-56920: Android HEVC decoder, firmware header parsing (fw_hevc_dec_header.c), s_decode_vui_param out-of-bounds write, CWE-787, CVSS 8.8 AV:N/AC:L/PR:L/UI:N. Note: "remote code execution with no additional execution privileges needed" — but CVSS says PR:L. Hmm, this is typical Android bulletin wording: "This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation." That's media framework / remote. But CVSS says PR:L which contradicts "no additional execution privileges needed". Actually Android media codecs often run in a sandboxed process (mediaserver), so PR:L reflects the sandbox context. There's a conflict worth noting. Product name: Android (Google Android). Or "Android HEVC Decoder"? 1-3 words. "Google Android" or "Android". Let's use "Android Media Framework"? Hmm — the file is fw_hevc_dec_header.c, HEVC decoder header parsing. Probably part of Android's media codec/firmware. I'll say "Android HEVC Decoder" — 3 words. Actually the CPE says google:android. Product name: "Android HEVC Decoder". Hmm, maybe safer: "Google Android". The field says the specific product or service name affected. CPE is google:android, and it's the HEVC decoder in Android firmware for Pixel devices (bulletin is Pixel). I'll go with "Android HEVC Decoder". Summary: Out-of-bounds write in HEVC VUI parameter decoding. Affected: Android devices with affected firmware (Pixel bulletin 2026-09-01). Remote code execution with no user interaction. No KEV, no POC identified. EPSS: not provided. KEV: not stated → assume not in KEV. POC: not provided → "no public exploit identified at time of analysis". Technical context: HEVC/H.265 VUI (Video Usability Information) parameters in SPS/VPS NAL units; s_decode_vui_param in fw_hevc_dec_header.c; firmware-based HEVC decoder in Android; logic error → insufficient bounds validation → OOB write → memory corruption in media codec process. CWE-787.
Let me synthesize. CVE-2026-56882: Cellular Modem (Android Pixel), information disclosure due to logic error, leading to RCE, no additional execution privileges, no UI. CVSS 8.8 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. CWE-200 (Exposure of Sensitive Information). Reported by Google_Devices, Pixel bulletin September 2026. Product name: "Android Cellular Modem" — 1-3 words. Maybe "Android Cellular Modem" (3 words). Or "Pixel Cellular Modem". Let's use "Android Cellular Modem". Prevalence: Android is ubiquitous. But cellular modem specifically... The affected component is the cellular modem firmware in Android/Pixel devices. Prevalence of Android = ubiquitous. Hmm. The CPE is google:android. Modem component. I'd say "ubiquitous" given Android base. But the specific modem component... The CPE says google:android, so I'll go with ubiquitous. Actually maybe "high"? Android is on billions of devices — ubiquitous is defensible. Let me say ubiquitous with basis "core platform component across billions of Android devices". Hmm, but cellular modem is only in phones with cellular. Still ubiquitous. Actually, let's be careful — the CPE is google:android which is the whole OS. Cellular modem affects devices with cellular radios = most Android phones. I'll go with ubiquitous. CVSS vector given: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H — PR:L is odd for a modem, but that's the input. Note the mismatch: description says "no additional execution privileges needed" but vector says PR:L. That's a conflict to note. My assessed vector: Given it's a modem logic error leading to info disclosure → RCE, remote. I'll assess AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H? Hmm. Let me think. Cellular modem attack — typically over-the-air from a rogue base station or via malicious network. AC:H might be reasonable (requires specific modem state / malformed signaling). But CVSS says AC:L. I'll go with AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H — hmm, but "no additional execution privileges needed" suggests PR:N. But
An integer overflow in the Android VPU (video processing unit) driver's size handling leads to an out-of-bounds write in kernel memory, allowing a locally installed application to escalate privileges to kernel/system level on affected Pixel devices. Exploitation requires only local low-privileged access (CVSS:3.1/AV:L/AC:L/PR:L/UI:N) and no user interaction, making it attractive for a malicious or trojanized app. No public exploit code or CISA KEV listing was identified at time of analysis, and the EPSS signal is not provided; the vulnerability is addressed in the September 2026 Android/Pixel security bulletin.
In decodeAmr of ImsMediaAudioPlayer.cpp, there is a possible out-of-bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation.
An out-of-bounds write in Android's IP Multimedia Subsystem (IMS) telephony stack, corrected in the September 2026 Android/Pixel security bulletin, can be turned into remote code execution against affected devices. The published vector (CVSS 8.8, AV:N/AC:L/PR:L/UI:N, C/I/A all High) indicates network-reachable exploitation with no user interaction, though it assumes low-level privileges while the description claims no additional execution privileges are needed. No public exploit code, EPSS score, or CISA KEV entry was provided, so active exploitation is not confirmed at time of analysis.
Local privilege escalation in the Android kernel's fingerprint (gf) driver allows a process with access to the fingerprint device interface to corrupt kernel heap memory and gain root-level code execution. The flaw is a heap-based out-of-bounds write in gf_base_update_finger_base() within gf_base.c, exploitable with a low-privileged local context and no user interaction, consistent with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N). Fixes are delivered through the Android/Pixel Security Bulletin dated 2026-09-01; no public exploit code or CISA KEV listing was identified at time of analysis.
A use-after-free race condition in multiple locations of the Android kernel allows an attacker to corrupt kernel memory and escalate to remote code execution, affecting Android devices covered by the September 2026 Android Security Bulletin. Exploitation requires an attacker to already hold a low-privilege foothold on the device (CVSS PR:L) — typically a malicious or compromised application — and no user interaction is needed once that foothold exists. No public exploit code or CISA KEV listing was identified at time of analysis, so this is currently a patch-now kernel hardening issue rather than a confirmed in-the-wild campaign.
Remote exploitation of the cellular modem stack in Google Android devices allows an attacker who controls the radio path to trigger a heap-based out-of-bounds write and escalate privileges on the handset, without any user interaction. The supplied CVSS 3.1 base score of 8.8 reflects high confidentiality, integrity and availability impact, but its PR:L metric (low privileges required) conflicts with the vendor description stating that no additional execution privileges are needed. No public exploit code, EPSS score, or CISA KEV entry was included in the intelligence feed, so active exploitation is unconfirmed at the time of analysis.
An out-of-bounds write in the Goodix fingerprint trusted-application test handler (gf_ta_test_set_config in gf_ta_test.c) on Android allows a locally installed application holding low privileges to corrupt memory and escalate to kernel-level privileges without any user interaction. The flaw stems from improper validation of caller-supplied input reaching a memory-write path inside the fingerprint TA interface. Google addressed it in the Pixel security bulletin dated 2026-09-01; no public exploit code or CISA KEV entry was identified at time of analysis.
An out-of-bounds write in the Android kernel, caused by a logic error in multiple code locations, allows code execution in the kernel context with high impact to confidentiality, integrity and availability. The flaw is remotely reachable per the CVSS vector (AV:N/AC:L/PR:L/UI:N) and requires no user interaction, though the vector indicates a low-privileged rather than fully unauthenticated attacker. Google published a fix in the Pixel security bulletin dated 2026-09-01; no public exploit code, EPSS score, or CISA KEV listing was provided in the available intelligence, so active exploitation is not confirmed.
An out-of-bounds write in Android's VP9 hardware decoder (Vp9DecodeFrameTag in vp9hwd_headers.cc) lets a crafted VP9 video stream corrupt memory in the codec context, giving an attacker code execution at the decoder's privilege level. Affected devices are those running Android builds that include the vulnerable VP9 hardware decoding path prior to the September 2026 Pixel security bulletin fix. No public exploit code or CISA KEV entry was identified at time of analysis, so exploitation appears to require a motivated actor with a delivery path for malicious media.
An out-of-bounds write in Google's Android Cellular Modem component allows code execution in the baseband when a crafted message is delivered to the modem, with no user interaction required. Google Pixel devices running Android builds prior to the September 2026 patch level are affected, per the Pixel security bulletin. Rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N, high confidentiality, integrity and availability impact); no public exploit code or CISA KEV entry was identified at time of analysis, so the immediate risk is to targeted radio-layer attacks rather than mass exploitation.
Let me parse the data. CVE-2026-19407: Bucket Squatting in Google Cloud Gemini Enterprise Agent Platform SDK for Python versions prior to 1.166.1. Allows RCE and tenant-project token theft. CVSS 7.7, CVSS 4.0 vector: AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L. CWE-330 (Use of Insufficiently Random Entropy — actually CWE-330 is "Use of Insufficiently Random Values"). Bucket squatting: attacker registers a cloud storage bucket name that the SDK attempts to use (predictable/guessable name), and the SDK downloads code/artifacts from that bucket, leading to RCE. Related to insufficient randomness in bucket naming. EPSS: not provided. KEV: not provided (no). POC: not provided. Note discrepancy: Description says versions prior to 1.166.1; EUVD says "1.16.0 <1.165.1". That's a data conflict — flag in confidence_notes. Patch: Available from vendor — release notes from March 31, 2026. Affected products: Google Cloud Gemini Enterprise Agent Platform SDK for Python, versions prior to 1.166.1 (fix version 1.166.1). Prevalence: This is a specific SDK — medium/low. It's a Google Cloud SDK for an agent platform — niche enterprise. I'd say "low". Hmm. Gemini Enterprise Agent Platform SDK for Python — AI agent dev kit. Deployment footprint probably low-medium. I'll say "low" with basis "specialized Google Cloud AI agent SDK, limited deployment footprint". Actually maybe "medium" since Google Cloud + Gemini is popular. But the specific SDK for agent platform — low. I'll go with "low". Assessed CVSS vector: AT:P means attack requirements are present (attacker must pre-register the bucket name — that's an attack requirement). PR:N, UI:P (victim must run the SDK / user interaction). So my 3.1 vector: AV:N/AC:H/PR:N/UI:R/S:C? Hmm. Scope — subsequent system impact SC:L/SI:L/SA:L, so scope changed in 3.1 terms. Let's do: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. Hmm, but scope change with C:H/I:H/A:H might be too high. Actually the vulnerable system impact is H/H/H.
Privilege escalation in Mozilla Firefox for Android allows an attacker who can get a user to open a crafted web page to gain privileges beyond those normally granted to web content, with high impact to confidentiality, integrity, and availability. Mozilla fixed the flaw in Firefox 156; no public exploit code and no active exploitation have been identified, and CISA's SSVC assessment rates exploitation as 'none' with automatable 'no'. The 8.8 CVSS score is driven entirely by a network attack vector plus required user interaction (UI:R), so real-world risk depends on convincing a target to browse attacker-controlled content rather than on mass scanning.
Gallery - Private Photo Vault 1.0.41 (Android, by Brain Trust) exposes an unauthenticated HTTP server on TCP port 8080 that is reachable by any device on the same local network, serving full directory listings and file contents from Android external storage - the very media the app is marketed to protect. Any network-adjacent attacker can trivially enumerate and exfiltrate photos, videos, and other files without credentials or user interaction. No public exploit code is required beyond a standard web browser or curl; Fluid Attacks' advisory confirms a proof-of-concept exists, but no CISA KEV listing has been identified at time of analysis.
Race condition in Microsoft Edge (Chromium-based) builds prior to 152.0.4191.66 lets an attacker who already holds low-privileged code execution inside the browser win a narrow timing window and elevate to full privileges outside the Chromium sandbox. The flaw is CWE-362 (concurrent execution on a shared resource with improper synchronization) and carries a CVSS 3.1 score of 7.8 with a Scope:Changed rating, indicating a successful exploit crosses a security boundary rather than simply corrupting the renderer. Exploitation is local, timing-dependent (AC:H) and non-automatable per CISA SSVC; no public exploit code or CISA KEV entry is associated with this CVE at time of analysis, and a vendor patch is available.
Ekia File Manager 1.2.7 for Android ships an exported ContentProvider (com.ekia.filecontrolmanager.OpenFileProvider) that declares no android:permission, readPermission, or writePermission, so any other app on the same device can invoke it. The provider maps the caller-supplied URI path straight to a filesystem path and passes it to new File(...), letting a malicious local app make the File Manager process read, create, overwrite, or delete every file that process can reach. The issue is not in CISA KEV, EPSS is only 0.11% (2nd percentile), and no public exploit tooling was identified in the supplied data, so real-world priority depends almost entirely on whether untrusted apps can be installed on the target device.
Improper input validation in Zscaler Client Connector for Android and ChromeOS (builds prior to 4.2.0.152) lets an attacker with elevated local privileges on the endpoint feed malformed input to the connector and bypass Zscaler's traffic inspection and access controls, with a CVSS 8.1 (AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L) rating that reflects total loss of the security control's integrity. The flaw is not remotely exploitable and requires high privileges (root or equivalent device-admin context) on the affected Android or ChromeOS device, and there is no public exploit identified at time of analysis. EPSS is 0.12% (2nd percentile) and CISA SSVC records exploitation 'none', automatable 'no' with total technical impact — a low-likelihood, patch-promptly issue rather than an emergency.
Out-of-bounds read and write in the Linux kernel's Chrome EC sensorhub driver exposes Chromebook-class systems to kernel heap corruption via an unvalidated 8-bit sensor number in EC FIFO events. The cros_ec_sensor_ring_process_event() function indexes batch_state[] using the sensor_num field from embedded-controller events without checking it against the allocated array size, allowing any event carrying sensor_num >= sensorhub->sensor_num to access arbitrary adjacent kernel heap memory. No public exploit or CISA KEV listing exists; EPSS is 0.20%, but the C:H/I:H/A:H CIA impact reflects the potential for kernel memory corruption on affected Chrome EC hardware.
Use-after-free in Microsoft Edge (Chromium-based) enables an authenticated network attacker to achieve remote code execution with scope change across all supported platforms including Windows, Linux, macOS, Android, and iOS. The vulnerability carries a CVSS 8.5 with high complexity and scope change (S:C), indicating that successful exploitation escapes the browser's sandboxing boundary and affects the underlying host. No public exploit or CISA KEV listing is present at time of analysis, though patch-available status from Microsoft confirms vendor acknowledgment.
Server-Side Request Forgery in Google Cloud Gemini Enterprise Agent Platform App Builder (all versions prior to the 2026-06-01 deployment date) enables unauthenticated remote attackers to exfiltrate the Compute Engine default service account access token by forcing the application to issue requests to the GCP instance metadata service. The stolen OAuth 2.0 bearer token carries the IAM permissions of the default service account, potentially enabling lateral movement across GCP project resources. Vendor-released patch was deployed on 1 June 2026, but existing app deployments require a manual redeployment to receive the fix - creating remediation lag risk for unmanaged deployments.
Arbitrary code execution in Google Cloud's Gemini CLI (npm @google/gemini-cli < 0.39.1) and the run-gemini-cli GitHub Action (< 0.1.22) lets an unprivileged attacker run code on the host by planting untrusted local .env / .gemini configuration files that override GEMINI_CLI_HOME. In headless (CI) mode, previous versions auto-trusted workspace folders and processed their config/environment variables, so a malicious pull request or issue processed by an automated Gemini workflow could trigger RCE; a related --yolo tool-allowlist bypass compounds the risk. Patched by vendor; no public exploit identified at time of analysis and it is not in CISA KEV.
Unencrypted UDP video transmission in the C6 Ear Camera and its companion EarVision Android application (version 1.3.1 / firmware 1.3.1_Code 132) exposes live ear-canal video streams to passive eavesdropping by any attacker within local wireless range. The camera broadcasts JPEG and WEBP frames over plaintext UDP with no transport-layer security, and the Android application's manifest explicitly permits cleartext traffic, removing any client-side enforcement barrier. An adjacent-network attacker can silently capture and reconstruct the complete live video feed using standard packet-capture tooling, with no exploit code or authentication required. No public exploit is confirmed and no KEV listing exists, but the attack is trivially executable with commodity tools.
Remote code execution in Google Cloud Agent Development Kit (ADK) for Python versions 2.0.0 through 2.6.0 allows an unauthenticated remote attacker to run arbitrary code on the host by submitting a crafted test session replay to the 'adk web' developer interface when the pytest package is present. The flaw stems from an incomplete input-restriction check (CWE-184) that lets malicious replay content reach code execution. No public exploit has been identified at time of analysis, but the vendor rates it CVSS 10.0 and shipped a fix in v2.7.0.
Heap-based buffer overflow in Google Chrome's WebRTC component (all versions prior to 153.0.8010.36) enables a remote unauthenticated attacker to potentially execute arbitrary code within the Chrome renderer sandbox by luring a target to a crafted HTML page. The vulnerability is classified CWE-122 and carries a CVSS base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); however, Chromium's own internal severity rating is 'Low,' which is notably discordant and implies that exploitation is constrained to within-sandbox code execution rather than full OS compromise. No public exploit code and no CISA KEV listing have been identified at the time of analysis.
Incorrect authorization in the Extensions component of Google Chrome before 153.0.8010.36 allows a remote attacker to bypass system access restrictions and reach a privileged internal page by luring a victim to a crafted HTML page. Google credits its own team with discovery, and a fixed build is available; no public exploit has been identified at time of analysis, and Chromium rated the underlying issue only Low severity despite the 9.8 NVD score.
Race-condition-triggered code execution in Google Chrome's V8 JavaScript engine (all versions prior to 153.0.8010.36) allows a remote unauthenticated attacker to execute arbitrary code inside the Chrome renderer sandbox by serving a crafted HTML page to a victim. Exploitation is constrained to the Chrome sandbox process rather than the underlying OS, which aligns with Chromium's own internal severity rating of 'Low' despite the CVSS base score of 7.5. No public exploit code or CISA KEV listing is present at time of analysis; the high attack complexity metric reflects the timing-sensitive nature of race-condition exploitation.
Improper certificate validation in Chrome's Federated Credential Management (FedCM) component — fixed in Chrome 153.0.8010.36 — lets a remote attacker who controls crafted network traffic, combined with social engineering of the victim, bypass web origin policy and expose cross-origin identity data. The flaw is a confidentiality-only issue (no integrity or availability impact) and Chrome rates it security severity Low, despite a 7.5 CVSS base score; EPSS is only 0.15% (4th percentile), it is not in CISA KEV, and no public exploit code has been identified at time of analysis. Vendor-released patch: 153.0.8010.36.
Memory corruption in V8, Chrome's JavaScript engine, allows an attacker who can get a user to install a crafted Chrome extension to execute arbitrary code confined within the Chrome sandbox, affecting all Chrome versions prior to 153.0.8010.36. Despite the CVSS 8.8 base score, Chromium's own security team rates this 'Low' severity, reflecting that exploitation is bounded by Chrome's sandbox and does not constitute a full OS-level compromise without a separate sandbox escape primitive. No public exploit code or active exploitation has been identified at time of analysis. Vendor-released patch is available.
Sandbox escape via incorrect authorization in the Chrome Updater component on Windows allows a local attacker to execute arbitrary code outside the browser's sandbox using a crafted local program. Affected versions are all Google Chrome releases prior to 153.0.8010.36 on Windows. The Chromium team rates internal severity as 'Low' - notably lower than the CVSS 8.1 score - suggesting that while the impact is high if exploited, real-world attack complexity limits practical risk. No public exploit or active exploitation has been identified at time of analysis.
Use-after-free in Google Chrome's DevTools component (versions prior to 153.0.8010.36) enables arbitrary code execution within the renderer sandbox when a victim is socially engineered into visiting a crafted HTML page. The CVSS score of 8.8 reflects full C/I/A impact, but Chromium's own internal severity classification of 'Low' signals that exploitation is sandboxed - OS-level compromise requires an additional chained sandbox escape. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Remote code execution in Google Chrome's DevTools component before 153.0.8010.36 stems from a use-after-free (CWE-416) that, per the advisory, allows a crafted HTML page to execute arbitrary code outside the browser sandbox. All desktop Chrome builds prior to the fixed stable release are affected; the flaw was reported internally by the Chrome team, is fixed in the stable channel, and has no public exploit identified at time of analysis. Notably, the assigned CVSS is 9.6 (Critical) while Chromium itself rated the security severity only 'Low', a significant conflict discussed below.
We need answer JSON only. Need synthesize. Need be careful: The description says SSRF in Mobile in Google Chrome prior to 153.0.8010.36, social engineering, crafted HTML page, Chromium severity Low. CVSS 9.8 contradictory: SSRF with social engineering likely UI, low severity, but given CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Need assess. We need follow instructions. Let's inspect input. CVE-2026-87595. Description: Server-side request forgery in Mobile in Google Chrome prior to 153.0.8010.36 allowed a remote attacker leveraging social engineering to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Low) CVSS Score 9.8 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. CWE-918. Multi-source: EPSS 0.18% percentile 7%. Patch available from vendor. Reported by Chrome. CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*:* (no version bounds in CPE string). Tags: Google, SSRF. ENVD affected versions ["Chrome 153.0.8010.36 <153.0.8010.36"] weird: probably means versions before 153.0.8010.36. References. Need output fields all strings except data_quality_flags is array? User says Return JSON object, data_quality_flags JSON array. But earlier "Every field below MUST be a plain text string — NOT an array, NOT an object" includes data_quality_flags? It says every field below must be plain text string, but data_quality_flags description says JSON array. Conflict. Need follow field description likely array. In final JSON, data_quality_flags can be array, but "Every field below MUST be a plain text string" maybe says all fields must be strings; but data_quality_flags is exception? They explicitly say JSON array. We should output array for data_quality_flags. Need ensure no markdown. Need produce product_name: "Google Chrome" (affected product). Maybe "Chrome" but product_name should specific product. "Google Chrome" okay. Summary: Must not copy description. Must start with impact verb and product. E.g. "Server-side request forgery in Google Chrom
Sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The flaw resides in the Storage component's incorrect reference resolution (CWE-706), making this a second-stage exploit that chains with a separate renderer compromise to achieve full sandbox breakout. No public exploit has been identified at time of analysis, and the fix is available in the stable channel release 153.0.8010.36.
Sandbox-escaping remote code execution in Google Chrome's WebPackaging component affects all desktop versions prior to 153.0.8010.36. A use-after-free (CWE-416) reachable from a crafted HTML page can let a remote attacker potentially execute arbitrary code outside the renderer sandbox with no authentication, requiring only that the victim visit a malicious page. No public exploit has been identified at time of analysis; Chromium's own internal triage rated the security severity 'Low', which sits in notable tension with the 9.6 CVSS assigned to the record.
Remote code execution in Google Chrome on iOS before 153.0.8010.36 stems from a use-after-free in the Sharing component (CWE-416), letting a remote attacker who lures a victim to crafted network content execute arbitrary code outside the browser sandbox. Google has shipped a patched Chrome build; no public exploit is identified at time of analysis, and Google/Chromium rated the underlying bug 'Medium' severity even though the assigned CVSS base score is 9.6.
Remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the Passwords component that, when triggered via crafted UI interaction and social engineering, can let a remote attacker escape the renderer sandbox and run arbitrary code. All Chrome desktop builds before the 153.0.8010.36 stable release are affected. No public exploit identified at time of analysis, and no EPSS or KEV data was provided; note that Google's Chromium team rated the underlying bug only 'Medium' severity, which sits in tension with the supplied CVSS 9.6.
Sandbox-escaping remote code execution in Google Chrome's Aura windowing layer affects all desktop builds prior to 153.0.8010.36. A remote attacker who lures a victim to a crafted HTML page can trigger a use-after-free (CWE-416) and potentially execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the fix ships in the stable-channel desktop update.
Out-of-bounds write in the Media component of Google Chrome before 153.0.8010.36 allows a remote attacker to potentially execute arbitrary code outside the browser's renderer sandbox by luring a victim to a crafted HTML page. The scope-changing memory-corruption bug carries a CVSS of 9.6 despite Chromium's own 'Medium' severity rating, and a vendor patch is available. There is no public exploit identified at time of analysis.
Remote code execution in Google Chrome on Windows prior to 153.0.8010.36 arises from a type-confusion bug in the browser's Rust code, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Google shipped a fixed build via the Stable channel, and the flaw was reported internally by the Chrome team. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though sandbox-escape memory-corruption bugs in Chrome are historically high-value exploitation targets.
Sandbox-escape remote code execution affects Google Chrome on macOS prior to 153.0.8010.36, where an improper quantity-validation flaw (CWE-1284) in Tint, the WebGPU/WGSL shader compiler in Chromium's Dawn graphics stack, lets a crafted HTML page break out of the renderer sandbox. A remote attacker who lures a victim to a malicious web page can potentially execute arbitrary code with the privileges of the browser process on the host. Google reports a fix is shipped; there is no public exploit identified at time of analysis, and Chromium internally rated the issue Medium severity despite the high provided CVSS.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from a numeric truncation error in the Media component, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. The vendor patch is available via the September 2026 stable-channel update; no public exploit is identified at time of analysis. Note a signal conflict: Chromium rated this 'Medium' severity while the supplied CVSS base score is 9.6 Critical.
Remote code execution in Google Chrome for macOS prior to 153.0.8010.36 stems from a use-after-free in the Extensions component, letting a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw carries a CVSS 9.6 (scope-changed, network vector with user interaction), though Chromium's own security team rated it 'Medium'. No public exploit has been identified at time of analysis, and the fix is available in the stable channel.
FileAPI improper input validation in Google Chrome prior to 153.0.8010.36 enables an attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code on the underlying host system. The flaw, tracked in Chromium issue 532957878, was addressed in the September 2026 stable channel release. With an EPSS of 0.30% and no confirmed active exploitation, this functions as a second-stage sandbox-escape primitive rather than a standalone remote attack.
Use-after-free in Chrome's V8 JavaScript engine allows a remote attacker who can socially engineer a victim into installing a crafted Chrome extension to execute arbitrary code within the browser's renderer sandbox, affecting all Chrome versions prior to 153.0.8010.36. The vulnerability is constrained to in-sandbox execution - it does not constitute a standalone sandbox escape - which aligns with the S:U CVSS metric and Chromium's internal 'Medium' severity rating despite the 8.8 base score. No public exploit code or active exploitation has been identified at time of analysis, and Google has shipped a patch in the stable channel.
Missing authorization in the Extensions subsystem of Google Chrome prior to 153.0.8010.36 enables a remote attacker to obtain sensitive browser information by delivering a crafted Chrome extension that bypasses access control checks. The vulnerability is classified CWE-862 (Missing Authorization), meaning the runtime fails to enforce proper permission boundaries between extension capabilities and protected browser data. No public exploit code or active exploitation has been identified at time of analysis; Chromium's own internal severity rating of 'Medium' reflects practical exploitation barriers not fully captured by the NVD CVSS 7.5 High rating.
Use-after-free in Google Chrome's DevTools component prior to 153.0.8010.36 enables a local attacker to escape the browser sandbox and execute arbitrary code at the host OS level via a crafted local program. Chromium's own severity rating is 'Medium', reflecting the local access prerequisite, while the CVSS 8.1 score captures the high-impact sandbox-escape outcome once exploitation succeeds. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the EPSS score (0.12%, 2nd percentile) confirms low observed exploitation probability.
Sandbox escape via incorrect authorization in the Views component of Google Chrome on Windows (versions prior to 153.0.8010.36) enables arbitrary code execution outside the browser sandbox. Exploitation requires an attacker to first compromise the renderer process and then leverage social engineering to induce user interaction with a crafted HTML page. No public exploit or KEV listing exists at time of analysis; Chromium's own severity rating of Medium contrasts with the CVSS 8.3 score, reflecting the difficult two-stage attack chain.
Sandbox escape via improper initialization (CWE-665) in Google Chrome's Views UI framework on Windows, prior to version 153.0.8010.36, can lead to arbitrary code execution outside the browser sandbox. The attack is chained: an adversary must first compromise the renderer process through a separate vulnerability, then leverage social engineering to trigger the Views initialization flaw, elevating from renderer-level code execution to full host OS access. No public exploit code has been identified and EPSS sits at 0.28% (20th percentile), consistent with the multi-step prerequisite bar, though the C:H/I:H/A:H impact profile warrants prompt patching.
Sandbox-escaping remote code execution in Google Chrome's Browser process on Windows (all versions prior to 153.0.8010.36) stems from a use-after-free flaw. A remote attacker who lures a victim into opening a crafted HTML page can corrupt reclaimed heap memory in the privileged browser process and execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the vendor has shipped a fixed stable build.
Uncontrolled search path element in Chrome's Windows CredentialProvider component (CWE-427) enables a local attacker to execute arbitrary code outside the browser sandbox on Windows systems running Chrome prior to 153.0.8010.36. The flaw is a DLL or executable search-order hijacking issue: Chrome's CredentialProvider resolves a dependency by searching an attacker-controllable path, allowing a malicious local program to intercept and execute in place of a legitimate component, with the result escaping Chrome's sandbox entirely. No public exploit code or CISA KEV listing has been identified at time of analysis.
Site isolation bypass in Google Chrome's FileSystem component allows a remote attacker who has already achieved renderer process compromise to escape cross-origin boundaries via a crafted PDF file. Affected versions are all Chrome releases prior to 153.0.8010.36 on desktop platforms. The vulnerability (CWE-863, Incorrect Authorization) enables the attacker to read or modify data belonging to other origins, undermining Chrome's core sandboxing guarantee. No public exploit or active exploitation (CISA KEV) has been identified; EPSS is 0.16%, consistent with the SSVC 'Exploitation: none' rating.
Incorrect authorization in Google Chrome's Permissions subsystem before version 153.0.8010.36 enables remote attackers to exfiltrate sensitive browser information through a crafted Chrome extension that requires social engineering to install. The flaw (CWE-863) causes Chrome's permission brokering layer to incorrectly authorize an extension's access to protected browser data, resulting in high-confidence confidentiality impact with no integrity or availability consequence. No public exploit has been identified and EPSS sits at 0.18%, consistent with the social-engineering prerequisite that constrains mass opportunistic exploitation.
Site isolation bypass in Google Chrome prior to 153.0.8010.36 allows a remote attacker who has already compromised the renderer process to escape Chrome's cross-site isolation boundary via a crafted file combined with social engineering. The flaw is rooted in incorrect authorization (CWE-863) within the SiteIsolation component, meaning the browser fails to properly enforce origin-based access controls once the renderer is under attacker control. Vendor-released patch 153.0.8010.36 is available; no public exploit has been identified and EPSS sits at 0.16% (6th percentile), consistent with the Chromium team's 'Medium' severity rating despite the CVSS 8.8 base score.
Sandbox-escape remote code execution in Google Chrome for Android before 153.0.8010.36 arises from an integer overflow in the GPU process, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. Fixed in the same 153.0.8010.36 Stable Channel release that addressed several other GPU/media memory-safety bugs; no public exploit identified at time of analysis. Note the rating tension: the input CVSS is 9.6 (Critical) while Google's own Chromium severity is only Medium.
Missing authorization in the WebView component of Google Chrome on Android before 153.0.8010.36 lets a remote attacker who first tricks a user via social engineering bypass system access restrictions through crafted network traffic. The flaw is tracked as CWE-862 (missing authorization) and was reported by Google's Chrome team; a vendor patch is available. Chromium rates the security severity as Medium, EPSS is low (0.17%), and no public exploit or CISA KEV listing has been identified.
Use-after-free in Chrome's ANGLE graphics layer on Windows enables sandbox escape and arbitrary code execution when a renderer process has already been compromised. Affected versions are all Chrome releases prior to 153.0.8010.36 on Windows; exploitation requires an attacker to first compromise the renderer and then deliver a crafted HTML page triggering the ANGLE memory corruption. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.28% (20th percentile) reflects low observed exploitation probability.
Memory corruption via use-after-free in Microsoft Edge (Chromium-based) lets a remote attacker run arbitrary code at elevated privilege in the browser and ultimately on the host, provided the victim opens attacker-controlled content. Microsoft scores it 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), so no credentials are needed but a single user visit is — a classic one-click browser exploitation pattern rather than a zero-click worm. The intelligence feed contains no EPSS score, no CISA KEV listing, and no public exploit reference, so at time of analysis this is a high-severity but not yet observed-exploited issue.
We need to produce JSON with fields. Need to be careful about "opole" in risk_assessment only, once, lowercase, natural prose, not a factual claim about who is affected. Something like "even a mid-sized municipal IT team in opole would likely..." Hmm it's a hypothetical illustrative reference, must not be presented as factual claim about who is affected. I'll phrase: "for instance, even a mid-sized IT team in opole..." That's hypothetical illustration. Should be fine. Keep once. Data: CVE-2026-69486, Microsoft Edge Chromium-based heap buffer overflow, CVSS 8.8 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-122. Patch available from vendor. Affected versions EUVD: Microsoft Edge (Chromium-based) 1.0.0.0 <153.0.4234.32. Reference MSRC. Tags include "Google" which is likely a mislabeled tag — Edge is Chromium-based, but "Google" tag on a Microsoft Edge CVE? Could be mislabeled. Hmm. The tag "Google" might refer to Google Chrome/Chromium? The CVE is Microsoft Edge. Flag mislabeled_tag "Google" with suggested "microsoft" or maybe "chromium"? Actually tags include "Microsoft" already. The "Google" tag is probably wrong vendor for a Microsoft Edge vulnerability — although Chromium is Google's project. Is it clearly wrong? Edge is Chromium-based, so a Google tag is arguably not strictly wrong but for vendor tagging it's mislabeled — the affected product is Microsoft Edge. Confidence medium? The instruction says only emit flag when clearly wrong and verifiable. Hmm, "Google" tag on Microsoft Edge CVE — Edge is built on Chromium (Google's open source project). But the vendor is Microsoft. I'd say medium confidence mislabeled_tag. Alternatively don't flag. Given the editorial note mentions nothing about tags. I think emitting one flag with medium confidence is acceptable: target "Google", suggested null or "microsoft"? Suggested is correct/canonical slug if known: "microsoft" already exists in tags. Maybe suggested null since "Google" isn't the right vendor and Microsoft is alread
We need produce JSON only. Need analyze. We have CVE data. Need synthesize all fields. Let's parse carefully. CVE-2026-91749: Use after free in Workers in Google Chrome prior to 153.0.8010.47 allowed remote attacker potentially execute arbitrary code outside sandbox via crafted HTML page. Critical. CVSS 9.6 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. CWE-416. Patch available vendor. Tags: RCE, Denial Of Service, Google, Use After Free, Memory Corruption. SSVC exploitation none, automatable no, technical impact total. EUVD affected versions weird "Chrome 153.0.8010.47 <153.0.8010.47" probably should be < 153.0.8010.47? Maybe formatting error. References to Chrome releases and issue. Need field product_name 1-3 words: "Google Chrome". Summary: original synthesis. Mention use after free in Workers in Google Chrome before 153.0.8010.47; remote attacker via crafted HTML page could execute arbitrary code outside sandbox. Patch available. No active exploitation per SSVC/KEV? Input lacks KEV status but SSVC says exploitation none. POC? not provided. Need not say if KEV no. EPSS absent. Mention no public exploit identified? Since POC not provided but SSVC no exploitation. We can state "No active exploitation reported in available data; SSVC lists exploitation none." Do not copy description. Start with specific impact verb: "Remote code execution outside the sandbox in Google Chrome before 153.0.8010.47..." Is that ok. Mention UAF in Workers triggered by crafted HTML page. Critical severity. Could mention patch available. No KEV. EPSS not provided. Need not include. Technical_context: underlying technology: Google Chrome Workers (Web Workers/Service Workers?) Need be specific: Workers likely the browser's worker subsystem / threading implementation. UAF in Workers. CWE-416 use after free. CPE data? Input doesn't include CPE strings explicitly. EUVD affected versions. We can reference affected product version. Explain root cause: memory management error where object freed then re
A time-of-check-to-time-of-use race condition in the Extensions component of Google Chrome on macOS allows an attacker to break out of the renderer sandbox and execute arbitrary code in the browser process context. The barrier to entry is meaningful: the attacker must already have compromised the renderer process through a separate bug and then use social engineering to persuade the victim into a specific UI interaction that widens the race window. Affected builds are Chrome for macOS prior to 153.0.8010.47, and Google rates the issue High severity; no public exploit code or CISA KEV entry was identified at time of analysis.
Sandbox escape in Google Chrome prior to 153.0.8010.47 allows a remote attacker who has already compromised the browser's renderer process to execute arbitrary code outside the sandbox via a race condition (TOCTOU) triggered by a crafted HTML page; the user must visit that page for the flaw to be reachable. Google rates the issue Chromium security severity High and a vendor patch is available from the 153.0.8010.47 stable channel release. There is no public exploit code and no CISA KEV listing at time of analysis, and the high attack complexity combined with a required renderer-compromise precondition keeps realistic risk below the raw 8.3 CVSS score.
Type confusion in Chrome's CacheStorage implementation in builds prior to 153.0.8010.47 lets a remote, unauthenticated attacker execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page. The bug is rated High by Chromium and 8.8 by NVD (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), but it is a renderer-level compromise rather than a sandbox escape, so host impact requires chaining a second vulnerability. No CISA KEV listing and no public exploit code were identified at time of analysis, and no EPSS score was supplied in the input data.
Use-after-free in Chrome's DOM implementation allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page in Chrome versions prior to 153.0.8010.47. The flaw carries a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and is rated High by Chromium security severity; a vendor patch is available and no public exploit code or CISA KEV entry was identified at time of analysis.
Google Chrome versions earlier than 153.0.8010.47 contain an incorrect authorization flaw (CWE-863) in the WebUI subsystem that lets an attacker who already controls a compromised renderer process break out of the browser sandbox and run arbitrary code on the host via a crafted HTML page. Exploitation is a two-stage proposition: the attacker must first obtain renderer code execution, then chain this flaw to escape the sandbox, and the victim must load the malicious page. Google rates the Chromium security severity as High and has shipped a fix in Chrome 153.0.8010.47; no public exploit code or CISA KEV entry was identified in the available intelligence at time of analysis.
Incorrect authorization in Chrome's Core component on Windows (versions prior to 153.0.8010.47) lets a local attacker who can run a program on the machine break out of the browser sandbox and execute arbitrary code at the user's privilege level outside it. The flaw is rated High by the Chromium security team and carries CVSS 7.4 (AV:L/AC:H/PR:N/UI:N, C/I/A all High), reflecting a local-only but complete confidentiality, integrity and availability impact once the sandbox boundary is crossed. No public exploit code or CISA KEV listing was provided in the input, and Google has released a fixed stable-channel build, so this is best treated as a high-value chaining primitive rather than a currently mass-exploited issue.
Improper state validation in the Skia graphics library, as shipped in Google Chrome prior to 153.0.8010.47, lets an attacker who already controls a compromised renderer process read memory outside the browser sandbox by serving a crafted HTML page. Exploitation requires the victim to load the malicious page (UI:R) and depends on chaining with a separate renderer compromise, which is why the vector carries AC:H despite the network attack path. Vendor status is "Patch available"; no public exploit code and no CISA KEV listing were present in the supplied intelligence, so the flaw should be treated as a sandbox-escape primitive rather than an observed, widely exploited issue.
Remote code execution inside the renderer sandbox affects Google Chrome desktop builds prior to 153.0.8010.47, caused by a type confusion flaw in the browser's compositing pipeline (CWE-843) that is reachable from a crafted HTML page. An attacker needs only to convince a user to load the page: the CVSS 3.1 vector is 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), so no credentials or privileges are required, but user interaction is mandatory. Google rates the issue Chromium security severity High and has shipped a fixed stable-channel build; no public exploit code or CISA KEV listing appears in the supplied intelligence, and no EPSS score was provided, so the current exploitation picture is best described as patch-now-but-not-known-exploited.
Integer overflow in V8 in Google Chrome prior to 153.0.8010.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Let me synthesize. CVE-2026-91727: Incorrect reference resolution in Extensions in Chrome on Mac prior to 153.0.8010.47. Local attacker who compromised renderer process could execute arbitrary code outside sandbox via a local program. CWE-706 (Use of Incorrectly-Resolved Name or Reference). CVSS 8.1 AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Product: Google Chrome (macOS). Product name 1-3 words: "Google Chrome". Prevalence: ubiquitous. Now fields. Summary: must not copy description; start with impact verb and product. E.g. "Sandbox escape in Google Chrome on macOS (prior to 153.0.8010.47) lets an attacker who has already compromised the renderer process escalate to code execution outside the browser sandbox..." Technical context: CWE-706 incorrect reference resolution in Extensions — extension API resolves a reference (name/path/identifier) incorrectly, allowing a local program to be loaded/executed outside sandbox. macOS-specific. Renderer compromise prerequisite. Risk assessment: CVSS 8.1 with AV:L AC:H PR:N UI:N S:C. EPSS not provided, KEV not provided. Patch available. No POC known. Attack requires renderer compromise (two-stage). S:C indicates sandbox escape crossing security scope. Not KEV → no public exploit identified at time of analysis. Note missing EPSS/KEV data explicitly. Affected products: Google Chrome on macOS versions prior to 153.0.8010.47; EUVD lists "Chrome 153.0.8010.47 <153.0.8010.47" which is malformed/likely means before 153.0.8010.47. Reference: chromereleases blog, chromium issue 516893912. Remediation: upgrade to 153.0.8010.47 or later. Chrome auto-update. macOS-specific. Compensating controls: restrict extension installs via enterprise policy, disable extensions, etc. Trade-offs. Exploit scenario: attacker chains a renderer RCE (e.g. via malicious web content) then exploits the extension reference resolution flaw to break out of sandbox and run native code on macOS host. Exploitation conditions: requires (1) macOS platform, (2) att
Google Chrome builds prior to 153.0.8010.47 carry a use-after-free in the browser's Input component that allows an attacker who already controls a compromised renderer process to escape the Chrome sandbox and run arbitrary code with the browser's privileges. Exploitation is not remote-standalone: it requires a chained renderer compromise plus a victim who opens a crafted HTML page, which is why the flaw is scored High (8.3) rather than Critical despite total technical impact. Google has shipped a fixed stable-channel build; no public exploit code has been identified and the issue is not listed in CISA KEV at time of analysis.
A use-after-free in Google Chrome's Internals component allows a remote attacker to potentially execute arbitrary code outside the browser sandbox when a victim opens a crafted HTML page, affecting all Chrome builds prior to 153.0.8010.47 on desktop. Exploitation requires user interaction (visiting the page) but no authentication or elevated privileges, and Google rates the Chromium security severity as Critical. Vendor-released patch: 153.0.8010.47. There is no public exploit code identified at time of analysis and no confirmed actively exploited (CISA KEV) status, though the SSVC framework assigns total technical impact.
Google Chrome on macOS versions prior to 153.0.8010.47 contain a race condition (TOCTOU) in the Extensions subsystem that lets an attacker who has already compromised the browser's renderer process break out of the sandbox and execute arbitrary code on the host, triggered when a victim loads a crafted HTML page. Google rated the issue High severity and Chromium's own severity assessment drove the 8.3 CVSS base score with a Scope change (S:C), reflecting that code execution crosses the renderer/sandbox boundary rather than staying contained. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, but a vendor patch is available and should be applied promptly because sandbox escapes are the high-value second stage of any Chrome exploit chain.
Type confusion in Google Chrome's ServiceWorker implementation before version 153.0.8010.47 allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox by getting a user to open a crafted HTML page. The flaw carries a CVSS base score of 8.8 (AV:N/AC:L/PR:N/UI:R), the classic memory-corruption profile for Chrome renderer bugs, and Google rated it High in its Chromium severity scheme. A vendor patch shipped in the 153.0.8010.47 stable release, and there is no public exploit code identified and no CISA KEV entry at time of analysis, so this is a prioritise-and-patch issue rather than a confirmed active campaign.
Remote code execution inside the Apache Airflow scheduler is possible through the Apache Kafka provider (apache-airflow-providers-apache-kafka) 1.15.0 to before 2.0.0, which resolves dotted-path strings from a Kafka connection's extra field into Python callables via import_string with no allowlist and hands them to the confluent-kafka client. An authenticated user whose only privilege is editing Airflow connections can thereby execute arbitrary code in the control plane when the non-default Kafka event producer (dag_run_events_enabled or task_instance_events_enabled) is switched on, exceeding the Airflow security model that limits connection-configuration users to code execution on workers. No public exploit code or CISA KEV listing was identified at time of analysis; deployments using Google Managed Kafka are not affected because that code path overwrites any user-supplied oauth_cb, while plain brokers and Amazon MSK are exposed.
Local privilege escalation in the Android kernel's Arm SMMUv3 driver (arm-smmu-v3.c) allows an attacker holding a low-privileged local context to subvert the IOMMU's protection mechanism and reach kernel-level access on a vulnerable device. The flaw is a logic error affecting multiple functions of the driver, rated CVSS 7.8 with a local attack vector, low privileges, and no user interaction required. Google ships the fix in the September 2026 Pixel/Android security bulletin; no CISA KEV listing and no public exploit code were identified at the time of analysis.
Improper input validation in multiple locations of the Android kernel allows a locally installed application to escalate privileges on affected Pixel and Android devices, with no additional execution privileges or user interaction required. The flaw is rated 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting a local attacker who already holds low-privileged code execution but can reach high-integrity kernel operations. It is addressed in the September 2026 Android/Pixel security bulletin; at time of analysis there is no CISA KEV listing, no confirmed public exploit code, and no EPSS signal was supplied with the source data.
An out-of-bounds write reachable through a race condition in google_mba_recv_msg() in google_mba_poll.c allows a locally installed low-privilege application on an affected Android device to corrupt kernel memory and escalate to system/kernel privileges. Rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N), the flaw requires no user interaction but does need the attacker to already run code on the device and to win a timing window, which keeps it materially below a remote, unauthenticated severity. No public exploit code has been identified and the issue is not listed in CISA KEV at time of analysis; no EPSS score was supplied in the source data.
Memory corruption in the ARM64 TLB-invalidation path of the Android kernel allows a local attacker holding low privileges to win a race condition and escalate to kernel/root privileges, with no user interaction and no additional execution privileges required. Affected builds are Google Android (CPE cpe:2.3:a:google:android:*:*:*:*:*:*:*:*), specifically ARM64 devices; Google's September 2026 Pixel security bulletin is the vendor reference for the fix. No EPSS score, CISA KEV listing, or public proof-of-concept was present in the supplied intelligence, so active exploitation is unconfirmed and no public exploit code has been identified at time of analysis.
Let me build the JSON. CVE-2026-58724: Android kernel use-after-free due to race condition, local EoP requiring System execution privileges, no UI. CVSS 7.0 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Reported by Google Devices. CPE: google:android. Tags: Privilege Escalation, Google, Race Condition. Reference: Android security bulletin September 2026 Pixel. Note: "System execution privileges needed" — this is Android bulletin phrasing meaning the attacker needs System-level privileges already... Actually in Android bulletins, "System execution privileges needed" means the vulnerability requires the attacker to already have System privileges? Hmm, actually Android bulletin says "This could lead to local escalation of privilege with System execution privileges needed" — meaning the attacker needs System execution privileges? Historically it means exploitation requires the attacker to run code with System privileges already... Actually it means the vulnerability can lead to local escalation of privilege with System execution privileges needed — i.e., it requires System-level privileges to exploit. That means privilege escalation from System to... hmm, in Android, "System" is a UID (system uid 1000). So it escalates to kernel. Actually "with System execution privileges needed" means the attacker must already have System privileges. CVSS PR:L is consistent-ish. Actually PR:L. Hmm but if System privileges needed, PR:H might be more apt. Given CVSS says PR:L, I'll assess PR:L... Hmm. My own assessment: AV:L/AC:H/PR:H? Let me think. The Android phrasing "System execution privileges needed" — needed to exploit — implies significant privileges already (system UID, not just any app). That's PR:H arguably. But CVSS gives PR:L. I'll go with PR:H? Let's be careful — I should ground my assessment in the description. The description says "with System execution privileges needed" — this means the exploit requires system-level privileges. So PR:H is honest. But the vendor's own CVSS says
Let me synthesize. CVE-2026-58710: DecodeFilmGrainParams in film_grain_dec.cc — Android libavc / media codec film grain decoding. Missing bounds check → OOB write → RCE. CVSS 8.8 with AV:N/AC:L/PR:L/UI:N — note PR:L is odd but that's given. CWE-120 (buffer copy without checking size). Reported by Google Devices, references Android Security Bulletin Pixel 2026-09-01. CPE google:android. EUVD affected versions: "Android Android kernel" — weird. Tags: RCE, Buffer Overflow, Google. Missing tag maybe "android". Product name: "Android" — or "Android Film Grain Decoder"? 1-3 words. "Google Android" maybe. Let's use "Android Media Codecs"? Hmm. The vulnerability is in film_grain_dec.cc which is part of libavc (Android's AVC decoder) or a codec2 component. Probably Android's media framework. Product name should be specific: "Android". Let's pick "Google Android" (2 words). Prevalence: Android is ubiquitous. Assessed CVSS vector: Given description "remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation." But CVSS vector says PR:L. Hmm. Media decoding typically happens when processing a media file — remotely delivered via messaging, or via media server. PR:L suggests some level of privilege required — perhaps access to a media-decoding service context, or the requirement to send media to a privileged process. Actually, for Android media codecs, an app can trigger decoding with its own privileges. The vendor assigned PR:L. I should give my own assessment. Given the description says "no additional execution privileges needed" and UI:N, but AV:N with media parsing... Typically media parsing is AV:L or AV:N depending on delivery. Android media codec flaws are usually CVSS AV:N/AC:L/PR:N/UI:R for a crafted file. Here UI:N suggests it's triggered via a network media stream (e.g., RTP, video call) without user opening a file. PR:L — the attacker needs local privileges? Hmm, in Android, media codec processes (media.
A permission bypass in the Android Cellular Modem (baseband) component lets an attacker who is within radio range of the device escalate privileges inside the modem context, exposing confidentiality, integrity and availability of device data with no user interaction. Exploitation requires the attacker to already hold low-level privileges on the modem interface (CVSS PR:L) and to be network-adjacent (AV:A), which in practice points to a rogue or compromised cellular base station rather than an internet-based attacker. The flaw stems from a logic error in permission checking rather than a memory-safety bug, and at time of analysis there is no public exploit code and no CISA KEV listing, though the vendor has published a fix in the September 2026 Pixel security bulletin that should be treated as authoritative.
A race condition in the trusty_dputc() debug output path of generic-arm64-smcall.c in the Android kernel allows an out-of-bounds write that can be leveraged for local privilege escalation. The flaw is only reachable by a process already running with System execution privileges, and exploitation requires winning a timing window (AC:H, PR:L), with no user interaction. Impact is high across confidentiality, integrity and availability because the corrupted memory is kernel/secure-monitor adjacent, but no public exploit code or in-the-wild exploitation is known from the available intelligence.
An out-of-bounds write in Android's IP Multimedia Subsystem (IMS) telephony stack allows an attacker positioned on the cellular signaling path to corrupt memory and achieve code execution inside the privileged process that handles VoLTE/VoWiFi traffic. User interaction on the target is not required, and the September 2026 Pixel bulletin identifies the flaw as remotely triggerable via improperly validated input. No public exploit code or CISA KEV entry was identified at the time of analysis, and no EPSS score was supplied with the source data, so real-world exploitation activity is unconfirmed.
An out-of-bounds write in the NXP NFC hardware abstraction layer (phNxpNciHal_ext_process_nfc_init_rsp in phNxpNciHal_ext.cc) lets a local attacker corrupt memory beyond the intended buffer while the HAL processes an NFC initialization response. Affected are Android devices that ship the NXP NFC HAL, which the Android CPE lists without a version bound; the flaw requires no user interaction and, per Google's bulletin wording, no additional execution privileges, so a typical app-level foothold is enough to attempt escalation. There is no CISA KEV listing and no public exploit code reported in the supplied intelligence, so exploitation is assessed as feasible but not yet observed.
An out-of-bounds write in Av1DecodeFrameTag (vp9hwd_headers.cc) in the Android media decoding stack allows crafted AV1/VP9 media content to corrupt memory and potentially achieve remote code execution in the codec process, which runs with elevated system privileges relative to a normal app. Google's Pixel security bulletin dated 2026-09-01 lists the fix, and no user interaction is required, though the provided CVSS vector (PR:L) implies the attacker must already be able to route content into the decoder path. No EPSS score, CISA KEV entry, or public exploit code was supplied with this record, so active exploitation is unconfirmed.
An out-of-bounds write in Android's audio RTP payload encoder node (AudioRtpPayloadEncoderNode.cpp) lets a remote attacker execute arbitrary code in the media framework process by supplying a crafted audio RTP payload that the node fails to validate. Affected builds are Android/Pixel devices covered by the September 2026 Android Security Bulletin; the vendor description states user interaction is required to trigger the flaw, and an NVD/EUVD record exists alongside the source.android.com advisory. No public exploit code or CISA KEV entry was identified in the supplied intelligence, and no EPSS score was provided at time of analysis.
A heap-based buffer overflow (out-of-bounds write) exists in the Android Cellular Modem component, allowing an attacker within adjacent/proximal radio range to corrupt heap memory and potentially execute code in the modem context without user interaction. The flaw carries a CVSS base score of 8.0 (AV:A/AC:L/PR:L/UI:N) and affects Google Android devices per the Android/Google Devices CPE. No public exploit code or CISA KEV listing was provided at time of analysis, so exploitation status is unconfirmed; the vendor fix is documented in the September 2026 Pixel/Android Security Bulletin.
Local privilege escalation in Google Android's VPU (Video Processing Unit) driver lets an unprivileged app trigger an out-of-bounds write through a confused-deputy path, corrupting kernel memory and gaining root-level code execution on the device. Per the CVSS vector, the attacker must already hold local code execution (PR:L) but needs no user interaction, and the September 2026 Pixel/Android Security Bulletin confirms a vendor fix. No public exploit code or CISA KEV activity has been identified at time of analysis.
An out-of-bounds write in ReadTileInfo of vp9hwd_headers.cc lets a crafted VP9 bitstream corrupt memory inside Android's VP9 hardware-decoder header parser, which Google rates as remote escalation of privilege with no additional execution privileges and no user interaction required. Affected builds are those tracked under the Google Android CPE and addressed by the Android/Pixel security bulletin dated 2026-09-01. There is no CISA KEV listing and no public exploit code identified at time of analysis, so this is currently a patch-window issue rather than a confirmed in-the-wild campaign.
Let me synthesize. CVE-2026-56920: Android HEVC decoder, firmware header parsing (fw_hevc_dec_header.c), s_decode_vui_param out-of-bounds write, CWE-787, CVSS 8.8 AV:N/AC:L/PR:L/UI:N. Note: "remote code execution with no additional execution privileges needed" — but CVSS says PR:L. Hmm, this is typical Android bulletin wording: "This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation." That's media framework / remote. But CVSS says PR:L which contradicts "no additional execution privileges needed". Actually Android media codecs often run in a sandboxed process (mediaserver), so PR:L reflects the sandbox context. There's a conflict worth noting. Product name: Android (Google Android). Or "Android HEVC Decoder"? 1-3 words. "Google Android" or "Android". Let's use "Android Media Framework"? Hmm — the file is fw_hevc_dec_header.c, HEVC decoder header parsing. Probably part of Android's media codec/firmware. I'll say "Android HEVC Decoder" — 3 words. Actually the CPE says google:android. Product name: "Android HEVC Decoder". Hmm, maybe safer: "Google Android". The field says the specific product or service name affected. CPE is google:android, and it's the HEVC decoder in Android firmware for Pixel devices (bulletin is Pixel). I'll go with "Android HEVC Decoder". Summary: Out-of-bounds write in HEVC VUI parameter decoding. Affected: Android devices with affected firmware (Pixel bulletin 2026-09-01). Remote code execution with no user interaction. No KEV, no POC identified. EPSS: not provided. KEV: not stated → assume not in KEV. POC: not provided → "no public exploit identified at time of analysis". Technical context: HEVC/H.265 VUI (Video Usability Information) parameters in SPS/VPS NAL units; s_decode_vui_param in fw_hevc_dec_header.c; firmware-based HEVC decoder in Android; logic error → insufficient bounds validation → OOB write → memory corruption in media codec process. CWE-787.
Let me synthesize. CVE-2026-56882: Cellular Modem (Android Pixel), information disclosure due to logic error, leading to RCE, no additional execution privileges, no UI. CVSS 8.8 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. CWE-200 (Exposure of Sensitive Information). Reported by Google_Devices, Pixel bulletin September 2026. Product name: "Android Cellular Modem" — 1-3 words. Maybe "Android Cellular Modem" (3 words). Or "Pixel Cellular Modem". Let's use "Android Cellular Modem". Prevalence: Android is ubiquitous. But cellular modem specifically... The affected component is the cellular modem firmware in Android/Pixel devices. Prevalence of Android = ubiquitous. Hmm. The CPE is google:android. Modem component. I'd say "ubiquitous" given Android base. But the specific modem component... The CPE says google:android, so I'll go with ubiquitous. Actually maybe "high"? Android is on billions of devices — ubiquitous is defensible. Let me say ubiquitous with basis "core platform component across billions of Android devices". Hmm, but cellular modem is only in phones with cellular. Still ubiquitous. Actually, let's be careful — the CPE is google:android which is the whole OS. Cellular modem affects devices with cellular radios = most Android phones. I'll go with ubiquitous. CVSS vector given: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H — PR:L is odd for a modem, but that's the input. Note the mismatch: description says "no additional execution privileges needed" but vector says PR:L. That's a conflict to note. My assessed vector: Given it's a modem logic error leading to info disclosure → RCE, remote. I'll assess AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H? Hmm. Let me think. Cellular modem attack — typically over-the-air from a rogue base station or via malicious network. AC:H might be reasonable (requires specific modem state / malformed signaling). But CVSS says AC:L. I'll go with AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H — hmm, but "no additional execution privileges needed" suggests PR:N. But
An integer overflow in the Android VPU (video processing unit) driver's size handling leads to an out-of-bounds write in kernel memory, allowing a locally installed application to escalate privileges to kernel/system level on affected Pixel devices. Exploitation requires only local low-privileged access (CVSS:3.1/AV:L/AC:L/PR:L/UI:N) and no user interaction, making it attractive for a malicious or trojanized app. No public exploit code or CISA KEV listing was identified at time of analysis, and the EPSS signal is not provided; the vulnerability is addressed in the September 2026 Android/Pixel security bulletin.
In decodeAmr of ImsMediaAudioPlayer.cpp, there is a possible out-of-bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation.
An out-of-bounds write in Android's IP Multimedia Subsystem (IMS) telephony stack, corrected in the September 2026 Android/Pixel security bulletin, can be turned into remote code execution against affected devices. The published vector (CVSS 8.8, AV:N/AC:L/PR:L/UI:N, C/I/A all High) indicates network-reachable exploitation with no user interaction, though it assumes low-level privileges while the description claims no additional execution privileges are needed. No public exploit code, EPSS score, or CISA KEV entry was provided, so active exploitation is not confirmed at time of analysis.
Local privilege escalation in the Android kernel's fingerprint (gf) driver allows a process with access to the fingerprint device interface to corrupt kernel heap memory and gain root-level code execution. The flaw is a heap-based out-of-bounds write in gf_base_update_finger_base() within gf_base.c, exploitable with a low-privileged local context and no user interaction, consistent with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N). Fixes are delivered through the Android/Pixel Security Bulletin dated 2026-09-01; no public exploit code or CISA KEV listing was identified at time of analysis.
A use-after-free race condition in multiple locations of the Android kernel allows an attacker to corrupt kernel memory and escalate to remote code execution, affecting Android devices covered by the September 2026 Android Security Bulletin. Exploitation requires an attacker to already hold a low-privilege foothold on the device (CVSS PR:L) — typically a malicious or compromised application — and no user interaction is needed once that foothold exists. No public exploit code or CISA KEV listing was identified at time of analysis, so this is currently a patch-now kernel hardening issue rather than a confirmed in-the-wild campaign.
Remote exploitation of the cellular modem stack in Google Android devices allows an attacker who controls the radio path to trigger a heap-based out-of-bounds write and escalate privileges on the handset, without any user interaction. The supplied CVSS 3.1 base score of 8.8 reflects high confidentiality, integrity and availability impact, but its PR:L metric (low privileges required) conflicts with the vendor description stating that no additional execution privileges are needed. No public exploit code, EPSS score, or CISA KEV entry was included in the intelligence feed, so active exploitation is unconfirmed at the time of analysis.
An out-of-bounds write in the Goodix fingerprint trusted-application test handler (gf_ta_test_set_config in gf_ta_test.c) on Android allows a locally installed application holding low privileges to corrupt memory and escalate to kernel-level privileges without any user interaction. The flaw stems from improper validation of caller-supplied input reaching a memory-write path inside the fingerprint TA interface. Google addressed it in the Pixel security bulletin dated 2026-09-01; no public exploit code or CISA KEV entry was identified at time of analysis.
An out-of-bounds write in the Android kernel, caused by a logic error in multiple code locations, allows code execution in the kernel context with high impact to confidentiality, integrity and availability. The flaw is remotely reachable per the CVSS vector (AV:N/AC:L/PR:L/UI:N) and requires no user interaction, though the vector indicates a low-privileged rather than fully unauthenticated attacker. Google published a fix in the Pixel security bulletin dated 2026-09-01; no public exploit code, EPSS score, or CISA KEV listing was provided in the available intelligence, so active exploitation is not confirmed.
An out-of-bounds write in Android's VP9 hardware decoder (Vp9DecodeFrameTag in vp9hwd_headers.cc) lets a crafted VP9 video stream corrupt memory in the codec context, giving an attacker code execution at the decoder's privilege level. Affected devices are those running Android builds that include the vulnerable VP9 hardware decoding path prior to the September 2026 Pixel security bulletin fix. No public exploit code or CISA KEV entry was identified at time of analysis, so exploitation appears to require a motivated actor with a delivery path for malicious media.
An out-of-bounds write in Google's Android Cellular Modem component allows code execution in the baseband when a crafted message is delivered to the modem, with no user interaction required. Google Pixel devices running Android builds prior to the September 2026 patch level are affected, per the Pixel security bulletin. Rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N, high confidentiality, integrity and availability impact); no public exploit code or CISA KEV entry was identified at time of analysis, so the immediate risk is to targeted radio-layer attacks rather than mass exploitation.
Let me parse the data. CVE-2026-19407: Bucket Squatting in Google Cloud Gemini Enterprise Agent Platform SDK for Python versions prior to 1.166.1. Allows RCE and tenant-project token theft. CVSS 7.7, CVSS 4.0 vector: AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L. CWE-330 (Use of Insufficiently Random Entropy — actually CWE-330 is "Use of Insufficiently Random Values"). Bucket squatting: attacker registers a cloud storage bucket name that the SDK attempts to use (predictable/guessable name), and the SDK downloads code/artifacts from that bucket, leading to RCE. Related to insufficient randomness in bucket naming. EPSS: not provided. KEV: not provided (no). POC: not provided. Note discrepancy: Description says versions prior to 1.166.1; EUVD says "1.16.0 <1.165.1". That's a data conflict — flag in confidence_notes. Patch: Available from vendor — release notes from March 31, 2026. Affected products: Google Cloud Gemini Enterprise Agent Platform SDK for Python, versions prior to 1.166.1 (fix version 1.166.1). Prevalence: This is a specific SDK — medium/low. It's a Google Cloud SDK for an agent platform — niche enterprise. I'd say "low". Hmm. Gemini Enterprise Agent Platform SDK for Python — AI agent dev kit. Deployment footprint probably low-medium. I'll say "low" with basis "specialized Google Cloud AI agent SDK, limited deployment footprint". Actually maybe "medium" since Google Cloud + Gemini is popular. But the specific SDK for agent platform — low. I'll go with "low". Assessed CVSS vector: AT:P means attack requirements are present (attacker must pre-register the bucket name — that's an attack requirement). PR:N, UI:P (victim must run the SDK / user interaction). So my 3.1 vector: AV:N/AC:H/PR:N/UI:R/S:C? Hmm. Scope — subsequent system impact SC:L/SI:L/SA:L, so scope changed in 3.1 terms. Let's do: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. Hmm, but scope change with C:H/I:H/A:H might be too high. Actually the vulnerable system impact is H/H/H.
Privilege escalation in Mozilla Firefox for Android allows an attacker who can get a user to open a crafted web page to gain privileges beyond those normally granted to web content, with high impact to confidentiality, integrity, and availability. Mozilla fixed the flaw in Firefox 156; no public exploit code and no active exploitation have been identified, and CISA's SSVC assessment rates exploitation as 'none' with automatable 'no'. The 8.8 CVSS score is driven entirely by a network attack vector plus required user interaction (UI:R), so real-world risk depends on convincing a target to browse attacker-controlled content rather than on mass scanning.
Gallery - Private Photo Vault 1.0.41 (Android, by Brain Trust) exposes an unauthenticated HTTP server on TCP port 8080 that is reachable by any device on the same local network, serving full directory listings and file contents from Android external storage - the very media the app is marketed to protect. Any network-adjacent attacker can trivially enumerate and exfiltrate photos, videos, and other files without credentials or user interaction. No public exploit code is required beyond a standard web browser or curl; Fluid Attacks' advisory confirms a proof-of-concept exists, but no CISA KEV listing has been identified at time of analysis.
Race condition in Microsoft Edge (Chromium-based) builds prior to 152.0.4191.66 lets an attacker who already holds low-privileged code execution inside the browser win a narrow timing window and elevate to full privileges outside the Chromium sandbox. The flaw is CWE-362 (concurrent execution on a shared resource with improper synchronization) and carries a CVSS 3.1 score of 7.8 with a Scope:Changed rating, indicating a successful exploit crosses a security boundary rather than simply corrupting the renderer. Exploitation is local, timing-dependent (AC:H) and non-automatable per CISA SSVC; no public exploit code or CISA KEV entry is associated with this CVE at time of analysis, and a vendor patch is available.
Ekia File Manager 1.2.7 for Android ships an exported ContentProvider (com.ekia.filecontrolmanager.OpenFileProvider) that declares no android:permission, readPermission, or writePermission, so any other app on the same device can invoke it. The provider maps the caller-supplied URI path straight to a filesystem path and passes it to new File(...), letting a malicious local app make the File Manager process read, create, overwrite, or delete every file that process can reach. The issue is not in CISA KEV, EPSS is only 0.11% (2nd percentile), and no public exploit tooling was identified in the supplied data, so real-world priority depends almost entirely on whether untrusted apps can be installed on the target device.
Improper input validation in Zscaler Client Connector for Android and ChromeOS (builds prior to 4.2.0.152) lets an attacker with elevated local privileges on the endpoint feed malformed input to the connector and bypass Zscaler's traffic inspection and access controls, with a CVSS 8.1 (AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L) rating that reflects total loss of the security control's integrity. The flaw is not remotely exploitable and requires high privileges (root or equivalent device-admin context) on the affected Android or ChromeOS device, and there is no public exploit identified at time of analysis. EPSS is 0.12% (2nd percentile) and CISA SSVC records exploitation 'none', automatable 'no' with total technical impact — a low-likelihood, patch-promptly issue rather than an emergency.
Out-of-bounds read and write in the Linux kernel's Chrome EC sensorhub driver exposes Chromebook-class systems to kernel heap corruption via an unvalidated 8-bit sensor number in EC FIFO events. The cros_ec_sensor_ring_process_event() function indexes batch_state[] using the sensor_num field from embedded-controller events without checking it against the allocated array size, allowing any event carrying sensor_num >= sensorhub->sensor_num to access arbitrary adjacent kernel heap memory. No public exploit or CISA KEV listing exists; EPSS is 0.20%, but the C:H/I:H/A:H CIA impact reflects the potential for kernel memory corruption on affected Chrome EC hardware.
Use-after-free in Microsoft Edge (Chromium-based) enables an authenticated network attacker to achieve remote code execution with scope change across all supported platforms including Windows, Linux, macOS, Android, and iOS. The vulnerability carries a CVSS 8.5 with high complexity and scope change (S:C), indicating that successful exploitation escapes the browser's sandboxing boundary and affects the underlying host. No public exploit or CISA KEV listing is present at time of analysis, though patch-available status from Microsoft confirms vendor acknowledgment.
Server-Side Request Forgery in Google Cloud Gemini Enterprise Agent Platform App Builder (all versions prior to the 2026-06-01 deployment date) enables unauthenticated remote attackers to exfiltrate the Compute Engine default service account access token by forcing the application to issue requests to the GCP instance metadata service. The stolen OAuth 2.0 bearer token carries the IAM permissions of the default service account, potentially enabling lateral movement across GCP project resources. Vendor-released patch was deployed on 1 June 2026, but existing app deployments require a manual redeployment to receive the fix - creating remediation lag risk for unmanaged deployments.
Arbitrary code execution in Google Cloud's Gemini CLI (npm @google/gemini-cli < 0.39.1) and the run-gemini-cli GitHub Action (< 0.1.22) lets an unprivileged attacker run code on the host by planting untrusted local .env / .gemini configuration files that override GEMINI_CLI_HOME. In headless (CI) mode, previous versions auto-trusted workspace folders and processed their config/environment variables, so a malicious pull request or issue processed by an automated Gemini workflow could trigger RCE; a related --yolo tool-allowlist bypass compounds the risk. Patched by vendor; no public exploit identified at time of analysis and it is not in CISA KEV.
Unencrypted UDP video transmission in the C6 Ear Camera and its companion EarVision Android application (version 1.3.1 / firmware 1.3.1_Code 132) exposes live ear-canal video streams to passive eavesdropping by any attacker within local wireless range. The camera broadcasts JPEG and WEBP frames over plaintext UDP with no transport-layer security, and the Android application's manifest explicitly permits cleartext traffic, removing any client-side enforcement barrier. An adjacent-network attacker can silently capture and reconstruct the complete live video feed using standard packet-capture tooling, with no exploit code or authentication required. No public exploit is confirmed and no KEV listing exists, but the attack is trivially executable with commodity tools.
Remote code execution in Google Cloud Agent Development Kit (ADK) for Python versions 2.0.0 through 2.6.0 allows an unauthenticated remote attacker to run arbitrary code on the host by submitting a crafted test session replay to the 'adk web' developer interface when the pytest package is present. The flaw stems from an incomplete input-restriction check (CWE-184) that lets malicious replay content reach code execution. No public exploit has been identified at time of analysis, but the vendor rates it CVSS 10.0 and shipped a fix in v2.7.0.
Heap-based buffer overflow in Google Chrome's WebRTC component (all versions prior to 153.0.8010.36) enables a remote unauthenticated attacker to potentially execute arbitrary code within the Chrome renderer sandbox by luring a target to a crafted HTML page. The vulnerability is classified CWE-122 and carries a CVSS base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); however, Chromium's own internal severity rating is 'Low,' which is notably discordant and implies that exploitation is constrained to within-sandbox code execution rather than full OS compromise. No public exploit code and no CISA KEV listing have been identified at the time of analysis.
Incorrect authorization in the Extensions component of Google Chrome before 153.0.8010.36 allows a remote attacker to bypass system access restrictions and reach a privileged internal page by luring a victim to a crafted HTML page. Google credits its own team with discovery, and a fixed build is available; no public exploit has been identified at time of analysis, and Chromium rated the underlying issue only Low severity despite the 9.8 NVD score.
Race-condition-triggered code execution in Google Chrome's V8 JavaScript engine (all versions prior to 153.0.8010.36) allows a remote unauthenticated attacker to execute arbitrary code inside the Chrome renderer sandbox by serving a crafted HTML page to a victim. Exploitation is constrained to the Chrome sandbox process rather than the underlying OS, which aligns with Chromium's own internal severity rating of 'Low' despite the CVSS base score of 7.5. No public exploit code or CISA KEV listing is present at time of analysis; the high attack complexity metric reflects the timing-sensitive nature of race-condition exploitation.
Improper certificate validation in Chrome's Federated Credential Management (FedCM) component — fixed in Chrome 153.0.8010.36 — lets a remote attacker who controls crafted network traffic, combined with social engineering of the victim, bypass web origin policy and expose cross-origin identity data. The flaw is a confidentiality-only issue (no integrity or availability impact) and Chrome rates it security severity Low, despite a 7.5 CVSS base score; EPSS is only 0.15% (4th percentile), it is not in CISA KEV, and no public exploit code has been identified at time of analysis. Vendor-released patch: 153.0.8010.36.
Memory corruption in V8, Chrome's JavaScript engine, allows an attacker who can get a user to install a crafted Chrome extension to execute arbitrary code confined within the Chrome sandbox, affecting all Chrome versions prior to 153.0.8010.36. Despite the CVSS 8.8 base score, Chromium's own security team rates this 'Low' severity, reflecting that exploitation is bounded by Chrome's sandbox and does not constitute a full OS-level compromise without a separate sandbox escape primitive. No public exploit code or active exploitation has been identified at time of analysis. Vendor-released patch is available.
Sandbox escape via incorrect authorization in the Chrome Updater component on Windows allows a local attacker to execute arbitrary code outside the browser's sandbox using a crafted local program. Affected versions are all Google Chrome releases prior to 153.0.8010.36 on Windows. The Chromium team rates internal severity as 'Low' - notably lower than the CVSS 8.1 score - suggesting that while the impact is high if exploited, real-world attack complexity limits practical risk. No public exploit or active exploitation has been identified at time of analysis.
Use-after-free in Google Chrome's DevTools component (versions prior to 153.0.8010.36) enables arbitrary code execution within the renderer sandbox when a victim is socially engineered into visiting a crafted HTML page. The CVSS score of 8.8 reflects full C/I/A impact, but Chromium's own internal severity classification of 'Low' signals that exploitation is sandboxed - OS-level compromise requires an additional chained sandbox escape. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Remote code execution in Google Chrome's DevTools component before 153.0.8010.36 stems from a use-after-free (CWE-416) that, per the advisory, allows a crafted HTML page to execute arbitrary code outside the browser sandbox. All desktop Chrome builds prior to the fixed stable release are affected; the flaw was reported internally by the Chrome team, is fixed in the stable channel, and has no public exploit identified at time of analysis. Notably, the assigned CVSS is 9.6 (Critical) while Chromium itself rated the security severity only 'Low', a significant conflict discussed below.
We need answer JSON only. Need synthesize. Need be careful: The description says SSRF in Mobile in Google Chrome prior to 153.0.8010.36, social engineering, crafted HTML page, Chromium severity Low. CVSS 9.8 contradictory: SSRF with social engineering likely UI, low severity, but given CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Need assess. We need follow instructions. Let's inspect input. CVE-2026-87595. Description: Server-side request forgery in Mobile in Google Chrome prior to 153.0.8010.36 allowed a remote attacker leveraging social engineering to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Low) CVSS Score 9.8 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. CWE-918. Multi-source: EPSS 0.18% percentile 7%. Patch available from vendor. Reported by Chrome. CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*:* (no version bounds in CPE string). Tags: Google, SSRF. ENVD affected versions ["Chrome 153.0.8010.36 <153.0.8010.36"] weird: probably means versions before 153.0.8010.36. References. Need output fields all strings except data_quality_flags is array? User says Return JSON object, data_quality_flags JSON array. But earlier "Every field below MUST be a plain text string — NOT an array, NOT an object" includes data_quality_flags? It says every field below must be plain text string, but data_quality_flags description says JSON array. Conflict. Need follow field description likely array. In final JSON, data_quality_flags can be array, but "Every field below MUST be a plain text string" maybe says all fields must be strings; but data_quality_flags is exception? They explicitly say JSON array. We should output array for data_quality_flags. Need ensure no markdown. Need produce product_name: "Google Chrome" (affected product). Maybe "Chrome" but product_name should specific product. "Google Chrome" okay. Summary: Must not copy description. Must start with impact verb and product. E.g. "Server-side request forgery in Google Chrom
Sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The flaw resides in the Storage component's incorrect reference resolution (CWE-706), making this a second-stage exploit that chains with a separate renderer compromise to achieve full sandbox breakout. No public exploit has been identified at time of analysis, and the fix is available in the stable channel release 153.0.8010.36.
Sandbox-escaping remote code execution in Google Chrome's WebPackaging component affects all desktop versions prior to 153.0.8010.36. A use-after-free (CWE-416) reachable from a crafted HTML page can let a remote attacker potentially execute arbitrary code outside the renderer sandbox with no authentication, requiring only that the victim visit a malicious page. No public exploit has been identified at time of analysis; Chromium's own internal triage rated the security severity 'Low', which sits in notable tension with the 9.6 CVSS assigned to the record.
Remote code execution in Google Chrome on iOS before 153.0.8010.36 stems from a use-after-free in the Sharing component (CWE-416), letting a remote attacker who lures a victim to crafted network content execute arbitrary code outside the browser sandbox. Google has shipped a patched Chrome build; no public exploit is identified at time of analysis, and Google/Chromium rated the underlying bug 'Medium' severity even though the assigned CVSS base score is 9.6.
Remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the Passwords component that, when triggered via crafted UI interaction and social engineering, can let a remote attacker escape the renderer sandbox and run arbitrary code. All Chrome desktop builds before the 153.0.8010.36 stable release are affected. No public exploit identified at time of analysis, and no EPSS or KEV data was provided; note that Google's Chromium team rated the underlying bug only 'Medium' severity, which sits in tension with the supplied CVSS 9.6.
Sandbox-escaping remote code execution in Google Chrome's Aura windowing layer affects all desktop builds prior to 153.0.8010.36. A remote attacker who lures a victim to a crafted HTML page can trigger a use-after-free (CWE-416) and potentially execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the fix ships in the stable-channel desktop update.
Out-of-bounds write in the Media component of Google Chrome before 153.0.8010.36 allows a remote attacker to potentially execute arbitrary code outside the browser's renderer sandbox by luring a victim to a crafted HTML page. The scope-changing memory-corruption bug carries a CVSS of 9.6 despite Chromium's own 'Medium' severity rating, and a vendor patch is available. There is no public exploit identified at time of analysis.
Remote code execution in Google Chrome on Windows prior to 153.0.8010.36 arises from a type-confusion bug in the browser's Rust code, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Google shipped a fixed build via the Stable channel, and the flaw was reported internally by the Chrome team. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though sandbox-escape memory-corruption bugs in Chrome are historically high-value exploitation targets.
Sandbox-escape remote code execution affects Google Chrome on macOS prior to 153.0.8010.36, where an improper quantity-validation flaw (CWE-1284) in Tint, the WebGPU/WGSL shader compiler in Chromium's Dawn graphics stack, lets a crafted HTML page break out of the renderer sandbox. A remote attacker who lures a victim to a malicious web page can potentially execute arbitrary code with the privileges of the browser process on the host. Google reports a fix is shipped; there is no public exploit identified at time of analysis, and Chromium internally rated the issue Medium severity despite the high provided CVSS.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from a numeric truncation error in the Media component, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. The vendor patch is available via the September 2026 stable-channel update; no public exploit is identified at time of analysis. Note a signal conflict: Chromium rated this 'Medium' severity while the supplied CVSS base score is 9.6 Critical.
Remote code execution in Google Chrome for macOS prior to 153.0.8010.36 stems from a use-after-free in the Extensions component, letting a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw carries a CVSS 9.6 (scope-changed, network vector with user interaction), though Chromium's own security team rated it 'Medium'. No public exploit has been identified at time of analysis, and the fix is available in the stable channel.
FileAPI improper input validation in Google Chrome prior to 153.0.8010.36 enables an attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code on the underlying host system. The flaw, tracked in Chromium issue 532957878, was addressed in the September 2026 stable channel release. With an EPSS of 0.30% and no confirmed active exploitation, this functions as a second-stage sandbox-escape primitive rather than a standalone remote attack.
Use-after-free in Chrome's V8 JavaScript engine allows a remote attacker who can socially engineer a victim into installing a crafted Chrome extension to execute arbitrary code within the browser's renderer sandbox, affecting all Chrome versions prior to 153.0.8010.36. The vulnerability is constrained to in-sandbox execution - it does not constitute a standalone sandbox escape - which aligns with the S:U CVSS metric and Chromium's internal 'Medium' severity rating despite the 8.8 base score. No public exploit code or active exploitation has been identified at time of analysis, and Google has shipped a patch in the stable channel.
Missing authorization in the Extensions subsystem of Google Chrome prior to 153.0.8010.36 enables a remote attacker to obtain sensitive browser information by delivering a crafted Chrome extension that bypasses access control checks. The vulnerability is classified CWE-862 (Missing Authorization), meaning the runtime fails to enforce proper permission boundaries between extension capabilities and protected browser data. No public exploit code or active exploitation has been identified at time of analysis; Chromium's own internal severity rating of 'Medium' reflects practical exploitation barriers not fully captured by the NVD CVSS 7.5 High rating.
Use-after-free in Google Chrome's DevTools component prior to 153.0.8010.36 enables a local attacker to escape the browser sandbox and execute arbitrary code at the host OS level via a crafted local program. Chromium's own severity rating is 'Medium', reflecting the local access prerequisite, while the CVSS 8.1 score captures the high-impact sandbox-escape outcome once exploitation succeeds. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the EPSS score (0.12%, 2nd percentile) confirms low observed exploitation probability.
Sandbox escape via incorrect authorization in the Views component of Google Chrome on Windows (versions prior to 153.0.8010.36) enables arbitrary code execution outside the browser sandbox. Exploitation requires an attacker to first compromise the renderer process and then leverage social engineering to induce user interaction with a crafted HTML page. No public exploit or KEV listing exists at time of analysis; Chromium's own severity rating of Medium contrasts with the CVSS 8.3 score, reflecting the difficult two-stage attack chain.
Sandbox escape via improper initialization (CWE-665) in Google Chrome's Views UI framework on Windows, prior to version 153.0.8010.36, can lead to arbitrary code execution outside the browser sandbox. The attack is chained: an adversary must first compromise the renderer process through a separate vulnerability, then leverage social engineering to trigger the Views initialization flaw, elevating from renderer-level code execution to full host OS access. No public exploit code has been identified and EPSS sits at 0.28% (20th percentile), consistent with the multi-step prerequisite bar, though the C:H/I:H/A:H impact profile warrants prompt patching.
Sandbox-escaping remote code execution in Google Chrome's Browser process on Windows (all versions prior to 153.0.8010.36) stems from a use-after-free flaw. A remote attacker who lures a victim into opening a crafted HTML page can corrupt reclaimed heap memory in the privileged browser process and execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the vendor has shipped a fixed stable build.
Uncontrolled search path element in Chrome's Windows CredentialProvider component (CWE-427) enables a local attacker to execute arbitrary code outside the browser sandbox on Windows systems running Chrome prior to 153.0.8010.36. The flaw is a DLL or executable search-order hijacking issue: Chrome's CredentialProvider resolves a dependency by searching an attacker-controllable path, allowing a malicious local program to intercept and execute in place of a legitimate component, with the result escaping Chrome's sandbox entirely. No public exploit code or CISA KEV listing has been identified at time of analysis.
Site isolation bypass in Google Chrome's FileSystem component allows a remote attacker who has already achieved renderer process compromise to escape cross-origin boundaries via a crafted PDF file. Affected versions are all Chrome releases prior to 153.0.8010.36 on desktop platforms. The vulnerability (CWE-863, Incorrect Authorization) enables the attacker to read or modify data belonging to other origins, undermining Chrome's core sandboxing guarantee. No public exploit or active exploitation (CISA KEV) has been identified; EPSS is 0.16%, consistent with the SSVC 'Exploitation: none' rating.
Incorrect authorization in Google Chrome's Permissions subsystem before version 153.0.8010.36 enables remote attackers to exfiltrate sensitive browser information through a crafted Chrome extension that requires social engineering to install. The flaw (CWE-863) causes Chrome's permission brokering layer to incorrectly authorize an extension's access to protected browser data, resulting in high-confidence confidentiality impact with no integrity or availability consequence. No public exploit has been identified and EPSS sits at 0.18%, consistent with the social-engineering prerequisite that constrains mass opportunistic exploitation.
Site isolation bypass in Google Chrome prior to 153.0.8010.36 allows a remote attacker who has already compromised the renderer process to escape Chrome's cross-site isolation boundary via a crafted file combined with social engineering. The flaw is rooted in incorrect authorization (CWE-863) within the SiteIsolation component, meaning the browser fails to properly enforce origin-based access controls once the renderer is under attacker control. Vendor-released patch 153.0.8010.36 is available; no public exploit has been identified and EPSS sits at 0.16% (6th percentile), consistent with the Chromium team's 'Medium' severity rating despite the CVSS 8.8 base score.
Sandbox-escape remote code execution in Google Chrome for Android before 153.0.8010.36 arises from an integer overflow in the GPU process, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. Fixed in the same 153.0.8010.36 Stable Channel release that addressed several other GPU/media memory-safety bugs; no public exploit identified at time of analysis. Note the rating tension: the input CVSS is 9.6 (Critical) while Google's own Chromium severity is only Medium.
Missing authorization in the WebView component of Google Chrome on Android before 153.0.8010.36 lets a remote attacker who first tricks a user via social engineering bypass system access restrictions through crafted network traffic. The flaw is tracked as CWE-862 (missing authorization) and was reported by Google's Chrome team; a vendor patch is available. Chromium rates the security severity as Medium, EPSS is low (0.17%), and no public exploit or CISA KEV listing has been identified.
Use-after-free in Chrome's ANGLE graphics layer on Windows enables sandbox escape and arbitrary code execution when a renderer process has already been compromised. Affected versions are all Chrome releases prior to 153.0.8010.36 on Windows; exploitation requires an attacker to first compromise the renderer and then deliver a crafted HTML page triggering the ANGLE memory corruption. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.28% (20th percentile) reflects low observed exploitation probability.