Monthly
Sandbox escape in Google Chrome (Linux and ChromeOS) prior to 148.0.7778.179 allows a remote attacker who has already compromised the renderer process to break out via a crafted video file processed by the GFX component. The flaw is a type confusion (CWE-843) rated High severity by Chromium, with no public exploit identified at time of analysis and SSVC indicating exploitation has not been observed. It requires user interaction and chained exploitation of a prior renderer compromise, which raises the bar despite the High CVSS of 7.5.
Remote code execution in Google Chrome versions prior to 148.0.7778.179 stems from a use-after-free condition in the QUIC networking stack, allowing remote attackers to execute arbitrary code within the browser sandbox via malicious network traffic. Exploitation requires user interaction (visiting a malicious site or processing attacker-controlled QUIC traffic), and no public exploit has been identified at time of analysis. Chromium rates this as High severity, and a vendor patch is available.
Remote code execution in Google Chrome on Windows prior to version 148.0.7778.179 stems from a use-after-free condition in the GPU component, enabling a remote attacker to run arbitrary code within the renderer sandbox after the victim loads a crafted HTML page. Google has rated the issue High severity and shipped a fix; no public exploit identified at time of analysis and SSVC indicates exploitation status 'none' despite total technical impact.
Remote code execution in Google Chrome on Linux before 148.0.7778.179 stems from a use-after-free flaw in the WebRTC component, allowing a remote attacker who lures a victim to a crafted HTML page to execute arbitrary code in the renderer process. Chromium rates the severity as Critical and a vendor patch is available, though there is no public exploit identified at time of analysis and SSVC indicates no observed exploitation. The CVSS 8.8 score reflects high impact across confidentiality, integrity, and availability with required user interaction (visiting a page).
Sandbox escape in Mozilla Firefox and Firefox Focus for Android lets a malicious web page break out of the content-process sandbox after luring a victim to attacker-controlled content, gaining full confidentiality, integrity, and availability impact on the affected process. Mozilla addressed it in Firefox 151 (advisory MFSA2026-46); there is no public exploit identified at time of analysis, and EPSS rates near-term exploitation at just 0.05% (16th percentile). CISA SSVC records exploitation status as none with a total technical impact, indicating a serious-but-not-yet-exploited browser flaw.
Arbitrary directory deletion in CloakBrowser's cloakserve CDP multiplexer (pip package cloakbrowser <= 0.3.27) allows unauthenticated network attackers to delete directories accessible to the service user by supplying path traversal sequences in the fingerprint query parameter. The service binds to 0.0.0.0 by default, dramatically widening exposure, and no public exploit identified at time of analysis though the vulnerability is trivially reproducible from the published advisory.
Remote code execution in Microsoft Edge (Chromium-based) versions prior to 148.0.3967.70 allows attackers to execute arbitrary code on victim systems when a user is lured to a malicious webpage. The vulnerability stems from improper input validation (CWE-20) and carries a CVSS 3.1 score of 8.8 with high impact across confidentiality, integrity, and availability. No public exploit identified at time of analysis, and the vulnerability is not currently listed in CISA KEV.
Rate limiter bypass in better-auth versions < 1.4.17 allows attackers to defeat authentication attempt limits by rotating through IPv6 addresses within their allocated /64 prefix or using different textual representations of the same address. The vulnerability affects authentication endpoints including sign-in, sign-up, and password reset when serving IPv6 clients, which includes most cloud providers by default. No public exploit identified at time of analysis.
Remote code execution in Google Cloud Application Integration allows unauthenticated attackers to access exposed internal API endpoints and execute arbitrary code. The vulnerability stems from improper access controls on internal APIs that were inadvertently exposed to external networks. With a CVSS 4.0 score of 10.0, this represents a critical risk allowing both information disclosure and full system compromise without authentication.
URL parser mismatch in Open WebUI allows authenticated users to bypass SSRF protections and access internal network resources. The validate_url function uses Python's urlparse library to extract hostnames for validation, while the requests library handles actual HTTP requests. These libraries disagree on parsing URLs containing backslash characters (e.g., http://127.0.0.1:6666\@1.1.1.1), allowing attackers to craft URLs that pass validation as external addresses but resolve to internal hosts. Exploitation requires low-privilege authentication but no user interaction, enabling access to cloud metadata endpoints and internal services. Fixed in version 0.9.5 per GitHub advisory GHSA-8w7q-q5jp-jvgx.
Arbitrary code execution in Google Chrome on macOS (versions prior to 148.0.7778.168) stems from a use-after-free in the browser's Extensions subsystem, allowing an attacker who convinces a user to install a malicious extension to run arbitrary code through a crafted Chrome extension. Chromium rates the severity Medium, but the CVSS 3.1 base score is 8.8 (High) because the flaw yields full confidentiality, integrity, and availability impact once triggered. There is no public exploit identified at time of analysis, it is not listed in CISA KEV, and the EPSS probability is negligible (0.02%, 5th percentile), indicating no observed real-world exploitation to date.
Out-of-bounds memory read in Google Chrome on iOS versions before 148.0.7778.168 enables remote attackers to access sensitive memory contents through a compromised renderer process. The vulnerability requires user interaction to visit a malicious webpage and exploitation of a prior renderer compromise. With EPSS at 0.03% and no known active exploitation, this represents a moderate risk primarily in targeted attack chains.
Arbitrary code execution in Google Chrome's GPU component (prior to 148.0.7778.168) lets a remote attacker run code inside the renderer/GPU sandbox by luring a victim to a crafted HTML page. The flaw is a CWE-416 use-after-free that Chromium rates Medium, though CVSS scores it 8.8 (High). No public exploit is identified and there is no CISA KEV listing; EPSS is very low at 0.08%, indicating no observed exploitation activity at time of analysis.
Sandbox escape in Google Chrome's Mojo IPC layer allows a remote attacker who lures a victim to a crafted HTML page to exploit a use-after-free (CWE-416) and potentially break out of the renderer sandbox on versions prior to 148.0.7778.168. Google fixed the flaw in the stable desktop channel (148.0.7778.168), and there is no public exploit identified at time of analysis (EPSS 0.07%, not in CISA KEV). Note a signal conflict: the CVSS base score is 9.6 (Critical) while Chromium's own triage rated the severity only Medium, so real-world exploitability is likely lower than the raw score implies.
Remote code execution in Google Chrome before 148.0.7778.168 stems from an integer overflow in the browser's font handling code, allowing a remote attacker who lures a victim to a crafted HTML page to execute arbitrary code - though notably constrained to run inside the renderer sandbox rather than achieving full host compromise. The flaw carries a CVSS of 8.8 but is rated Medium by Chromium's own severity scale, reflecting the sandbox containment. There is no public exploit identified at time of analysis, EPSS is very low (0.08%), and CISA SSVC records exploitation status as none.
Sandbox escape in Google Chrome desktop before 148.0.7778.168 lets an attacker who already controls a compromised renderer process leverage a use-after-free in the browser UI component to break out of the renderer sandbox via a crafted HTML page. This is the second-stage bug in a typical browser exploit chain and Chromium rates it Medium severity; there is no public exploit identified at time of analysis and EPSS estimates only a 0.07% exploitation probability. Google has released a fixed stable-channel build, and Red Hat and SUSE have picked it up for their Chromium packages.
Sandbox escape in Google Chrome on Windows before 148.0.7778.168 stems from a use-after-free in the browser's Core component, allowing an attacker who has already compromised the renderer process to break out of the sandbox and potentially execute code in the more privileged browser process via a crafted HTML page. Google rates it Medium severity internally, though the assigned CVSS is 8.3 due to the scope change and total impact. There is no public exploit identified at time of analysis, EPSS is very low (0.07%), and SSVC records exploitation status as none.
Sandbox escape in Google Chrome on Windows (versions prior to 148.0.7778.168) can be triggered by an integer overflow in the codecs component when the browser processes a crafted video file, allowing a remote attacker to potentially break out of the renderer sandbox. Chromium rates the security severity as Medium; the assigned CVSS is 8.3 due to high complexity but scope change and full CIA impact. There is no public exploit identified at time of analysis, EPSS is very low (0.07%), and CISA SSVC lists exploitation status as none, indicating no observed attacks.
Sandbox escape in Google Chrome for Android before 148.0.7778.168 lets an attacker who has already compromised the renderer process break out of the sandbox through insufficient policy enforcement in the GPU component, escalating a contained renderer bug into fuller device compromise via a crafted HTML page. Rated Medium by Chromium but scored CVSS 8.3 by NVD due to the scope change and total technical impact. There is no public exploit identified at time of analysis and EPSS probability is low (0.09%).
Sandbox escape in Google Chrome for macOS (versions prior to 148.0.7778.168) stems from an out-of-bounds write in the browser's media codec handling, letting a remote unauthenticated attacker who lures a victim into opening a crafted video file corrupt memory and potentially break out of the renderer sandbox. The flaw carries a CVSS 8.3 rating driven by a scope-changing, full-triad impact, though Chromium internally rated the security severity only Medium. There is no public exploit identified at time of analysis, EPSS is very low at 0.07%, and CISA SSVC records exploitation as none.
Privilege escalation in Google Chrome desktop before 148.0.7778.168 lets an attacker who has already compromised the renderer process abuse a use-after-free in the Accessibility component to break out of the sandbox and gain elevated privileges via a crafted HTML page. Rated High by Chromium and scored CVSS 7.5, it is a second-stage exploit primitive rather than a standalone entry point. There is no public exploit identified at time of analysis, it is not in CISA KEV, and EPSS is very low at 0.07%.
Remote code execution in Google Chrome on Windows before 148.0.7778.168 stems from a use-after-free in the GTK component, letting a remote attacker run arbitrary code when a victim opens a crafted HTML page. Google rates the Chromium severity High and has shipped a fixed Stable channel build; no public exploit is identified at time of analysis, EPSS risk is low (0.08%), and CISA SSVC marks exploitation status as none.
Remote code execution in Google Chrome desktop before 148.0.7778.168 stems from a use-after-free (CWE-416) in the Downloads component, letting a remote attacker who lures a victim into performing specific UI interactions run arbitrary code via a crafted HTML page. Rated High by Chromium and CVSS 8.8, the flaw was reported internally by the Chrome team and is patched in the Stable channel update. No public exploit identified at time of analysis, and EPSS is low at 0.08%.
Remote code execution in Google Chrome's Media component (versions prior to 148.0.7778.168) allows a remote attacker to run arbitrary code within the renderer sandbox when a victim opens a crafted HTML page. Rated High by Chromium and CVSS 8.8, the flaw is a use-after-free (CWE-416); Google has shipped a fixed Stable channel build. There is no public exploit identified at time of analysis, EPSS is low (0.08%), and CISA SSVC records exploitation as none - though memory-corruption bugs in Chrome's media stack are historically attractive to attackers.
Sandbox escape in Google Chrome's Media component (versions prior to 148.0.7778.168) allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page. This is an out-of-bounds write (CWE-787) rated High by Chromium and CVSS 8.3, but exploitation is gated on chaining from a prior renderer compromise, and there is no public exploit identified at time of analysis. EPSS is very low (0.07%, 21st percentile) and CISA SSVC lists exploitation status as none.
Privilege escalation in Google Chrome's Passwords component on Windows (versions prior to 148.0.7778.168) lets a remote attacker who has already compromised the renderer process escape its privilege boundary via a crafted HTML page. Rated High by Chromium and CVSS 7.5, it is a second-stage bug used to extend an existing renderer foothold rather than an initial-access vector. There is no public exploit identified at time of analysis, and the EPSS score is very low (0.07%, 20th percentile), consistent with SSVC marking exploitation as none.
Remote code execution in Google Chrome's Media component (versions prior to 148.0.7778.168) allows a remote attacker to run arbitrary code within the renderer sandbox when a victim visits a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium with a CVSS of 8.8; no public exploit identified at time of analysis, and SSVC records no observed exploitation with a low EPSS of 0.08%. Exploitation requires user interaction (visiting a malicious page) and, because code runs inside the sandbox, a separate sandbox-escape bug would be needed for full host compromise.
Sandbox escape in Google Chrome on Windows before 148.0.7778.168 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox and gain code execution at higher privilege on the host. The flaw is a use-after-free (CWE-416) in Chrome's Core component, triggered via a crafted HTML page; Google rates it High severity. No public exploit has been identified at time of analysis, and EPSS is very low (0.07%, 21st percentile), consistent with an internally reported bug not yet weaponized.
Remote code execution in Google Chrome's V8 JavaScript engine before 148.0.7778.168 allows a remote attacker to run arbitrary code within the renderer sandbox when a victim visits a crafted HTML page. Rated High by Chromium and CVSS 8.8, the flaw is a type confusion bug and requires user interaction (visiting a malicious page); no public exploit identified at time of analysis and EPSS probability is very low (0.08%). Google has shipped a patched Stable channel release.
Sandbox escape in the GPU process of Google Chrome (and ChromeOS) on Linux, fixed in 148.0.7778.168, lets an attacker who has ALREADY compromised the renderer process break out of the browser sandbox via a crafted HTML page. This is a second-stage bug rather than an initial-access flaw, so it must be chained with a separate renderer exploit to be useful. There is no public exploit identified at time of analysis, EPSS is very low (0.07%), and CISA SSVC lists exploitation as none, though the technical impact if exploited is total.
Sandbox escape in Google Chrome desktop before 148.0.7778.168 lets a remote attacker who has already compromised the renderer process break out of the sandbox by triggering a use-after-free in the Accessibility component via a crafted HTML page. Rated High by Chromium and scored CVSS 8.3, it is a second-stage exploit primitive rather than a standalone remote break-in. No public exploit identified at time of analysis, and EPSS is very low (0.07%, 21st percentile), consistent with the SSVC exploitation status of 'none'.
Sandboxed remote code execution in Google Chrome desktop versions prior to 148.0.7778.168 allows a remote attacker to run arbitrary code within the browser's renderer sandbox by luring a victim to a crafted HTML page. The flaw stems from an integer overflow in Chrome's XML handling and is rated High by Chromium; it requires user interaction (visiting a malicious page) and carries no public exploit identified at time of analysis, with a low EPSS of 0.08%.
Heap buffer overflow in Google Chrome's WebML component on Windows lets a remote attacker trigger heap corruption-and potentially achieve code execution in the renderer-by luring a victim to a crafted HTML page in a version prior to 148.0.7778.168. Chromium rates the flaw High severity, and a vendor patch is available. There is no public exploit identified at time of analysis, and EPSS exploitation probability is low (0.06%).
Sandbox escape in Google Chrome on Windows before 148.0.7778.168 lets an attacker who already controls a compromised renderer process break out of the browser sandbox by triggering a use-after-free in the Network component via a crafted HTML page. It is a second-stage bug that chains onto a prior renderer compromise rather than a standalone entry point, carrying High Chromium severity and CVSS 8.3. There is no public exploit identified at time of analysis, and EPSS is very low at 0.07% (21st percentile).
Remote code execution in Google Chrome desktop prior to 148.0.7778.168 stems from a heap buffer overflow in the browser's media Codecs component, allowing a remote attacker to run arbitrary code within the renderer sandbox when a victim processes a crafted video file. Reported internally by the Chrome team and rated High severity by Chromium, it carries CVSS 8.8 but requires user interaction (UI:R). There is no public exploit identified at time of analysis, and EPSS is low at 0.07%.
Remote code execution in Google Chrome's Downloads component before version 148.0.7778.168 allows a remote attacker to execute arbitrary code when a victim visits or interacts with a crafted HTML page. Chromium rates this High severity, and the CVSS 8.8 vector confirms the flaw is network-reachable and unauthenticated but requires user interaction (UI:R). There is no public exploit identified at time of analysis, and EPSS is low (0.08%), consistent with CISA SSVC marking exploitation status as none.
Out-of-bounds write in the WebRTC component of Google Chrome before 148.0.7778.168 lets a remote attacker achieve arbitrary code execution inside the renderer sandbox when a victim opens a crafted HTML page. Rated High by Chromium and CVSS 8.8, it requires user interaction (visiting a page) but no authentication. There is no public exploit identified at time of analysis, EPSS is low (0.07%), and CISA SSVC lists exploitation as none, indicating no observed in-the-wild activity yet.
Sandbox escape in Google Chrome for macOS before 148.0.7778.168 stems from a heap buffer overflow in the ANGLE graphics abstraction layer, letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox and cross into a higher-privilege context. Google rates the Chromium severity High and a fixed build is available, but there is no public exploit identified at time of analysis. EPSS is very low (0.06%) and CISA SSVC records exploitation status as none, indicating no observed attacks.
Out-of-bounds write in Google Chrome's WebAudio component (versions prior to 148.0.7778.168) lets a remote attacker achieve arbitrary code execution within the renderer sandbox when a victim opens a crafted HTML page. Google rates the Chromium severity as High and has shipped a fixed Stable channel build; there is no public exploit identified at time of analysis and the EPSS score is very low (0.07%). Because execution is confined to the sandbox, real-world impact typically requires chaining a separate sandbox-escape bug.
Renderer-sandboxed remote code execution in Google Chrome's Fonts component (versions prior to 148.0.7778.168) lets a remote attacker run arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page. Rated High by Chromium and CVSS 8.8, the flaw is a CWE-787 out-of-bounds write reported internally by the Chrome team. There is no public exploit identified at time of analysis, and EPSS is very low (0.04%, 11th percentile), consistent with the CISA SSVC assessment of no known exploitation.
Sandbox escape in Google Chrome desktop versions prior to 148.0.7778.168 lets an attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page, abusing a use-after-free in the Mojo IPC layer. Rated High by Chromium and CVSS 8.3, it enables a scope change from the low-privilege renderer to the more-privileged browser process. There is no public exploit identified at time of analysis, it is not in CISA KEV, and EPSS is very low (0.07%), indicating no observed exploitation.
Remote code execution in Google Chrome on macOS prior to 148.0.7778.168 stems from a use-after-free in the Downloads component, letting a remote attacker who lures a victim to a crafted HTML page corrupt memory and execute arbitrary code in the browser process. Rated Critical by Chromium and CVSS 8.8, it requires user interaction (visiting the page) but no authentication. No public exploit identified at time of analysis, and EPSS is low (0.08%), consistent with SSVC exploitation status of 'none'.
Remote code execution in Google Chrome's Tab Groups component (versions prior to 148.0.7778.168) stems from a use-after-free (CWE-416) that a remote attacker can trigger via malicious network traffic, per Google's Chrome Releases advisory rated Chromium-Critical. Successful exploitation yields arbitrary code execution in the affected browser process with total technical impact. There is no public exploit identified at time of analysis, EPSS is very low (0.03%, 10th percentile), and CISA SSVC records exploitation status as none.
Sandbox escape in Google Chrome's Payments component before 148.0.7778.168 lets a remote attacker who lures a victim to a crafted HTML page break out of the renderer sandbox by winning a race condition. Rated Critical by Chromium and scored CVSS 8.3, it carries a scope-changing high-impact profile, though EPSS is a low 0.06% and there is no public exploit identified at time of analysis. A vendor patch is available and the flaw is not listed in CISA KEV.
Out-of-bounds memory write in Google Chrome's ANGLE graphics abstraction layer on Windows before 148.0.7778.168 lets a remote attacker corrupt memory by luring a victim to a crafted HTML page, potentially leading to renderer-process code execution. Rated Critical by Chromium and scored CVSS 8.8, it requires user interaction (visiting a page) but no authentication. Currently there is no public exploit identified and the SSVC exploitation status is 'none', though the very low EPSS (0.07%) reflects newness rather than confirmed safety.
Renderer-side arbitrary code execution in Google Chrome desktop before 148.0.7778.168 stems from a use-after-free in the Blink rendering engine, letting a remote attacker who lures a victim to a crafted HTML page run code within the browser's renderer sandbox. Chromium rates the flaw Critical severity; however, exploitation still requires the user to open a malicious page (UI:R), the code executes inside the sandbox (scope unchanged), and there is no public exploit identified at time of analysis. EPSS is low (0.08%, 23rd percentile) and CISA SSVC records exploitation as 'none', so this is a high-severity but not yet actively exploited issue.
Remote code execution in Google Chrome on macOS (versions prior to 148.0.7778.168) stems from an object lifecycle flaw in the WebShare API, allowing a remote attacker to run arbitrary code within the browser process after luring a victim to a crafted HTML page and getting them to perform specific UI gestures. Rated Critical by Chromium and reported internally by the Chrome team, a vendor patch is available; there is no public exploit identified at time of analysis, and the EPSS probability is very low (0.07%). CISA SSVC currently rates exploitation as none with total technical impact.
Sandbox escape in Google Chrome desktop before 148.0.7778.168 stems from a use-after-free in the WebHID implementation, letting a remote attacker who lures a victim into specific UI gestures on a crafted HTML page corrupt memory and potentially break out of the renderer sandbox. Chromium rates the severity Critical, though no public exploit is identified and EPSS is very low (0.07%). Exploitation requires user interaction and is not automatable, indicating a high-skill rather than mass-exploited threat.
Sandbox escape in Google Chrome's Aura windowing subsystem (versions prior to 148.0.7778.168) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page. Rated Critical by Chromium and CVSS 8.3, it is a use-after-free (CWE-416) that serves as the second stage of an exploit chain rather than an initial entry point. There is no public exploit identified at time of analysis, and EPSS is very low (0.07%), consistent with a patched, chain-dependent bug.
Sandbox escape in Google Chrome for Android before 148.0.7778.168 lets an attacker who has already compromised the renderer process leverage a use-after-free in the Input component to break out of the sandbox via a crafted HTML page. Rated Critical by Chromium and CVSS 8.3, this is a second-stage bug requiring an existing renderer compromise rather than a standalone remote exploit. EPSS is very low (0.07%) and there is no public exploit identified at time of analysis; SSVC records no observed exploitation.
Sandbox escape in Google Chrome desktop before 148.0.7778.168 stems from a use-after-free in the FileSystem component, letting a remote attacker who serves a crafted HTML page and coaxes the victim into specific UI gestures corrupt memory and break out of the renderer sandbox. Chromium rates it Critical, and the CVSS:3.1 8.3 score reflects a scope change (S:C) with full confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; EPSS is low at 0.07% (21st percentile).
Sandbox escape in Google Chrome's UI layer, driven by a use-after-free (CWE-416) reachable before version 148.0.7778.168, lets a remote attacker who lures a victim to a crafted HTML page break out of the renderer sandbox. Google rates the Chromium severity Critical and has shipped a fix; there is no public exploit identified at time of analysis, and EPSS is low (0.07%, 21st percentile), so this is a high-severity but not-yet-exploited memory-safety bug. SSVC lists exploitation as none with total technical impact.
Out-of-bounds memory write in Google Chrome's Skia graphics library on Windows (versions prior to 148.0.7778.168) lets an attacker who has already compromised the renderer process trigger an integer overflow via a crafted HTML page, corrupting memory in a Critical-rated flaw. It is a second-stage primitive used to widen an existing renderer foothold, not a standalone remote-entry bug. No public exploit identified at time of analysis, and EPSS is very low (0.07%, 21st percentile), consistent with the SSVC 'Exploitation: none' assessment.
Remote code execution in Google Chrome's WebML component (versions prior to 148.0.7778.168) allows a remote attacker to run arbitrary code within the browser's renderer sandbox by luring a victim to a crafted HTML page. Chromium rates this a Critical severity heap buffer overflow (CWE-122), though the CVSS base is 8.8 because code execution is contained inside the sandbox rather than achieving a full host compromise. There is no public exploit identified at time of analysis, and the EPSS score is very low (0.06%, 20th percentile), consistent with SSVC showing no observed exploitation.
Authentication bypass in the Burst Statistics WordPress plugin versions 3.4.0 through 3.4.1.1 allows unauthenticated remote attackers to impersonate any administrator whose username they know by supplying an arbitrary Basic Authentication password. The flaw resides in flawed return-value handling within the `is_mainwp_authenticated()` function used to validate application passwords from the Authorization header, enabling privilege escalation per request. No public exploit identified at time of analysis, and EPSS is low (0.26%), but the CVSS 9.8 score and SSVC 'total' technical impact mark it as a high-severity authentication bypass worth prioritizing.
Broken access control in the MonsterInsights Google Analytics plugin for WordPress (versions up to and including 10.1.2) lets any authenticated user with Subscriber-level access or higher call the unprotected get_ads_access_token() and reset_experience() functions, exposing live Google OAuth access tokens and letting them reset the plugin's Google Ads integration. The disclosed OAuth tokens can be abused to access the linked Google Ads/Analytics account outside WordPress, while the reset function disrupts the site's advertising integration. No public exploit identified at time of analysis, and EPSS is very low (0.03%), consistent with SSVC exploitation status of 'none'.
Session persistence after credential change in SillyTavern before 1.18.0 lets an attacker holding a stolen session cookie retain full account access even after the victim resets their password. Because sessions are stateless and stored entirely in a signed client-side cookie with a default 400-day lifespan, the change-password and account-recovery endpoints update the password hash but never revoke outstanding tokens, defeating the standard remediation for cookie theft. No active exploitation is recorded (not in CISA KEV) and EPSS is very low at 0.02%, but public proof-of-concept reproduction steps are documented in the GHSA advisory.
Information disclosure in Microsoft Edge (Chromium-based) before 148.0.3967.55 allows a remote, unauthenticated attacker to read data they should not have access to by luring a victim into interacting with malicious web content. Rooted in external control of a file name or path (CWE-73) with a changed CVSS scope, it can leak sensitive information across security boundaries. Reported by Microsoft with a vendor patch available; no public exploit identified at time of analysis and EPSS exploitation probability is very low (0.05%).
Full administrative database takeover in Google Cloud AlloyDB for PostgreSQL affected clusters provisioned via Terraform or the REST API before 2025-11-03, where those provisioning paths applied an insecure default password. A remote attacker with network reachability to such a cluster could authenticate as a privileged account and gain complete control of the database. There is no public exploit identified at time of analysis, and the EPSS probability is very low (0.04%, 12th percentile), consistent with the SSVC assessment of no observed exploitation.
Remote unauthenticated attackers can decrypt user credentials and hijack IoT device sessions in Meari SDK-based mobile applications (CloudEdge, Arenti, white-label apps) by exploiting hardcoded cryptographic keys shared across all installations. The SDK embeds API signing secrets, password-transport encryption keys, and service access tokens in application binaries, enabling adversaries to intercept and decrypt account credentials in transit, forge authenticated API requests, and potentially access cloud services without user authentication. No public exploit code identified at time of analysis, but EPSS scoring and exploitation complexity are low given the static nature of hardcoded secrets.
Decompression bomb safeguards in urllib3 2.6.0 can be bypassed during streaming API operations, causing excessive CPU and memory consumption on client systems. Applications using urllib3 versions 2.6.0 through 2.6.x that stream Brotli-compressed responses with multiple read() calls, or invoke drain_conn() after partial decompression, may decompress entire payloads instead of requested chunks. This allows malicious servers to trigger resource exhaustion attacks against urllib3 clients. Vendor-released patch (version 2.7.0) confirmed by GitHub advisory GHSA-mf9v-mfxr-j63j. No public exploit identified at time of analysis, but exploitation requires only a malicious HTTP server delivering compressed responses - a low-complexity attack scenario.
Server-side request forgery in Gotenberg's Chromium URL-to-PDF endpoint allows unauthenticated remote attackers to exfiltrate cloud credentials and access internal services. The primary `/forms/chromium/convert/url` endpoint ships with no default deny-list for HTTP/HTTPS targets - only blocking file:// URIs - enabling direct access to AWS/GCP/Azure metadata endpoints at 169.254.169.254, RFC 1918 private networks, and localhost services. Even when administrators configure custom deny-lists, attackers bypass validation via HTTP 302 redirects, as Chromium follows redirects without re-validating destinations. Vendor-confirmed public exploit code exists (PoC in GHSA-chwh-f6gm-r836). Patch available in version 8.32.0.
Cross-origin WebSocket hijacking in the Cline `kanban` server (npm `kanban`, shipped via the `cline` CLI ≤ 2.13.0) lets any website a developer visits silently connect to the loopback server on 127.0.0.1:3484 and leak workspace paths, task content, git branches, and AI-agent chat, then inject prompts into a running agent's terminal for remote code execution and kill active tasks. Because browsers do not apply CORS to WebSocket handshakes and the three endpoints perform no Origin validation or authentication (CWE-306), exploitation needs only that the victim run kanban and browse to an attacker page. A full interactive proof-of-concept exists (publicly available exploit code exists); it is not listed in CISA KEV and EPSS is very low at 0.02%, indicating no observed mass exploitation to date.
Remote code execution in SiYuan's Electron renderer occurs when users hover over search results, file tree items, or attribute view elements containing URL-encoded XSS payloads in document titles or metadata. The vulnerability chains a URL-decoding step (decodeURIComponent) with unsafe innerHTML assignment in tooltip rendering, bypassing the escapeAriaLabel sanitizer that only handles HTML entities but ignores %XX URL escapes. Because SiYuan's renderer runs with nodeIntegration:true and contextIsolation:false, the XSS escalates to arbitrary code execution via require('child_process'). Exploitation requires user interaction (hovering) but no authentication, and malicious payloads survive .sy.zip export/import and sync replication, enabling supply-chain and shared-workspace attacks. No public exploit code identified at time of analysis, though detailed proof-of-concept is published in the GitHub advisory.
Server-side request forgery in n8n-mcp versions 2.18.7 through 2.50.1 allows authenticated attackers with MCP session access to bypass SSRF protections and send HTTP requests to cloud metadata endpoints and internal services, with response bodies returned directly to the attacker. Multi-tenant HTTP deployments are critically exposed: any tenant sharing an AUTH_TOKEN can exfiltrate AWS IAM, GCP service account, or Azure managed identity credentials from the operator's cloud metadata service (169.254.169.254 and related endpoints). Single-tenant and stdio deployments remain vulnerable via indirect prompt injection attacks that manipulate LLM tool calls. Vendor-released patch: n8n-mcp version 2.50.2. No CVSS score assigned; no public exploit code identified at time of analysis, though the advisory contains sufficient technical detail for proof-of-concept development.
Remote code execution in SiYuan's Electron desktop application allows authenticated attackers (or browser extensions on localhost) to inject malicious JavaScript through unescaped Attribute View names, escalating from stored XSS to arbitrary system command execution. The Go kernel backend stores AV names without HTML escaping, then embeds them via string replacement into HTML templates pushed over WebSocket. Three TypeScript renderer paths (render.ts, Title.ts, transaction.ts) consume this data using innerHTML/outerHTML without sanitization. Because the Electron main window runs with nodeIntegration:true and contextIsolation:false, script injection grants full Node.js API access—enabling attackers to spawn child processes (calc.exe/xcalc demonstrated in PoC), exfiltrate SSH keys, install backdoors, or pivot to cloud credentials. Payloads persist in JSON files under data/storage/av/, replicate across all sync transports (S3/WebDAV/cloud), survive .sy.zip export-import, and trigger for any user role (Administrator/Editor/Reader/Visitor) opening a document bound to the poisoned database view. CVSS 9.4 (Network/Low/None/High Confidentiality-Integrity-Availability + Scope Changed) reflects worst-case remote network vector, though the primary realistic attack path is via installed browser extensions (chrome-extension:// Origin explicitly allowlisted in session.go:277) calling the /api/transactions endpoint as an auto-granted admin on default installations with no Access Authorization Code. GitHub advisory GHSA-2h64-c999-c9r6 confirms patch available in kernel commit 0.0.0-20260512140701-d7b77d945e0d. No public exploit code identified at time of analysis, but detailed reproduction steps with curl payloads and Electron DevTools inspection are published in the advisory.
Use-after-free (UAF) in Linux kernel Bluetooth subsystem allows adjacent network attackers to trigger memory corruption via malformed LE Read Features Complete responses. The vulnerability occurs when hci_conn is freed before le_read_features_complete callback executes but after hci_le_read_remote_features_sync initiates, causing atomic operations on freed memory during hci_conn_drop. Active exploitation status not confirmed (no CISA KEV listing). EPSS score of 0.02% (5th percentile) indicates very low observed exploitation probability. Upstream patches committed to stable kernel branches 6.19.12+ and 7.0+.
Remote unauthenticated attackers can access Google Secrets Manager credentials from unintended GCP projects via crafted requests to Spring Cloud Config servers using Google Secrets Manager as a backend. VMware confirmed this high-severity information disclosure vulnerability (CVSS 7.5) affecting all 3.1.x through 5.0.x versions. No CISA KEV listing or public exploit code identified at time of analysis, but the network-accessible attack vector with no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N) indicates straightforward exploitation once attackers identify vulnerable Spring Cloud Config deployments with Google Secrets Manager integration.
Unauthenticated server-side request forgery (SSRF) in Gotenberg 8.30.1 and earlier allows remote attackers to force the server to make HTTP requests to internal/loopback addresses by bypassing default deny-lists with IPv4-mapped IPv6 notation (e.g., http://[::ffff:127.0.0.1]:port). The vulnerability affects both the downloadFrom file-fetching feature and the webhook delivery feature. Attackers can read content from internal HTTP endpoints and trigger state-changing requests against services bound to localhost, exposing internal APIs, cloud metadata endpoints, and admin interfaces. Fix available in version 8.32.0. No public exploit code confirmed outside the GitHub advisory PoC, not listed in CISA KEV, but CVSS 9.4 Critical rating reflects the network-accessible, unauthenticated nature and high confidentiality/integrity impact.
Unauthenticated remote attackers crash Gotenberg 8.x (≤ 8.31.0) by triggering a race condition between webhook goroutine context reuse and Echo framework connection pooling. When webhook middleware spawns an async goroutine holding an `echo.Context` reference, the synchronous handler returns immediately, recycling the context to Echo's `sync.Pool`. Concurrent requests reset the pooled context, causing unchecked type assertions in the still-running webhook goroutine to panic outside any `recover()` scope, terminating the process with exit code 2. Twenty-four webhook requests plus sixty concurrent GET requests demonstrate reliable two-second crash windows. No patch was available at initial disclosure; upstream commit fixes the panic in version 8.32.0. CVSS 7.5 (AV:N/AC:L/PR:N/UI:N) reflects trivial unauthenticated network exploitation producing complete service disruption.
Server-Side Request Forgery in Gotenberg's LibreOffice conversion endpoint allows remote attackers to make arbitrary HTTP requests from the server to internal networks and cloud metadata endpoints. Attackers upload specially crafted Office documents (DOCX, XLSX, PPTX) with embedded external URL references that LibreOffice fetches during PDF conversion, completely bypassing the SSRF protections introduced in v8.31.0. Publicly available exploit code exists with detailed proof-of-concept showing three successful HTTP requests to attacker-controlled servers. The vulnerability enables exfiltration of cloud IAM credentials from metadata services (169.254.169.254), internal service enumeration, and network reconnaissance without authentication. CVSS 8.2 with network vector and no privileges required reflects accurate real-world risk given documented exploitation method and lack of vendor-released patch.
Unauthenticated remote code execution in Gotenberg 8.29.1 allows network attackers to execute arbitrary OS commands via newline injection in PDF metadata keys. The `/forms/pdfengines/metadata/write` endpoint passes user-controlled JSON metadata keys directly to ExifTool without control-character validation. Embedding `\n` in a key splits ExifTool's stdin stream, injecting arbitrary flags including `-if` which evaluates Perl expressions. Attack returns HTTP 200 with valid PDF output, evading basic monitoring. CVSS 9.8 (AV:N/AC:L/PR:N/UI:N) reflects critical network-accessible RCE. No vendor-released patch identified at time of analysis — GitHub advisory GHSA-rqgh-gxv4-6657 confirms the issue but CPE data shows no fixed version. Publicly available exploit code exists in Python and bash with OOB exfiltration. Default Docker image `gotenberg/gotenberg:8` runs the vulnerable process as uid 1001 with root group membership, amplifying post-exploitation impact.
Unauthenticated remote control of the Optoma CinemaX P2 smart projector (firmware TVOS-04.24.010.04.01, Android 8.0.0) is possible through an HTTP API listening on TCP port 2345. Any host on the same network can read 74 configuration endpoints and write settings including power, volume, brightness, display mode, and network protocol toggles - notably enabling TELNET, which can widen the attack surface. No public exploit identified at time of analysis, and EPSS is very low (0.02%), but the flaw requires no credentials and CVSS is rated 9.8.
Unauthenticated remote root access on Optoma CinemaX P2 smart projectors allows network attackers to execute arbitrary code with full system privileges. The device ships with ADB enabled on TCP 5555 without authentication (ro.adb.secure=0) and contains an unrestricted su binary, enabling complete device compromise including WiFi credential theft, malware installation, and data exfiltration. EPSS score (0.02%, 6th percentile) indicates low widespread exploitation probability, though SSVC framework assesses total technical impact. No public exploit code or active exploitation confirmed at time of analysis.
JupyterLab's CommandLinker executes arbitrary commands via single-click social engineering when users open malicious notebooks shared through email, GitHub, or Binder links. Attackers embed deceptive HTML buttons with allowlisted data-commandlinker-* attributes in pre-saved notebook output cells to trigger commands without code execution submission, enabling immediate arbitrary code execution in available kernels, silent file deletion, or resource exhaustion in multi-tenant deployments. The patched version 4.5.7 was released by the JupyterLab team through GitHub advisory GHSA-mqcg-5x36-vfcg. Chromium browser users face expanded terminal access risk through multi-click clipboard permission abuse. Third-party JupyterLab extensions increase attack surface by exposing additional commands to exploitation.
Chrome DevTools Protocol exposure in OpenClaw sandbox browser allows adjacent network attackers to remotely control sandboxed Chrome instances and access sensitive data. The CDP relay binds to 0.0.0.0 without source IP restrictions in versions before 2026.4.10, enabling attackers on the same Docker network to bypass sandbox isolation and execute arbitrary JavaScript in browser contexts. Vendor-released patch available (v2026.4.10); no public exploit identified at time of analysis. CVSS 9.0 reflects adjacent network attack vector with high confidentiality, integrity, and availability impact across virtual and system scopes.
Sandbox escape in Google Chrome prior to 148.0.7778.96 allows remote attackers to break out of Chrome's security sandbox via specially crafted network traffic targeting a policy enforcement weakness in DevTools. The vulnerability requires high attack complexity (CVSS AC:H) but no user interaction, enabling complete compromise of confidentiality, integrity, and availability if successfully exploited. Vendor patch released in Chrome 148.0.7778.96 per official Google Chrome stable channel update. Despite CVSS 8.1 (High), Chromium assigns Low security severity, suggesting limited real-world exploitability or significant attack prerequisites. No active exploitation (not in CISA KEV) or public exploit code identified at time of analysis.
Remote code execution within Chrome's sandbox allows arbitrary code execution via a malicious HTML page exploiting a use-after-free vulnerability in WebRTC. Affects Chrome versions prior to 148.0.7778.96. Despite high CVSS 8.8 scoring and RCE capability, exploitation requires user interaction (visiting a crafted page) and is confined to Chrome's sandbox, limiting system-level impact. Vendor patch released in Chrome 148.0.7778.96. No evidence of active exploitation (not in CISA KEV) or public POC at time of analysis, though Chromium security team rated this as Low severity internally, suggesting limited real-world exploitability despite the technical impact.
Privilege escalation in Google Chrome's Cast component (versions prior to 148.0.7778.96) allows remote attackers to elevate from renderer to higher-privilege browser process via specially crafted HTML page after initial renderer compromise. Despite 7.5 CVSS score, Chromium security team rates this as Low severity, indicating limited real-world impact. Vendor patch released in version 148.0.7778.96. No public exploit identified at time of analysis.
Remote code execution in Google Chrome on macOS versions prior to 148.0.7778.96 enables attackers to execute arbitrary code within the browser's sandbox through a malicious HTML page exploiting a use-after-free vulnerability in the Audio subsystem. The vulnerability requires user interaction (visiting a crafted webpage) but no authentication, with CVSS 8.8 rating reflecting high impact across confidentiality, integrity, and availability. Google has released patches in Chrome 148.0.7778.96; no active exploitation (KEV) or public POC has been identified at time of analysis, though the technical details are publicly accessible via Chromium issue tracker 495779613.
Sandbox escape in Google Chrome prior to 148.0.7778.96 on Linux, Mac, and ChromeOS allows remote attackers who have already compromised the renderer process to break out of Chrome's sandbox via a crafted HTML page exploiting a use-after-free vulnerability in the printing subsystem. Despite the 8.3 CVSS score, Chromium rates this Low severity because exploitation requires a two-stage attack chain (initial renderer compromise followed by sandbox escape). Vendor patch released as Chrome 148.0.7778.96. No evidence of active exploitation or public POC identified at time of analysis.
Remote code execution affects ChromeDriver in Google Chrome versions prior to 148.0.7778.96 on Windows platforms. Exploitation requires user interaction with a malicious HTML page, enabling remote attackers to achieve arbitrary code execution with high impact to confidentiality, integrity, and availability. Vendor-released patch available (version 148.0.7778.96). No active exploitation confirmed in CISA KEV at time of analysis, though CVSS base score of 8.8 reflects significant potential impact if users visit attacker-controlled content.
Local privilege escalation in Google Chrome's macOS Updater component allows attackers to gain OS-level administrative privileges through malicious files. The flaw affects Chrome versions prior to 148.0.7778.96 on macOS and requires user interaction to exploit. Google has released Chrome 148.0.7778.96 to address this vulnerability. Despite the 7.8 CVSS score, Google rates this as Low severity, reflecting the local attack vector and user interaction requirement that significantly constrain real-world exploitation scenarios.
Remote code execution within Chrome's sandbox affects all versions prior to 148.0.7778.96 through an out-of-bounds read vulnerability in the AdFilter component. Attackers can execute arbitrary code by delivering a specially crafted HTML page, requiring only that a user visit the malicious page. Chrome has released version 148.0.7778.96 to address this vulnerability. No evidence of active exploitation (not in CISA KEV) or public proof-of-concept code at time of analysis, though the vulnerability's network-based attack vector and low complexity make it a realistic exploitation target once technical details become public.
Local privilege escalation in Google Chrome Chromoting (prior to 148.0.7778.96) on Windows allows attackers to gain elevated OS-level privileges by tricking users into opening a malicious file. While CVSS scores this as high severity (7.8), real-world risk is tempered by local access and required user interaction (CVSS: AV:L/UI:R). Vendor patch available in version 148.0.7778.96 released May 2026. No active exploitation (CISA KEV) or public exploit code identified at time of analysis.
Remote code execution in Google Chrome versions prior to 148.0.7778.96 on Linux and ChromeOS allows attackers to execute arbitrary code when users perform specific UI gestures on a malicious webpage. The vulnerability stems from insufficient input validation in Chrome's UI layer (CWE-20). Vendor patch available in Chrome 148.0.7778.96. No public exploit identified at time of analysis, though CVSS 8.8 reflects high impact across confidentiality, integrity, and availability.
Remote code execution in Google Chrome prior to 148.0.7778.96 through a use-after-free vulnerability in the UI component. Attackers who have already compromised the renderer process can escape sandbox restrictions and execute arbitrary code by delivering a specially crafted HTML page requiring user interaction. Google has released patch version 148.0.7778.96. No active exploitation confirmed in CISA KEV at time of analysis, though the vulnerability requires prior renderer compromise which increases attack complexity beyond the CVSS AC:L rating suggests.
Local privilege escalation in Google Chrome's Windows updater component allows unprivileged users to gain SYSTEM-level access by exploiting insufficient input validation when the updater processes a specially crafted malicious file. Affects all Chrome versions on Windows prior to 148.0.7778.96. Google has released a patched version (148.0.7778.96). No active exploitation confirmed by CISA KEV at time of analysis, though the local attack vector and medium severity rating suggest potential for targeted attacks in enterprise environments where Chrome auto-update may be delayed.
Remote code execution in Google Chrome's WebRTC implementation (versions prior to 148.0.7778.96) allows attackers to execute arbitrary code within the browser sandbox through a malicious HTML page exploiting type confusion in WebRTC. Patch available via Chrome 148.0.7778.96. Requires user interaction (visiting crafted page) but no authentication. CVSS 8.8 reflects high impact across confidentiality, integrity, and availability within sandbox constraints. No confirmed active exploitation or public POC identified at time of analysis.
Remote code execution in Google Chrome's WebRTC component (versions prior to 148.0.7778.96) allows attackers to execute arbitrary code within the browser's sandbox by exploiting a use-after-free memory corruption vulnerability via a malicious HTML page. While sandboxed, successful exploitation achieves high confidentiality, integrity, and availability impact within the renderer process. EPSS data unavailable; not listed in CISA KEV, indicating no confirmed widespread exploitation at time of analysis. Vendor patch released as Chrome 148.0.7778.96.
Sandbox escape in Google Chrome (Linux and ChromeOS) prior to 148.0.7778.179 allows a remote attacker who has already compromised the renderer process to break out via a crafted video file processed by the GFX component. The flaw is a type confusion (CWE-843) rated High severity by Chromium, with no public exploit identified at time of analysis and SSVC indicating exploitation has not been observed. It requires user interaction and chained exploitation of a prior renderer compromise, which raises the bar despite the High CVSS of 7.5.
Remote code execution in Google Chrome versions prior to 148.0.7778.179 stems from a use-after-free condition in the QUIC networking stack, allowing remote attackers to execute arbitrary code within the browser sandbox via malicious network traffic. Exploitation requires user interaction (visiting a malicious site or processing attacker-controlled QUIC traffic), and no public exploit has been identified at time of analysis. Chromium rates this as High severity, and a vendor patch is available.
Remote code execution in Google Chrome on Windows prior to version 148.0.7778.179 stems from a use-after-free condition in the GPU component, enabling a remote attacker to run arbitrary code within the renderer sandbox after the victim loads a crafted HTML page. Google has rated the issue High severity and shipped a fix; no public exploit identified at time of analysis and SSVC indicates exploitation status 'none' despite total technical impact.
Remote code execution in Google Chrome on Linux before 148.0.7778.179 stems from a use-after-free flaw in the WebRTC component, allowing a remote attacker who lures a victim to a crafted HTML page to execute arbitrary code in the renderer process. Chromium rates the severity as Critical and a vendor patch is available, though there is no public exploit identified at time of analysis and SSVC indicates no observed exploitation. The CVSS 8.8 score reflects high impact across confidentiality, integrity, and availability with required user interaction (visiting a page).
Sandbox escape in Mozilla Firefox and Firefox Focus for Android lets a malicious web page break out of the content-process sandbox after luring a victim to attacker-controlled content, gaining full confidentiality, integrity, and availability impact on the affected process. Mozilla addressed it in Firefox 151 (advisory MFSA2026-46); there is no public exploit identified at time of analysis, and EPSS rates near-term exploitation at just 0.05% (16th percentile). CISA SSVC records exploitation status as none with a total technical impact, indicating a serious-but-not-yet-exploited browser flaw.
Arbitrary directory deletion in CloakBrowser's cloakserve CDP multiplexer (pip package cloakbrowser <= 0.3.27) allows unauthenticated network attackers to delete directories accessible to the service user by supplying path traversal sequences in the fingerprint query parameter. The service binds to 0.0.0.0 by default, dramatically widening exposure, and no public exploit identified at time of analysis though the vulnerability is trivially reproducible from the published advisory.
Remote code execution in Microsoft Edge (Chromium-based) versions prior to 148.0.3967.70 allows attackers to execute arbitrary code on victim systems when a user is lured to a malicious webpage. The vulnerability stems from improper input validation (CWE-20) and carries a CVSS 3.1 score of 8.8 with high impact across confidentiality, integrity, and availability. No public exploit identified at time of analysis, and the vulnerability is not currently listed in CISA KEV.
Rate limiter bypass in better-auth versions < 1.4.17 allows attackers to defeat authentication attempt limits by rotating through IPv6 addresses within their allocated /64 prefix or using different textual representations of the same address. The vulnerability affects authentication endpoints including sign-in, sign-up, and password reset when serving IPv6 clients, which includes most cloud providers by default. No public exploit identified at time of analysis.
Remote code execution in Google Cloud Application Integration allows unauthenticated attackers to access exposed internal API endpoints and execute arbitrary code. The vulnerability stems from improper access controls on internal APIs that were inadvertently exposed to external networks. With a CVSS 4.0 score of 10.0, this represents a critical risk allowing both information disclosure and full system compromise without authentication.
URL parser mismatch in Open WebUI allows authenticated users to bypass SSRF protections and access internal network resources. The validate_url function uses Python's urlparse library to extract hostnames for validation, while the requests library handles actual HTTP requests. These libraries disagree on parsing URLs containing backslash characters (e.g., http://127.0.0.1:6666\@1.1.1.1), allowing attackers to craft URLs that pass validation as external addresses but resolve to internal hosts. Exploitation requires low-privilege authentication but no user interaction, enabling access to cloud metadata endpoints and internal services. Fixed in version 0.9.5 per GitHub advisory GHSA-8w7q-q5jp-jvgx.
Arbitrary code execution in Google Chrome on macOS (versions prior to 148.0.7778.168) stems from a use-after-free in the browser's Extensions subsystem, allowing an attacker who convinces a user to install a malicious extension to run arbitrary code through a crafted Chrome extension. Chromium rates the severity Medium, but the CVSS 3.1 base score is 8.8 (High) because the flaw yields full confidentiality, integrity, and availability impact once triggered. There is no public exploit identified at time of analysis, it is not listed in CISA KEV, and the EPSS probability is negligible (0.02%, 5th percentile), indicating no observed real-world exploitation to date.
Out-of-bounds memory read in Google Chrome on iOS versions before 148.0.7778.168 enables remote attackers to access sensitive memory contents through a compromised renderer process. The vulnerability requires user interaction to visit a malicious webpage and exploitation of a prior renderer compromise. With EPSS at 0.03% and no known active exploitation, this represents a moderate risk primarily in targeted attack chains.
Arbitrary code execution in Google Chrome's GPU component (prior to 148.0.7778.168) lets a remote attacker run code inside the renderer/GPU sandbox by luring a victim to a crafted HTML page. The flaw is a CWE-416 use-after-free that Chromium rates Medium, though CVSS scores it 8.8 (High). No public exploit is identified and there is no CISA KEV listing; EPSS is very low at 0.08%, indicating no observed exploitation activity at time of analysis.
Sandbox escape in Google Chrome's Mojo IPC layer allows a remote attacker who lures a victim to a crafted HTML page to exploit a use-after-free (CWE-416) and potentially break out of the renderer sandbox on versions prior to 148.0.7778.168. Google fixed the flaw in the stable desktop channel (148.0.7778.168), and there is no public exploit identified at time of analysis (EPSS 0.07%, not in CISA KEV). Note a signal conflict: the CVSS base score is 9.6 (Critical) while Chromium's own triage rated the severity only Medium, so real-world exploitability is likely lower than the raw score implies.
Remote code execution in Google Chrome before 148.0.7778.168 stems from an integer overflow in the browser's font handling code, allowing a remote attacker who lures a victim to a crafted HTML page to execute arbitrary code - though notably constrained to run inside the renderer sandbox rather than achieving full host compromise. The flaw carries a CVSS of 8.8 but is rated Medium by Chromium's own severity scale, reflecting the sandbox containment. There is no public exploit identified at time of analysis, EPSS is very low (0.08%), and CISA SSVC records exploitation status as none.
Sandbox escape in Google Chrome desktop before 148.0.7778.168 lets an attacker who already controls a compromised renderer process leverage a use-after-free in the browser UI component to break out of the renderer sandbox via a crafted HTML page. This is the second-stage bug in a typical browser exploit chain and Chromium rates it Medium severity; there is no public exploit identified at time of analysis and EPSS estimates only a 0.07% exploitation probability. Google has released a fixed stable-channel build, and Red Hat and SUSE have picked it up for their Chromium packages.
Sandbox escape in Google Chrome on Windows before 148.0.7778.168 stems from a use-after-free in the browser's Core component, allowing an attacker who has already compromised the renderer process to break out of the sandbox and potentially execute code in the more privileged browser process via a crafted HTML page. Google rates it Medium severity internally, though the assigned CVSS is 8.3 due to the scope change and total impact. There is no public exploit identified at time of analysis, EPSS is very low (0.07%), and SSVC records exploitation status as none.
Sandbox escape in Google Chrome on Windows (versions prior to 148.0.7778.168) can be triggered by an integer overflow in the codecs component when the browser processes a crafted video file, allowing a remote attacker to potentially break out of the renderer sandbox. Chromium rates the security severity as Medium; the assigned CVSS is 8.3 due to high complexity but scope change and full CIA impact. There is no public exploit identified at time of analysis, EPSS is very low (0.07%), and CISA SSVC lists exploitation status as none, indicating no observed attacks.
Sandbox escape in Google Chrome for Android before 148.0.7778.168 lets an attacker who has already compromised the renderer process break out of the sandbox through insufficient policy enforcement in the GPU component, escalating a contained renderer bug into fuller device compromise via a crafted HTML page. Rated Medium by Chromium but scored CVSS 8.3 by NVD due to the scope change and total technical impact. There is no public exploit identified at time of analysis and EPSS probability is low (0.09%).
Sandbox escape in Google Chrome for macOS (versions prior to 148.0.7778.168) stems from an out-of-bounds write in the browser's media codec handling, letting a remote unauthenticated attacker who lures a victim into opening a crafted video file corrupt memory and potentially break out of the renderer sandbox. The flaw carries a CVSS 8.3 rating driven by a scope-changing, full-triad impact, though Chromium internally rated the security severity only Medium. There is no public exploit identified at time of analysis, EPSS is very low at 0.07%, and CISA SSVC records exploitation as none.
Privilege escalation in Google Chrome desktop before 148.0.7778.168 lets an attacker who has already compromised the renderer process abuse a use-after-free in the Accessibility component to break out of the sandbox and gain elevated privileges via a crafted HTML page. Rated High by Chromium and scored CVSS 7.5, it is a second-stage exploit primitive rather than a standalone entry point. There is no public exploit identified at time of analysis, it is not in CISA KEV, and EPSS is very low at 0.07%.
Remote code execution in Google Chrome on Windows before 148.0.7778.168 stems from a use-after-free in the GTK component, letting a remote attacker run arbitrary code when a victim opens a crafted HTML page. Google rates the Chromium severity High and has shipped a fixed Stable channel build; no public exploit is identified at time of analysis, EPSS risk is low (0.08%), and CISA SSVC marks exploitation status as none.
Remote code execution in Google Chrome desktop before 148.0.7778.168 stems from a use-after-free (CWE-416) in the Downloads component, letting a remote attacker who lures a victim into performing specific UI interactions run arbitrary code via a crafted HTML page. Rated High by Chromium and CVSS 8.8, the flaw was reported internally by the Chrome team and is patched in the Stable channel update. No public exploit identified at time of analysis, and EPSS is low at 0.08%.
Remote code execution in Google Chrome's Media component (versions prior to 148.0.7778.168) allows a remote attacker to run arbitrary code within the renderer sandbox when a victim opens a crafted HTML page. Rated High by Chromium and CVSS 8.8, the flaw is a use-after-free (CWE-416); Google has shipped a fixed Stable channel build. There is no public exploit identified at time of analysis, EPSS is low (0.08%), and CISA SSVC records exploitation as none - though memory-corruption bugs in Chrome's media stack are historically attractive to attackers.
Sandbox escape in Google Chrome's Media component (versions prior to 148.0.7778.168) allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page. This is an out-of-bounds write (CWE-787) rated High by Chromium and CVSS 8.3, but exploitation is gated on chaining from a prior renderer compromise, and there is no public exploit identified at time of analysis. EPSS is very low (0.07%, 21st percentile) and CISA SSVC lists exploitation status as none.
Privilege escalation in Google Chrome's Passwords component on Windows (versions prior to 148.0.7778.168) lets a remote attacker who has already compromised the renderer process escape its privilege boundary via a crafted HTML page. Rated High by Chromium and CVSS 7.5, it is a second-stage bug used to extend an existing renderer foothold rather than an initial-access vector. There is no public exploit identified at time of analysis, and the EPSS score is very low (0.07%, 20th percentile), consistent with SSVC marking exploitation as none.
Remote code execution in Google Chrome's Media component (versions prior to 148.0.7778.168) allows a remote attacker to run arbitrary code within the renderer sandbox when a victim visits a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium with a CVSS of 8.8; no public exploit identified at time of analysis, and SSVC records no observed exploitation with a low EPSS of 0.08%. Exploitation requires user interaction (visiting a malicious page) and, because code runs inside the sandbox, a separate sandbox-escape bug would be needed for full host compromise.
Sandbox escape in Google Chrome on Windows before 148.0.7778.168 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox and gain code execution at higher privilege on the host. The flaw is a use-after-free (CWE-416) in Chrome's Core component, triggered via a crafted HTML page; Google rates it High severity. No public exploit has been identified at time of analysis, and EPSS is very low (0.07%, 21st percentile), consistent with an internally reported bug not yet weaponized.
Remote code execution in Google Chrome's V8 JavaScript engine before 148.0.7778.168 allows a remote attacker to run arbitrary code within the renderer sandbox when a victim visits a crafted HTML page. Rated High by Chromium and CVSS 8.8, the flaw is a type confusion bug and requires user interaction (visiting a malicious page); no public exploit identified at time of analysis and EPSS probability is very low (0.08%). Google has shipped a patched Stable channel release.
Sandbox escape in the GPU process of Google Chrome (and ChromeOS) on Linux, fixed in 148.0.7778.168, lets an attacker who has ALREADY compromised the renderer process break out of the browser sandbox via a crafted HTML page. This is a second-stage bug rather than an initial-access flaw, so it must be chained with a separate renderer exploit to be useful. There is no public exploit identified at time of analysis, EPSS is very low (0.07%), and CISA SSVC lists exploitation as none, though the technical impact if exploited is total.
Sandbox escape in Google Chrome desktop before 148.0.7778.168 lets a remote attacker who has already compromised the renderer process break out of the sandbox by triggering a use-after-free in the Accessibility component via a crafted HTML page. Rated High by Chromium and scored CVSS 8.3, it is a second-stage exploit primitive rather than a standalone remote break-in. No public exploit identified at time of analysis, and EPSS is very low (0.07%, 21st percentile), consistent with the SSVC exploitation status of 'none'.
Sandboxed remote code execution in Google Chrome desktop versions prior to 148.0.7778.168 allows a remote attacker to run arbitrary code within the browser's renderer sandbox by luring a victim to a crafted HTML page. The flaw stems from an integer overflow in Chrome's XML handling and is rated High by Chromium; it requires user interaction (visiting a malicious page) and carries no public exploit identified at time of analysis, with a low EPSS of 0.08%.
Heap buffer overflow in Google Chrome's WebML component on Windows lets a remote attacker trigger heap corruption-and potentially achieve code execution in the renderer-by luring a victim to a crafted HTML page in a version prior to 148.0.7778.168. Chromium rates the flaw High severity, and a vendor patch is available. There is no public exploit identified at time of analysis, and EPSS exploitation probability is low (0.06%).
Sandbox escape in Google Chrome on Windows before 148.0.7778.168 lets an attacker who already controls a compromised renderer process break out of the browser sandbox by triggering a use-after-free in the Network component via a crafted HTML page. It is a second-stage bug that chains onto a prior renderer compromise rather than a standalone entry point, carrying High Chromium severity and CVSS 8.3. There is no public exploit identified at time of analysis, and EPSS is very low at 0.07% (21st percentile).
Remote code execution in Google Chrome desktop prior to 148.0.7778.168 stems from a heap buffer overflow in the browser's media Codecs component, allowing a remote attacker to run arbitrary code within the renderer sandbox when a victim processes a crafted video file. Reported internally by the Chrome team and rated High severity by Chromium, it carries CVSS 8.8 but requires user interaction (UI:R). There is no public exploit identified at time of analysis, and EPSS is low at 0.07%.
Remote code execution in Google Chrome's Downloads component before version 148.0.7778.168 allows a remote attacker to execute arbitrary code when a victim visits or interacts with a crafted HTML page. Chromium rates this High severity, and the CVSS 8.8 vector confirms the flaw is network-reachable and unauthenticated but requires user interaction (UI:R). There is no public exploit identified at time of analysis, and EPSS is low (0.08%), consistent with CISA SSVC marking exploitation status as none.
Out-of-bounds write in the WebRTC component of Google Chrome before 148.0.7778.168 lets a remote attacker achieve arbitrary code execution inside the renderer sandbox when a victim opens a crafted HTML page. Rated High by Chromium and CVSS 8.8, it requires user interaction (visiting a page) but no authentication. There is no public exploit identified at time of analysis, EPSS is low (0.07%), and CISA SSVC lists exploitation as none, indicating no observed in-the-wild activity yet.
Sandbox escape in Google Chrome for macOS before 148.0.7778.168 stems from a heap buffer overflow in the ANGLE graphics abstraction layer, letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox and cross into a higher-privilege context. Google rates the Chromium severity High and a fixed build is available, but there is no public exploit identified at time of analysis. EPSS is very low (0.06%) and CISA SSVC records exploitation status as none, indicating no observed attacks.
Out-of-bounds write in Google Chrome's WebAudio component (versions prior to 148.0.7778.168) lets a remote attacker achieve arbitrary code execution within the renderer sandbox when a victim opens a crafted HTML page. Google rates the Chromium severity as High and has shipped a fixed Stable channel build; there is no public exploit identified at time of analysis and the EPSS score is very low (0.07%). Because execution is confined to the sandbox, real-world impact typically requires chaining a separate sandbox-escape bug.
Renderer-sandboxed remote code execution in Google Chrome's Fonts component (versions prior to 148.0.7778.168) lets a remote attacker run arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page. Rated High by Chromium and CVSS 8.8, the flaw is a CWE-787 out-of-bounds write reported internally by the Chrome team. There is no public exploit identified at time of analysis, and EPSS is very low (0.04%, 11th percentile), consistent with the CISA SSVC assessment of no known exploitation.
Sandbox escape in Google Chrome desktop versions prior to 148.0.7778.168 lets an attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page, abusing a use-after-free in the Mojo IPC layer. Rated High by Chromium and CVSS 8.3, it enables a scope change from the low-privilege renderer to the more-privileged browser process. There is no public exploit identified at time of analysis, it is not in CISA KEV, and EPSS is very low (0.07%), indicating no observed exploitation.
Remote code execution in Google Chrome on macOS prior to 148.0.7778.168 stems from a use-after-free in the Downloads component, letting a remote attacker who lures a victim to a crafted HTML page corrupt memory and execute arbitrary code in the browser process. Rated Critical by Chromium and CVSS 8.8, it requires user interaction (visiting the page) but no authentication. No public exploit identified at time of analysis, and EPSS is low (0.08%), consistent with SSVC exploitation status of 'none'.
Remote code execution in Google Chrome's Tab Groups component (versions prior to 148.0.7778.168) stems from a use-after-free (CWE-416) that a remote attacker can trigger via malicious network traffic, per Google's Chrome Releases advisory rated Chromium-Critical. Successful exploitation yields arbitrary code execution in the affected browser process with total technical impact. There is no public exploit identified at time of analysis, EPSS is very low (0.03%, 10th percentile), and CISA SSVC records exploitation status as none.
Sandbox escape in Google Chrome's Payments component before 148.0.7778.168 lets a remote attacker who lures a victim to a crafted HTML page break out of the renderer sandbox by winning a race condition. Rated Critical by Chromium and scored CVSS 8.3, it carries a scope-changing high-impact profile, though EPSS is a low 0.06% and there is no public exploit identified at time of analysis. A vendor patch is available and the flaw is not listed in CISA KEV.
Out-of-bounds memory write in Google Chrome's ANGLE graphics abstraction layer on Windows before 148.0.7778.168 lets a remote attacker corrupt memory by luring a victim to a crafted HTML page, potentially leading to renderer-process code execution. Rated Critical by Chromium and scored CVSS 8.8, it requires user interaction (visiting a page) but no authentication. Currently there is no public exploit identified and the SSVC exploitation status is 'none', though the very low EPSS (0.07%) reflects newness rather than confirmed safety.
Renderer-side arbitrary code execution in Google Chrome desktop before 148.0.7778.168 stems from a use-after-free in the Blink rendering engine, letting a remote attacker who lures a victim to a crafted HTML page run code within the browser's renderer sandbox. Chromium rates the flaw Critical severity; however, exploitation still requires the user to open a malicious page (UI:R), the code executes inside the sandbox (scope unchanged), and there is no public exploit identified at time of analysis. EPSS is low (0.08%, 23rd percentile) and CISA SSVC records exploitation as 'none', so this is a high-severity but not yet actively exploited issue.
Remote code execution in Google Chrome on macOS (versions prior to 148.0.7778.168) stems from an object lifecycle flaw in the WebShare API, allowing a remote attacker to run arbitrary code within the browser process after luring a victim to a crafted HTML page and getting them to perform specific UI gestures. Rated Critical by Chromium and reported internally by the Chrome team, a vendor patch is available; there is no public exploit identified at time of analysis, and the EPSS probability is very low (0.07%). CISA SSVC currently rates exploitation as none with total technical impact.
Sandbox escape in Google Chrome desktop before 148.0.7778.168 stems from a use-after-free in the WebHID implementation, letting a remote attacker who lures a victim into specific UI gestures on a crafted HTML page corrupt memory and potentially break out of the renderer sandbox. Chromium rates the severity Critical, though no public exploit is identified and EPSS is very low (0.07%). Exploitation requires user interaction and is not automatable, indicating a high-skill rather than mass-exploited threat.
Sandbox escape in Google Chrome's Aura windowing subsystem (versions prior to 148.0.7778.168) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page. Rated Critical by Chromium and CVSS 8.3, it is a use-after-free (CWE-416) that serves as the second stage of an exploit chain rather than an initial entry point. There is no public exploit identified at time of analysis, and EPSS is very low (0.07%), consistent with a patched, chain-dependent bug.
Sandbox escape in Google Chrome for Android before 148.0.7778.168 lets an attacker who has already compromised the renderer process leverage a use-after-free in the Input component to break out of the sandbox via a crafted HTML page. Rated Critical by Chromium and CVSS 8.3, this is a second-stage bug requiring an existing renderer compromise rather than a standalone remote exploit. EPSS is very low (0.07%) and there is no public exploit identified at time of analysis; SSVC records no observed exploitation.
Sandbox escape in Google Chrome desktop before 148.0.7778.168 stems from a use-after-free in the FileSystem component, letting a remote attacker who serves a crafted HTML page and coaxes the victim into specific UI gestures corrupt memory and break out of the renderer sandbox. Chromium rates it Critical, and the CVSS:3.1 8.3 score reflects a scope change (S:C) with full confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; EPSS is low at 0.07% (21st percentile).
Sandbox escape in Google Chrome's UI layer, driven by a use-after-free (CWE-416) reachable before version 148.0.7778.168, lets a remote attacker who lures a victim to a crafted HTML page break out of the renderer sandbox. Google rates the Chromium severity Critical and has shipped a fix; there is no public exploit identified at time of analysis, and EPSS is low (0.07%, 21st percentile), so this is a high-severity but not-yet-exploited memory-safety bug. SSVC lists exploitation as none with total technical impact.
Out-of-bounds memory write in Google Chrome's Skia graphics library on Windows (versions prior to 148.0.7778.168) lets an attacker who has already compromised the renderer process trigger an integer overflow via a crafted HTML page, corrupting memory in a Critical-rated flaw. It is a second-stage primitive used to widen an existing renderer foothold, not a standalone remote-entry bug. No public exploit identified at time of analysis, and EPSS is very low (0.07%, 21st percentile), consistent with the SSVC 'Exploitation: none' assessment.
Remote code execution in Google Chrome's WebML component (versions prior to 148.0.7778.168) allows a remote attacker to run arbitrary code within the browser's renderer sandbox by luring a victim to a crafted HTML page. Chromium rates this a Critical severity heap buffer overflow (CWE-122), though the CVSS base is 8.8 because code execution is contained inside the sandbox rather than achieving a full host compromise. There is no public exploit identified at time of analysis, and the EPSS score is very low (0.06%, 20th percentile), consistent with SSVC showing no observed exploitation.
Authentication bypass in the Burst Statistics WordPress plugin versions 3.4.0 through 3.4.1.1 allows unauthenticated remote attackers to impersonate any administrator whose username they know by supplying an arbitrary Basic Authentication password. The flaw resides in flawed return-value handling within the `is_mainwp_authenticated()` function used to validate application passwords from the Authorization header, enabling privilege escalation per request. No public exploit identified at time of analysis, and EPSS is low (0.26%), but the CVSS 9.8 score and SSVC 'total' technical impact mark it as a high-severity authentication bypass worth prioritizing.
Broken access control in the MonsterInsights Google Analytics plugin for WordPress (versions up to and including 10.1.2) lets any authenticated user with Subscriber-level access or higher call the unprotected get_ads_access_token() and reset_experience() functions, exposing live Google OAuth access tokens and letting them reset the plugin's Google Ads integration. The disclosed OAuth tokens can be abused to access the linked Google Ads/Analytics account outside WordPress, while the reset function disrupts the site's advertising integration. No public exploit identified at time of analysis, and EPSS is very low (0.03%), consistent with SSVC exploitation status of 'none'.
Session persistence after credential change in SillyTavern before 1.18.0 lets an attacker holding a stolen session cookie retain full account access even after the victim resets their password. Because sessions are stateless and stored entirely in a signed client-side cookie with a default 400-day lifespan, the change-password and account-recovery endpoints update the password hash but never revoke outstanding tokens, defeating the standard remediation for cookie theft. No active exploitation is recorded (not in CISA KEV) and EPSS is very low at 0.02%, but public proof-of-concept reproduction steps are documented in the GHSA advisory.
Information disclosure in Microsoft Edge (Chromium-based) before 148.0.3967.55 allows a remote, unauthenticated attacker to read data they should not have access to by luring a victim into interacting with malicious web content. Rooted in external control of a file name or path (CWE-73) with a changed CVSS scope, it can leak sensitive information across security boundaries. Reported by Microsoft with a vendor patch available; no public exploit identified at time of analysis and EPSS exploitation probability is very low (0.05%).
Full administrative database takeover in Google Cloud AlloyDB for PostgreSQL affected clusters provisioned via Terraform or the REST API before 2025-11-03, where those provisioning paths applied an insecure default password. A remote attacker with network reachability to such a cluster could authenticate as a privileged account and gain complete control of the database. There is no public exploit identified at time of analysis, and the EPSS probability is very low (0.04%, 12th percentile), consistent with the SSVC assessment of no observed exploitation.
Remote unauthenticated attackers can decrypt user credentials and hijack IoT device sessions in Meari SDK-based mobile applications (CloudEdge, Arenti, white-label apps) by exploiting hardcoded cryptographic keys shared across all installations. The SDK embeds API signing secrets, password-transport encryption keys, and service access tokens in application binaries, enabling adversaries to intercept and decrypt account credentials in transit, forge authenticated API requests, and potentially access cloud services without user authentication. No public exploit code identified at time of analysis, but EPSS scoring and exploitation complexity are low given the static nature of hardcoded secrets.
Decompression bomb safeguards in urllib3 2.6.0 can be bypassed during streaming API operations, causing excessive CPU and memory consumption on client systems. Applications using urllib3 versions 2.6.0 through 2.6.x that stream Brotli-compressed responses with multiple read() calls, or invoke drain_conn() after partial decompression, may decompress entire payloads instead of requested chunks. This allows malicious servers to trigger resource exhaustion attacks against urllib3 clients. Vendor-released patch (version 2.7.0) confirmed by GitHub advisory GHSA-mf9v-mfxr-j63j. No public exploit identified at time of analysis, but exploitation requires only a malicious HTTP server delivering compressed responses - a low-complexity attack scenario.
Server-side request forgery in Gotenberg's Chromium URL-to-PDF endpoint allows unauthenticated remote attackers to exfiltrate cloud credentials and access internal services. The primary `/forms/chromium/convert/url` endpoint ships with no default deny-list for HTTP/HTTPS targets - only blocking file:// URIs - enabling direct access to AWS/GCP/Azure metadata endpoints at 169.254.169.254, RFC 1918 private networks, and localhost services. Even when administrators configure custom deny-lists, attackers bypass validation via HTTP 302 redirects, as Chromium follows redirects without re-validating destinations. Vendor-confirmed public exploit code exists (PoC in GHSA-chwh-f6gm-r836). Patch available in version 8.32.0.
Cross-origin WebSocket hijacking in the Cline `kanban` server (npm `kanban`, shipped via the `cline` CLI ≤ 2.13.0) lets any website a developer visits silently connect to the loopback server on 127.0.0.1:3484 and leak workspace paths, task content, git branches, and AI-agent chat, then inject prompts into a running agent's terminal for remote code execution and kill active tasks. Because browsers do not apply CORS to WebSocket handshakes and the three endpoints perform no Origin validation or authentication (CWE-306), exploitation needs only that the victim run kanban and browse to an attacker page. A full interactive proof-of-concept exists (publicly available exploit code exists); it is not listed in CISA KEV and EPSS is very low at 0.02%, indicating no observed mass exploitation to date.
Remote code execution in SiYuan's Electron renderer occurs when users hover over search results, file tree items, or attribute view elements containing URL-encoded XSS payloads in document titles or metadata. The vulnerability chains a URL-decoding step (decodeURIComponent) with unsafe innerHTML assignment in tooltip rendering, bypassing the escapeAriaLabel sanitizer that only handles HTML entities but ignores %XX URL escapes. Because SiYuan's renderer runs with nodeIntegration:true and contextIsolation:false, the XSS escalates to arbitrary code execution via require('child_process'). Exploitation requires user interaction (hovering) but no authentication, and malicious payloads survive .sy.zip export/import and sync replication, enabling supply-chain and shared-workspace attacks. No public exploit code identified at time of analysis, though detailed proof-of-concept is published in the GitHub advisory.
Server-side request forgery in n8n-mcp versions 2.18.7 through 2.50.1 allows authenticated attackers with MCP session access to bypass SSRF protections and send HTTP requests to cloud metadata endpoints and internal services, with response bodies returned directly to the attacker. Multi-tenant HTTP deployments are critically exposed: any tenant sharing an AUTH_TOKEN can exfiltrate AWS IAM, GCP service account, or Azure managed identity credentials from the operator's cloud metadata service (169.254.169.254 and related endpoints). Single-tenant and stdio deployments remain vulnerable via indirect prompt injection attacks that manipulate LLM tool calls. Vendor-released patch: n8n-mcp version 2.50.2. No CVSS score assigned; no public exploit code identified at time of analysis, though the advisory contains sufficient technical detail for proof-of-concept development.
Remote code execution in SiYuan's Electron desktop application allows authenticated attackers (or browser extensions on localhost) to inject malicious JavaScript through unescaped Attribute View names, escalating from stored XSS to arbitrary system command execution. The Go kernel backend stores AV names without HTML escaping, then embeds them via string replacement into HTML templates pushed over WebSocket. Three TypeScript renderer paths (render.ts, Title.ts, transaction.ts) consume this data using innerHTML/outerHTML without sanitization. Because the Electron main window runs with nodeIntegration:true and contextIsolation:false, script injection grants full Node.js API access—enabling attackers to spawn child processes (calc.exe/xcalc demonstrated in PoC), exfiltrate SSH keys, install backdoors, or pivot to cloud credentials. Payloads persist in JSON files under data/storage/av/, replicate across all sync transports (S3/WebDAV/cloud), survive .sy.zip export-import, and trigger for any user role (Administrator/Editor/Reader/Visitor) opening a document bound to the poisoned database view. CVSS 9.4 (Network/Low/None/High Confidentiality-Integrity-Availability + Scope Changed) reflects worst-case remote network vector, though the primary realistic attack path is via installed browser extensions (chrome-extension:// Origin explicitly allowlisted in session.go:277) calling the /api/transactions endpoint as an auto-granted admin on default installations with no Access Authorization Code. GitHub advisory GHSA-2h64-c999-c9r6 confirms patch available in kernel commit 0.0.0-20260512140701-d7b77d945e0d. No public exploit code identified at time of analysis, but detailed reproduction steps with curl payloads and Electron DevTools inspection are published in the advisory.
Use-after-free (UAF) in Linux kernel Bluetooth subsystem allows adjacent network attackers to trigger memory corruption via malformed LE Read Features Complete responses. The vulnerability occurs when hci_conn is freed before le_read_features_complete callback executes but after hci_le_read_remote_features_sync initiates, causing atomic operations on freed memory during hci_conn_drop. Active exploitation status not confirmed (no CISA KEV listing). EPSS score of 0.02% (5th percentile) indicates very low observed exploitation probability. Upstream patches committed to stable kernel branches 6.19.12+ and 7.0+.
Remote unauthenticated attackers can access Google Secrets Manager credentials from unintended GCP projects via crafted requests to Spring Cloud Config servers using Google Secrets Manager as a backend. VMware confirmed this high-severity information disclosure vulnerability (CVSS 7.5) affecting all 3.1.x through 5.0.x versions. No CISA KEV listing or public exploit code identified at time of analysis, but the network-accessible attack vector with no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N) indicates straightforward exploitation once attackers identify vulnerable Spring Cloud Config deployments with Google Secrets Manager integration.
Unauthenticated server-side request forgery (SSRF) in Gotenberg 8.30.1 and earlier allows remote attackers to force the server to make HTTP requests to internal/loopback addresses by bypassing default deny-lists with IPv4-mapped IPv6 notation (e.g., http://[::ffff:127.0.0.1]:port). The vulnerability affects both the downloadFrom file-fetching feature and the webhook delivery feature. Attackers can read content from internal HTTP endpoints and trigger state-changing requests against services bound to localhost, exposing internal APIs, cloud metadata endpoints, and admin interfaces. Fix available in version 8.32.0. No public exploit code confirmed outside the GitHub advisory PoC, not listed in CISA KEV, but CVSS 9.4 Critical rating reflects the network-accessible, unauthenticated nature and high confidentiality/integrity impact.
Unauthenticated remote attackers crash Gotenberg 8.x (≤ 8.31.0) by triggering a race condition between webhook goroutine context reuse and Echo framework connection pooling. When webhook middleware spawns an async goroutine holding an `echo.Context` reference, the synchronous handler returns immediately, recycling the context to Echo's `sync.Pool`. Concurrent requests reset the pooled context, causing unchecked type assertions in the still-running webhook goroutine to panic outside any `recover()` scope, terminating the process with exit code 2. Twenty-four webhook requests plus sixty concurrent GET requests demonstrate reliable two-second crash windows. No patch was available at initial disclosure; upstream commit fixes the panic in version 8.32.0. CVSS 7.5 (AV:N/AC:L/PR:N/UI:N) reflects trivial unauthenticated network exploitation producing complete service disruption.
Server-Side Request Forgery in Gotenberg's LibreOffice conversion endpoint allows remote attackers to make arbitrary HTTP requests from the server to internal networks and cloud metadata endpoints. Attackers upload specially crafted Office documents (DOCX, XLSX, PPTX) with embedded external URL references that LibreOffice fetches during PDF conversion, completely bypassing the SSRF protections introduced in v8.31.0. Publicly available exploit code exists with detailed proof-of-concept showing three successful HTTP requests to attacker-controlled servers. The vulnerability enables exfiltration of cloud IAM credentials from metadata services (169.254.169.254), internal service enumeration, and network reconnaissance without authentication. CVSS 8.2 with network vector and no privileges required reflects accurate real-world risk given documented exploitation method and lack of vendor-released patch.
Unauthenticated remote code execution in Gotenberg 8.29.1 allows network attackers to execute arbitrary OS commands via newline injection in PDF metadata keys. The `/forms/pdfengines/metadata/write` endpoint passes user-controlled JSON metadata keys directly to ExifTool without control-character validation. Embedding `\n` in a key splits ExifTool's stdin stream, injecting arbitrary flags including `-if` which evaluates Perl expressions. Attack returns HTTP 200 with valid PDF output, evading basic monitoring. CVSS 9.8 (AV:N/AC:L/PR:N/UI:N) reflects critical network-accessible RCE. No vendor-released patch identified at time of analysis — GitHub advisory GHSA-rqgh-gxv4-6657 confirms the issue but CPE data shows no fixed version. Publicly available exploit code exists in Python and bash with OOB exfiltration. Default Docker image `gotenberg/gotenberg:8` runs the vulnerable process as uid 1001 with root group membership, amplifying post-exploitation impact.
Unauthenticated remote control of the Optoma CinemaX P2 smart projector (firmware TVOS-04.24.010.04.01, Android 8.0.0) is possible through an HTTP API listening on TCP port 2345. Any host on the same network can read 74 configuration endpoints and write settings including power, volume, brightness, display mode, and network protocol toggles - notably enabling TELNET, which can widen the attack surface. No public exploit identified at time of analysis, and EPSS is very low (0.02%), but the flaw requires no credentials and CVSS is rated 9.8.
Unauthenticated remote root access on Optoma CinemaX P2 smart projectors allows network attackers to execute arbitrary code with full system privileges. The device ships with ADB enabled on TCP 5555 without authentication (ro.adb.secure=0) and contains an unrestricted su binary, enabling complete device compromise including WiFi credential theft, malware installation, and data exfiltration. EPSS score (0.02%, 6th percentile) indicates low widespread exploitation probability, though SSVC framework assesses total technical impact. No public exploit code or active exploitation confirmed at time of analysis.
JupyterLab's CommandLinker executes arbitrary commands via single-click social engineering when users open malicious notebooks shared through email, GitHub, or Binder links. Attackers embed deceptive HTML buttons with allowlisted data-commandlinker-* attributes in pre-saved notebook output cells to trigger commands without code execution submission, enabling immediate arbitrary code execution in available kernels, silent file deletion, or resource exhaustion in multi-tenant deployments. The patched version 4.5.7 was released by the JupyterLab team through GitHub advisory GHSA-mqcg-5x36-vfcg. Chromium browser users face expanded terminal access risk through multi-click clipboard permission abuse. Third-party JupyterLab extensions increase attack surface by exposing additional commands to exploitation.
Chrome DevTools Protocol exposure in OpenClaw sandbox browser allows adjacent network attackers to remotely control sandboxed Chrome instances and access sensitive data. The CDP relay binds to 0.0.0.0 without source IP restrictions in versions before 2026.4.10, enabling attackers on the same Docker network to bypass sandbox isolation and execute arbitrary JavaScript in browser contexts. Vendor-released patch available (v2026.4.10); no public exploit identified at time of analysis. CVSS 9.0 reflects adjacent network attack vector with high confidentiality, integrity, and availability impact across virtual and system scopes.
Sandbox escape in Google Chrome prior to 148.0.7778.96 allows remote attackers to break out of Chrome's security sandbox via specially crafted network traffic targeting a policy enforcement weakness in DevTools. The vulnerability requires high attack complexity (CVSS AC:H) but no user interaction, enabling complete compromise of confidentiality, integrity, and availability if successfully exploited. Vendor patch released in Chrome 148.0.7778.96 per official Google Chrome stable channel update. Despite CVSS 8.1 (High), Chromium assigns Low security severity, suggesting limited real-world exploitability or significant attack prerequisites. No active exploitation (not in CISA KEV) or public exploit code identified at time of analysis.
Remote code execution within Chrome's sandbox allows arbitrary code execution via a malicious HTML page exploiting a use-after-free vulnerability in WebRTC. Affects Chrome versions prior to 148.0.7778.96. Despite high CVSS 8.8 scoring and RCE capability, exploitation requires user interaction (visiting a crafted page) and is confined to Chrome's sandbox, limiting system-level impact. Vendor patch released in Chrome 148.0.7778.96. No evidence of active exploitation (not in CISA KEV) or public POC at time of analysis, though Chromium security team rated this as Low severity internally, suggesting limited real-world exploitability despite the technical impact.
Privilege escalation in Google Chrome's Cast component (versions prior to 148.0.7778.96) allows remote attackers to elevate from renderer to higher-privilege browser process via specially crafted HTML page after initial renderer compromise. Despite 7.5 CVSS score, Chromium security team rates this as Low severity, indicating limited real-world impact. Vendor patch released in version 148.0.7778.96. No public exploit identified at time of analysis.
Remote code execution in Google Chrome on macOS versions prior to 148.0.7778.96 enables attackers to execute arbitrary code within the browser's sandbox through a malicious HTML page exploiting a use-after-free vulnerability in the Audio subsystem. The vulnerability requires user interaction (visiting a crafted webpage) but no authentication, with CVSS 8.8 rating reflecting high impact across confidentiality, integrity, and availability. Google has released patches in Chrome 148.0.7778.96; no active exploitation (KEV) or public POC has been identified at time of analysis, though the technical details are publicly accessible via Chromium issue tracker 495779613.
Sandbox escape in Google Chrome prior to 148.0.7778.96 on Linux, Mac, and ChromeOS allows remote attackers who have already compromised the renderer process to break out of Chrome's sandbox via a crafted HTML page exploiting a use-after-free vulnerability in the printing subsystem. Despite the 8.3 CVSS score, Chromium rates this Low severity because exploitation requires a two-stage attack chain (initial renderer compromise followed by sandbox escape). Vendor patch released as Chrome 148.0.7778.96. No evidence of active exploitation or public POC identified at time of analysis.
Remote code execution affects ChromeDriver in Google Chrome versions prior to 148.0.7778.96 on Windows platforms. Exploitation requires user interaction with a malicious HTML page, enabling remote attackers to achieve arbitrary code execution with high impact to confidentiality, integrity, and availability. Vendor-released patch available (version 148.0.7778.96). No active exploitation confirmed in CISA KEV at time of analysis, though CVSS base score of 8.8 reflects significant potential impact if users visit attacker-controlled content.
Local privilege escalation in Google Chrome's macOS Updater component allows attackers to gain OS-level administrative privileges through malicious files. The flaw affects Chrome versions prior to 148.0.7778.96 on macOS and requires user interaction to exploit. Google has released Chrome 148.0.7778.96 to address this vulnerability. Despite the 7.8 CVSS score, Google rates this as Low severity, reflecting the local attack vector and user interaction requirement that significantly constrain real-world exploitation scenarios.
Remote code execution within Chrome's sandbox affects all versions prior to 148.0.7778.96 through an out-of-bounds read vulnerability in the AdFilter component. Attackers can execute arbitrary code by delivering a specially crafted HTML page, requiring only that a user visit the malicious page. Chrome has released version 148.0.7778.96 to address this vulnerability. No evidence of active exploitation (not in CISA KEV) or public proof-of-concept code at time of analysis, though the vulnerability's network-based attack vector and low complexity make it a realistic exploitation target once technical details become public.
Local privilege escalation in Google Chrome Chromoting (prior to 148.0.7778.96) on Windows allows attackers to gain elevated OS-level privileges by tricking users into opening a malicious file. While CVSS scores this as high severity (7.8), real-world risk is tempered by local access and required user interaction (CVSS: AV:L/UI:R). Vendor patch available in version 148.0.7778.96 released May 2026. No active exploitation (CISA KEV) or public exploit code identified at time of analysis.
Remote code execution in Google Chrome versions prior to 148.0.7778.96 on Linux and ChromeOS allows attackers to execute arbitrary code when users perform specific UI gestures on a malicious webpage. The vulnerability stems from insufficient input validation in Chrome's UI layer (CWE-20). Vendor patch available in Chrome 148.0.7778.96. No public exploit identified at time of analysis, though CVSS 8.8 reflects high impact across confidentiality, integrity, and availability.
Remote code execution in Google Chrome prior to 148.0.7778.96 through a use-after-free vulnerability in the UI component. Attackers who have already compromised the renderer process can escape sandbox restrictions and execute arbitrary code by delivering a specially crafted HTML page requiring user interaction. Google has released patch version 148.0.7778.96. No active exploitation confirmed in CISA KEV at time of analysis, though the vulnerability requires prior renderer compromise which increases attack complexity beyond the CVSS AC:L rating suggests.
Local privilege escalation in Google Chrome's Windows updater component allows unprivileged users to gain SYSTEM-level access by exploiting insufficient input validation when the updater processes a specially crafted malicious file. Affects all Chrome versions on Windows prior to 148.0.7778.96. Google has released a patched version (148.0.7778.96). No active exploitation confirmed by CISA KEV at time of analysis, though the local attack vector and medium severity rating suggest potential for targeted attacks in enterprise environments where Chrome auto-update may be delayed.
Remote code execution in Google Chrome's WebRTC implementation (versions prior to 148.0.7778.96) allows attackers to execute arbitrary code within the browser sandbox through a malicious HTML page exploiting type confusion in WebRTC. Patch available via Chrome 148.0.7778.96. Requires user interaction (visiting crafted page) but no authentication. CVSS 8.8 reflects high impact across confidentiality, integrity, and availability within sandbox constraints. No confirmed active exploitation or public POC identified at time of analysis.
Remote code execution in Google Chrome's WebRTC component (versions prior to 148.0.7778.96) allows attackers to execute arbitrary code within the browser's sandbox by exploiting a use-after-free memory corruption vulnerability via a malicious HTML page. While sandboxed, successful exploitation achieves high confidentiality, integrity, and availability impact within the renderer process. EPSS data unavailable; not listed in CISA KEV, indicating no confirmed widespread exploitation at time of analysis. Vendor patch released as Chrome 148.0.7778.96.