Suse
Monthly
Backend connection hijacking in Traefik reverse proxy (2.11.0 through 2.11.56 and 3.0.0 through 3.7.12) lets an unauthenticated remote client impersonate another user over HTTP/3. Because the HTTP/3 entrypoint never calls service.AddTransportOnContext, the kerberosRoundTripper falls back to a shared backend transport instead of one bound to each frontend connection, so when a backend uses connection-bound NTLM or Negotiate authentication with keep-alive, an unrelated client can reuse a backend connection already authenticated for a victim, read the victim's data, and act as the victim without ever obtaining their credentials. No public exploit is identified at time of analysis, though the fix PR ships a regression test that effectively demonstrates the flaw.
Traefik's header-security defenses (aliasHeadersStrategy, underscoreHeadersStrategy, forwardedHeaders) inspect req.Header but not req.Trailer, allowing unauthenticated clients on versions 3.2.0 through 3.7.12 to smuggle security-sensitive header values through HTTP/1.1 chunked trailers or HTTP/2 trailers. When retry or buffering middleware is active in the routing chain, attacker-controlled trailer values become accessible before the request is cloned for the backend; backends that merge trailers into their header namespace then receive the spoofed values, bypassing Traefik's documented delete or reject behavior. No public exploit code has been identified and this CVE is not in CISA KEV, but the impact on identity and routing integrity at the backend is classified high by the CVSS 4.0 subsequent-system metrics.
Container escape in crun >= 1.29, when built with libkrun and started rootful with passt networking (krun.use_passt), allows an attacker who controls the container image to execute arbitrary code with host root privileges. This is a regression introduced in crun 1.29, meaning environments that recently upgraded are at risk while those on earlier versions are not. No public exploit code or CISA KEV listing has been identified at time of analysis, but successful exploitation yields full host compromise via container escape.
Template injection in Velociraptor's notebook backup restoration pipeline allows a low-privileged NOTEBOOK_EDITOR user to execute arbitrary VQL queries at elevated server-level permissions. The daily backup feature - enabled by default - captures notebook cell content verbatim; when an administrator later restores the backup, that content is interpolated into a Go template without ACL enforcement, breaking the privilege boundary between analyst and server roles. No public exploit has been identified at time of analysis, but the chained attack path (plant payload, wait for restore) represents a credible insider or compromised-analyst escalation vector against DFIR infrastructure.
Privilege escalation in Rapid7 Velociraptor lets any user permitted to schedule client monitoring artifacts run otherwise-restricted artifacts - including Linux.Sys.BashShell - to execute arbitrary commands on managed endpoints. The server enforced the EXECVE permission for scheduling command-execution artifacts through normal collection, but applied no equivalent permission or CLIENT_EVENTS-type check on the client monitoring path, so a low-privileged operator can bypass the gate entirely. No public exploit identified at time of analysis, though the upstream fix (PR #4967) makes the missing check straightforward to reconstruct.
HTTP request smuggling via inconsistent request framing in Puma's native http11_parser (reported range Puma 5.0.0 through 8.0.3) allows a remote, unauthenticated attacker to desynchronize request boundaries between Puma and an upstream HTTP intermediary, enabling request hijacking, cache poisoning, or bypass of front-end access controls; the description's claim of arbitrary code execution is unverified and inconsistent with CWE-444. Exploitation is deployment-dependent: it requires a reverse proxy, CDN, or load balancer whose parsing of ambiguous Content-Length/Transfer-Encoding framing diverges from Puma's, which is why our independent assessment rates it AV:N/AC:H/PR:N/UI:N/S:C rather than the published 9.1. Risk signals are weak and conflicting - EPSS is 0.17% (6th percentile), there is no CISA KEV listing and no confirmed public exploit code, and the only third-party reference is an unverified GitHub issue - so raw severity should be discounted.
Cross-tenant IDOR in identrail's GitHub App connection-completion endpoint allows any authenticated tenant to hijack another customer's GitHub App installation and read their organization's private repositories. The flaw exists at POST /v1/workspaces/:workspace_id/projects/:project_id/github/connect/complete, where the client-supplied installation_id is accepted and persisted with no ownership verification-despite the co-located state token being rigorously bound to {TenantID, WorkspaceID, ProjectID}. Fixed in v1.0.2; no public exploit code or CISA KEV listing identified at time of analysis.
Arbitrary code execution in Joker (the Clojure/ClojureScript linter) before v1.8.2 allows an attacker who controls files within a repository to execute arbitrary Clojure code on any developer or CI runner that lints that repository. The linter's directory-walking behavior automatically located and executed project-local `.jokerd/linter.*` files before processing any source file, treating attacker-controlled repository content as trusted configuration. Because editor integrations and CI pipelines commonly invoke `joker --lint` automatically on checked-out code, this creates a reliable developer-toolchain attack surface. No public exploit or CISA KEV listing has been identified; vendor-confirmed fix is available in v1.8.2.
A double-free in the CalDAV calendar worker of Cyrus IMAP before 3.12.4 lets an authenticated calendar user crash that worker by sending a WebDAV PATCH request carrying PATCH-ACTION="BYPARAM@..." against a calendar resource that holds two or more properties of the matched kind. The vulnerability is reachable only with valid credentials and with the CalDAV/calendar component enabled (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H, CWE-415), and the assessed outcome is a worker crash/restart rather than data disclosure or code execution. No public exploit code has been identified and EPSS is low at 0.22% (12th percentile); CISA SSVC rates exploitation as 'none' and the issue as not automatable, so this is a bounded availability bug rather than a critical-priority one.
The krb5 crypto subsystem in the Linux kernel fails to zero derived Kerberos key material before freeing memory buffers, leaving sensitive cryptographic keys resident in freed slab allocator objects. Both `crypto_krb5_prepare_encryption()` and `crypto_krb5_prepare_checksum()` call plain `kfree()` instead of the security-aware `kfree_sensitive()` wrapper, which would first zero the allocation. Systems using Kerberos-authenticated kernel services - primarily NFSv4 with sec=krb5 or CIFS/SMB with Kerberos - on kernel versions from commit 3936f02b through the stable fixes are affected; no public exploit or active exploitation has been identified.
Unauthorized cryptographic hardware access in KVM for s390 (IBM Z) nested virtualization allows a low-privileged nested guest to access AP queues (hardware crypto devices) that were explicitly revoked from its allocation. When the KVM VSIE subsystem shadows a format0 APCB (Adjunct Processor Control Block) from a crycb type 0 or 1 structure, it only copies bits 0-63 but leaves bits 64-255 unchanged from whatever stale state existed in the vsie shadow page. A nested (L2) guest exploiting this retains access to cryptographic devices beyond those granted by the host hypervisor, potentially exposing cryptographic keys and operations belonging to other workloads. No public exploit has been identified at time of analysis and no CISA KEV listing exists.
Use-after-free in the Linux kernel Bluetooth ISO stack allows an adjacent unauthenticated attacker to corrupt kernel memory and potentially execute arbitrary code. The flaw is a race condition in iso_conn_ready(): when a BIS listener socket is concurrently closed while an incoming Bluetooth Isochronous connection is being processed, a child socket is allocated that holds a dangling pointer to the now-freed parent socket, which is later dereferenced during disconnect via iso_chan_del() and bt_accept_unlink(). Patches are available across multiple stable kernel branches (6.12.109, 7.2.4, 6.18.50, and 7.3-rc1); no public exploit code or active exploitation has been identified at time of analysis.
Use-after-free in zstd-jni versions 1.3.8-4 through 1.5.7-13 allows callers to invoke setDict, setLongMax, setLevel, and setRefMultipleDDicts on already-closed stream objects, writing through freed native (JNI) pointers into arbitrary JVM memory. The root cause is missing closed-state validation in stream classes such as BaseZstdBufferDecompressingStreamNoFinalizer and ZstdInputStreamNoFinalizer, meaning the JNI layer operates on native context structures that have already been released. Exploitation can corrupt unrelated heap objects or terminate the JVM process entirely. No public exploit code or CISA KEV listing is identified at time of analysis.
Use-after-free in zstd-jni versions 1.3.8-4 through 1.5.7-13 allows attackers to trigger silent data corruption or JVM crashes by closing a Zstandard dictionary after it has been associated with a stream or context. The library's locking design released the dictionary's shared lock immediately after the load call, leaving the stream holding a native pointer to freed memory; subsequent read or write operations on that stream then access freed native heap, producing undefined behavior at the JVM/native boundary. No public exploit has been identified at time of analysis, and a patched release (v1.5.7-14) is available with two upstream commits.
Out-of-bounds memory access in zstd-jni versions 1.3.3-1 through 1.5.7-13 enables unauthenticated network-accessible attackers to crash the JVM by supplying crafted sample-size arrays to the Zstd.trainFromBufferDirect dictionary-training API. The native C implementation (jni_zdict.c) failed to sum caller-supplied sample lengths against the DirectBuffer's actual capacity before iterating, allowing the native code to walk past the buffer allocation boundary and trigger a hard JVM termination. A patched release (v1.5.7-14) is available; no public exploit has been identified at time of analysis.
Out-of-bounds memory reads in zstd-jni versions 1.1.1 through 1.5.7-13 allow unauthenticated remote attackers to crash the JVM or extract arbitrary frame-size data from unintended memory regions by supplying crafted Zstandard-compressed input with negative or integer-overflowing offset values. Three JNI native methods - findDirectByteBufferFrame, decompressedDirectByteBuffer, and getDirectByteBufferFrame - perform 32-bit signed bounds checks without first validating that src_offset or src_size are non-negative, allowing values near Integer.MIN_VALUE to pass the comparison and drive native code to read unmapped memory. The CVSS 4.0 score of 8.8 reflects a high availability impact (JVM termination) and limited confidentiality impact; no public exploit or KEV listing has been identified at time of analysis.
Heap out-of-bounds write in VLC Media Player 3.0.0 through 3.0.23 allows a local attacker to corrupt memory by tricking a user into opening a crafted PNG file with attacker-controlled dimensions. The root cause is a 32-bit integer overflow in AllocatePicture() where plane pitch-times-lines multiplication wraps before widening to the size_t accumulator, causing both overflow guards to pass on the already-corrupted value; aligned_alloc then reserves a small wrapped buffer while the PNG decoder writes full-dimension scanlines past its end. No public exploit has been identified at time of analysis, and EPSS indicates 0.30% exploitation probability over the next 30 days.
Regular expression denial of service in GitPython before 3.1.60 allows unauthenticated remote attackers to exhaust server CPU resources by supplying a crafted commit with a malformed author or committer field. The vulnerable regex Actor.name_email_regex exhibits quadratic backtracking when processing an unterminated angle bracket in the author string, stalling affected processes for over two minutes per commit access. Any application that reads attacker-influenced git repositories using GitPython is exposed; no public exploit or active exploitation (CISA KEV) has been identified at time of analysis.
Argument injection in GitPython 3.1.59's high-level diff API allows low-privileged remote attackers to read arbitrary filesystem paths by passing the unsanitized `--no-index` flag to the underlying git diff command. By chaining `--no-index` with the `-I`/`--ignore-matching-lines` regex filter, an attacker can construct a content-dependent Boolean oracle - issuing repeated queries that distinguish between regex match and mismatch responses to recover single-line secrets from local files. No active exploitation has been confirmed (not in CISA KEV), but the technique is deterministic and requires only authenticated API access. Patch-upgraded version 3.1.60 is available.
Arbitrary code execution in GitPython before 3.1.60 is possible when a victim application calls index.commit() on an attacker-controlled repository. The root cause is insufficient validation of the git directory location: GitPython trusts tracked files such as gitdir, commondir, and HEAD to resolve the effective git directory, allowing a crafted repository to redirect that resolution to an attacker-controlled path containing a malicious pre-commit hook. No public exploit has been identified at time of analysis, but the attack is realistic in any Python-based DevOps pipeline, CI/CD system, or tooling that opens and commits to externally sourced repositories.
Out-of-bounds read in zstd-jni versions 1.2.0 through 1.5.7-13 allows attackers who can supply dictionary constructor parameters to crash the JVM and potentially read limited native heap memory. The ZstdDictCompress constructor passed unvalidated offset and length values directly to the C JNI layer, where out-of-range values cause the native code to read beyond the allocated Java heap array. No CISA KEV listing or public exploit has been identified; the CVSS 4.0 score of 8.8 reflects high availability impact via reliable JVM crash and limited confidentiality exposure from native heap reads.
Plaintext recovery and content forgery in OpenIDC/cjose 0.6.1 through 0.6.2.5 occurs because the library zero-fills the content-encryption key (CEK) instead of randomizing it whenever a JWE is built with an AES-CBC-HMAC enc (A128CBC-HS256/A192CBC-HS384/A256CBC-HS512) and a key-management algorithm that generates a fresh CEK. Every affected ciphertext is therefore encrypted and authenticated under an all-zero, publicly known key, so anyone who obtains the JWE can decrypt it and forge or modify its contents. Fixed in 0.6.2.6; no public exploit identified at time of analysis, but the flaw is trivially demonstrable and confirmed by the vendor GitHub Security Advisory.
Heap buffer overflow in OpenIDC/cjose versions prior to 0.6.2.5 allows a remote unauthenticated attacker to corrupt process heap memory by submitting a crafted JWE token with an oversized `encrypted_key` segment targeting the AES Key Wrap decryption path. The `cjose_jwe_import()` and `cjose_jwe_decrypt()` functions are pre-authentication entry points that accept fully attacker-controlled input, making every application that decrypts AES-KW JWEs with this library directly reachable. Impact ranges from a reliable denial of service (process crash) to potential memory-corruption-based code execution depending on heap layout and allocator behavior. No public exploit has been identified at time of analysis, but the patch commit confirms the exact boundary condition and includes a regression test demonstrating the overflow trigger.
Heap-based buffer overflow in Google Chrome's WebRTC component (all versions prior to 153.0.8010.36) enables a remote unauthenticated attacker to potentially execute arbitrary code within the Chrome renderer sandbox by luring a target to a crafted HTML page. The vulnerability is classified CWE-122 and carries a CVSS base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); however, Chromium's own internal severity rating is 'Low,' which is notably discordant and implies that exploitation is constrained to within-sandbox code execution rather than full OS compromise. No public exploit code and no CISA KEV listing have been identified at the time of analysis.
Incorrect authorization in the Extensions component of Google Chrome before 153.0.8010.36 allows a remote attacker to bypass system access restrictions and reach a privileged internal page by luring a victim to a crafted HTML page. Google credits its own team with discovery, and a fixed build is available; no public exploit has been identified at time of analysis, and Chromium rated the underlying issue only Low severity despite the 9.8 NVD score.
Race-condition-triggered code execution in Google Chrome's V8 JavaScript engine (all versions prior to 153.0.8010.36) allows a remote unauthenticated attacker to execute arbitrary code inside the Chrome renderer sandbox by serving a crafted HTML page to a victim. Exploitation is constrained to the Chrome sandbox process rather than the underlying OS, which aligns with Chromium's own internal severity rating of 'Low' despite the CVSS base score of 7.5. No public exploit code or CISA KEV listing is present at time of analysis; the high attack complexity metric reflects the timing-sensitive nature of race-condition exploitation.
Improper certificate validation in Chrome's Federated Credential Management (FedCM) component — fixed in Chrome 153.0.8010.36 — lets a remote attacker who controls crafted network traffic, combined with social engineering of the victim, bypass web origin policy and expose cross-origin identity data. The flaw is a confidentiality-only issue (no integrity or availability impact) and Chrome rates it security severity Low, despite a 7.5 CVSS base score; EPSS is only 0.15% (4th percentile), it is not in CISA KEV, and no public exploit code has been identified at time of analysis. Vendor-released patch: 153.0.8010.36.
Memory corruption in V8, Chrome's JavaScript engine, allows an attacker who can get a user to install a crafted Chrome extension to execute arbitrary code confined within the Chrome sandbox, affecting all Chrome versions prior to 153.0.8010.36. Despite the CVSS 8.8 base score, Chromium's own security team rates this 'Low' severity, reflecting that exploitation is bounded by Chrome's sandbox and does not constitute a full OS-level compromise without a separate sandbox escape primitive. No public exploit code or active exploitation has been identified at time of analysis. Vendor-released patch is available.
Sandbox escape via incorrect authorization in the Chrome Updater component on Windows allows a local attacker to execute arbitrary code outside the browser's sandbox using a crafted local program. Affected versions are all Google Chrome releases prior to 153.0.8010.36 on Windows. The Chromium team rates internal severity as 'Low' - notably lower than the CVSS 8.1 score - suggesting that while the impact is high if exploited, real-world attack complexity limits practical risk. No public exploit or active exploitation has been identified at time of analysis.
Use-after-free in Google Chrome's DevTools component (versions prior to 153.0.8010.36) enables arbitrary code execution within the renderer sandbox when a victim is socially engineered into visiting a crafted HTML page. The CVSS score of 8.8 reflects full C/I/A impact, but Chromium's own internal severity classification of 'Low' signals that exploitation is sandboxed - OS-level compromise requires an additional chained sandbox escape. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Remote code execution in Google Chrome's DevTools component before 153.0.8010.36 stems from a use-after-free (CWE-416) that, per the advisory, allows a crafted HTML page to execute arbitrary code outside the browser sandbox. All desktop Chrome builds prior to the fixed stable release are affected; the flaw was reported internally by the Chrome team, is fixed in the stable channel, and has no public exploit identified at time of analysis. Notably, the assigned CVSS is 9.6 (Critical) while Chromium itself rated the security severity only 'Low', a significant conflict discussed below.
Server-side request forgery in Google Chrome for Mobile (builds prior to 153.0.8010.36) allows a remote attacker who successfully social-engineers a victim into opening a crafted HTML page to induce the browser to issue requests that bypass system access restrictions. Exploitation is not a drive-by: user interaction is mandatory, and the authoritative reassessment scores this as CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N (confidentiality/access-restriction bypass only), so the widely circulated 9.8 vector overstates the real-world impact; Chromium itself rates the issue Low. EPSS is 0.18% (7th percentile) and no public exploit identified at time of analysis, while a vendor-released patch (153.0.8010.36) is already available.
Sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The flaw resides in the Storage component's incorrect reference resolution (CWE-706), making this a second-stage exploit that chains with a separate renderer compromise to achieve full sandbox breakout. No public exploit has been identified at time of analysis, and the fix is available in the stable channel release 153.0.8010.36.
Sandbox-escaping remote code execution in Google Chrome's WebPackaging component affects all desktop versions prior to 153.0.8010.36. A use-after-free (CWE-416) reachable from a crafted HTML page can let a remote attacker potentially execute arbitrary code outside the renderer sandbox with no authentication, requiring only that the victim visit a malicious page. No public exploit has been identified at time of analysis; Chromium's own internal triage rated the security severity 'Low', which sits in notable tension with the 9.6 CVSS assigned to the record.
Remote code execution in Google Chrome on iOS before 153.0.8010.36 stems from a use-after-free in the Sharing component (CWE-416), letting a remote attacker who lures a victim to crafted network content execute arbitrary code outside the browser sandbox. Google has shipped a patched Chrome build; no public exploit is identified at time of analysis, and Google/Chromium rated the underlying bug 'Medium' severity even though the assigned CVSS base score is 9.6.
Remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the Passwords component that, when triggered via crafted UI interaction and social engineering, can let a remote attacker escape the renderer sandbox and run arbitrary code. All Chrome desktop builds before the 153.0.8010.36 stable release are affected. No public exploit identified at time of analysis, and no EPSS or KEV data was provided; note that Google's Chromium team rated the underlying bug only 'Medium' severity, which sits in tension with the supplied CVSS 9.6.
Sandbox-escaping remote code execution in Google Chrome's Aura windowing layer affects all desktop builds prior to 153.0.8010.36. A remote attacker who lures a victim to a crafted HTML page can trigger a use-after-free (CWE-416) and potentially execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the fix ships in the stable-channel desktop update.
Out-of-bounds write in the Media component of Google Chrome before 153.0.8010.36 allows a remote attacker to potentially execute arbitrary code outside the browser's renderer sandbox by luring a victim to a crafted HTML page. The scope-changing memory-corruption bug carries a CVSS of 9.6 despite Chromium's own 'Medium' severity rating, and a vendor patch is available. There is no public exploit identified at time of analysis.
Remote code execution in Google Chrome on Windows prior to 153.0.8010.36 arises from a type-confusion bug in the browser's Rust code, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Google shipped a fixed build via the Stable channel, and the flaw was reported internally by the Chrome team. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though sandbox-escape memory-corruption bugs in Chrome are historically high-value exploitation targets.
Sandbox-escape remote code execution affects Google Chrome on macOS prior to 153.0.8010.36, where an improper quantity-validation flaw (CWE-1284) in Tint, the WebGPU/WGSL shader compiler in Chromium's Dawn graphics stack, lets a crafted HTML page break out of the renderer sandbox. A remote attacker who lures a victim to a malicious web page can potentially execute arbitrary code with the privileges of the browser process on the host. Google reports a fix is shipped; there is no public exploit identified at time of analysis, and Chromium internally rated the issue Medium severity despite the high provided CVSS.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from a numeric truncation error in the Media component, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. The vendor patch is available via the September 2026 stable-channel update; no public exploit is identified at time of analysis. Note a signal conflict: Chromium rated this 'Medium' severity while the supplied CVSS base score is 9.6 Critical.
Remote code execution in Google Chrome for macOS prior to 153.0.8010.36 stems from a use-after-free in the Extensions component, letting a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw carries a CVSS 9.6 (scope-changed, network vector with user interaction), though Chromium's own security team rated it 'Medium'. No public exploit has been identified at time of analysis, and the fix is available in the stable channel.
FileAPI improper input validation in Google Chrome prior to 153.0.8010.36 enables an attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code on the underlying host system. The flaw, tracked in Chromium issue 532957878, was addressed in the September 2026 stable channel release. With an EPSS of 0.30% and no confirmed active exploitation, this functions as a second-stage sandbox-escape primitive rather than a standalone remote attack.
Use-after-free in Chrome's V8 JavaScript engine allows a remote attacker who can socially engineer a victim into installing a crafted Chrome extension to execute arbitrary code within the browser's renderer sandbox, affecting all Chrome versions prior to 153.0.8010.36. The vulnerability is constrained to in-sandbox execution - it does not constitute a standalone sandbox escape - which aligns with the S:U CVSS metric and Chromium's internal 'Medium' severity rating despite the 8.8 base score. No public exploit code or active exploitation has been identified at time of analysis, and Google has shipped a patch in the stable channel.
Missing authorization in the Extensions subsystem of Google Chrome prior to 153.0.8010.36 enables a remote attacker to obtain sensitive browser information by delivering a crafted Chrome extension that bypasses access control checks. The vulnerability is classified CWE-862 (Missing Authorization), meaning the runtime fails to enforce proper permission boundaries between extension capabilities and protected browser data. No public exploit code or active exploitation has been identified at time of analysis; Chromium's own internal severity rating of 'Medium' reflects practical exploitation barriers not fully captured by the NVD CVSS 7.5 High rating.
Use-after-free in Google Chrome's DevTools component prior to 153.0.8010.36 enables a local attacker to escape the browser sandbox and execute arbitrary code at the host OS level via a crafted local program. Chromium's own severity rating is 'Medium', reflecting the local access prerequisite, while the CVSS 8.1 score captures the high-impact sandbox-escape outcome once exploitation succeeds. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the EPSS score (0.12%, 2nd percentile) confirms low observed exploitation probability.
Sandbox escape via incorrect authorization in the Views component of Google Chrome on Windows (versions prior to 153.0.8010.36) enables arbitrary code execution outside the browser sandbox. Exploitation requires an attacker to first compromise the renderer process and then leverage social engineering to induce user interaction with a crafted HTML page. No public exploit or KEV listing exists at time of analysis; Chromium's own severity rating of Medium contrasts with the CVSS 8.3 score, reflecting the difficult two-stage attack chain.
Sandbox escape via improper initialization (CWE-665) in Google Chrome's Views UI framework on Windows, prior to version 153.0.8010.36, can lead to arbitrary code execution outside the browser sandbox. The attack is chained: an adversary must first compromise the renderer process through a separate vulnerability, then leverage social engineering to trigger the Views initialization flaw, elevating from renderer-level code execution to full host OS access. No public exploit code has been identified and EPSS sits at 0.28% (20th percentile), consistent with the multi-step prerequisite bar, though the C:H/I:H/A:H impact profile warrants prompt patching.
Sandbox-escaping remote code execution in Google Chrome's Browser process on Windows (all versions prior to 153.0.8010.36) stems from a use-after-free flaw. A remote attacker who lures a victim into opening a crafted HTML page can corrupt reclaimed heap memory in the privileged browser process and execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the vendor has shipped a fixed stable build.
Uncontrolled search path element in Chrome's Windows CredentialProvider component (CWE-427) enables a local attacker to execute arbitrary code outside the browser sandbox on Windows systems running Chrome prior to 153.0.8010.36. The flaw is a DLL or executable search-order hijacking issue: Chrome's CredentialProvider resolves a dependency by searching an attacker-controllable path, allowing a malicious local program to intercept and execute in place of a legitimate component, with the result escaping Chrome's sandbox entirely. No public exploit code or CISA KEV listing has been identified at time of analysis.
Site isolation bypass in Google Chrome's FileSystem component allows a remote attacker who has already achieved renderer process compromise to escape cross-origin boundaries via a crafted PDF file. Affected versions are all Chrome releases prior to 153.0.8010.36 on desktop platforms. The vulnerability (CWE-863, Incorrect Authorization) enables the attacker to read or modify data belonging to other origins, undermining Chrome's core sandboxing guarantee. No public exploit or active exploitation (CISA KEV) has been identified; EPSS is 0.16%, consistent with the SSVC 'Exploitation: none' rating.
Incorrect authorization in Google Chrome's Permissions subsystem before version 153.0.8010.36 enables remote attackers to exfiltrate sensitive browser information through a crafted Chrome extension that requires social engineering to install. The flaw (CWE-863) causes Chrome's permission brokering layer to incorrectly authorize an extension's access to protected browser data, resulting in high-confidence confidentiality impact with no integrity or availability consequence. No public exploit has been identified and EPSS sits at 0.18%, consistent with the social-engineering prerequisite that constrains mass opportunistic exploitation.
Site isolation bypass in Google Chrome prior to 153.0.8010.36 allows a remote attacker who has already compromised the renderer process to escape Chrome's cross-site isolation boundary via a crafted file combined with social engineering. The flaw is rooted in incorrect authorization (CWE-863) within the SiteIsolation component, meaning the browser fails to properly enforce origin-based access controls once the renderer is under attacker control. Vendor-released patch 153.0.8010.36 is available; no public exploit has been identified and EPSS sits at 0.16% (6th percentile), consistent with the Chromium team's 'Medium' severity rating despite the CVSS 8.8 base score.
Sandbox-escape remote code execution in Google Chrome for Android before 153.0.8010.36 arises from an integer overflow in the GPU process, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. Fixed in the same 153.0.8010.36 Stable Channel release that addressed several other GPU/media memory-safety bugs; no public exploit identified at time of analysis. Note the rating tension: the input CVSS is 9.6 (Critical) while Google's own Chromium severity is only Medium.
Missing authorization in the WebView component of Google Chrome on Android before 153.0.8010.36 lets a remote attacker who first tricks a user via social engineering bypass system access restrictions through crafted network traffic. The flaw is tracked as CWE-862 (missing authorization) and was reported by Google's Chrome team; a vendor patch is available. Chromium rates the security severity as Medium, EPSS is low (0.17%), and no public exploit or CISA KEV listing has been identified.
Use-after-free in Chrome's ANGLE graphics layer on Windows enables sandbox escape and arbitrary code execution when a renderer process has already been compromised. Affected versions are all Chrome releases prior to 153.0.8010.36 on Windows; exploitation requires an attacker to first compromise the renderer and then deliver a crafted HTML page triggering the ANGLE memory corruption. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.28% (20th percentile) reflects low observed exploitation probability.
Chrome's Extensions subsystem prior to 153.0.8010.36 fails to correctly enforce security policies when inputs originate from a compromised renderer process (CWE-807), enabling a two-stage sandbox escape that results in arbitrary code execution outside the Chrome sandbox on the host OS. Exploitation chains a prior renderer compromise with social engineering to bypass Extensions-mediated policy decisions. No public exploit code exists and EPSS is low (0.30%, 22nd percentile), consistent with Chromium's internal 'Medium' severity rating despite the CVSS 8.3 score - reflecting the substantial pre-condition barrier.
Heap-based buffer overflow in the WebRTC component of Google Chrome prior to 153.0.8010.36 allows a remote unauthenticated attacker to execute arbitrary code within the Chrome renderer sandbox by luring a user to a crafted HTML page. The RCE is sandbox-confined (CVSS S:U), meaning a chained sandbox-escape exploit would be needed for full host-level compromise. No public exploit or active exploitation has been identified at time of analysis, and EPSS sits at a low 0.24% (15th percentile), consistent with Chromium's own 'Medium' severity designation despite the 8.8 CVSS base score.
Sandbox-escape remote code execution in Google Chrome's Extensions component (versions prior to 153.0.8010.36) lets a remote attacker potentially run arbitrary code outside the renderer sandbox by delivering crafted network traffic. The root cause is incorrect reference resolution (CWE-706), where a name or reference is resolved to the wrong target. Google has shipped a fix; there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.20%).
Sandbox escape via confused deputy in Chrome's DataTransfer component allows an attacker who has already compromised the renderer process to execute arbitrary code outside the sandbox by directing the victim to a crafted HTML page. Fixed in Chrome 153.0.8010.36, this is classified 'Medium' severity by the Chromium team despite the CVSS 8.3 score with full scope change (S:C, C:H/I:H/A:H), reflecting that renderer pre-compromise is required. No public exploit code or CISA KEV listing exists at time of analysis, and EPSS is 0.25% (16th percentile).
Site isolation bypass in Google Chrome's ServiceWorker implementation allows a remote attacker who has already compromised the renderer process to escape cross-origin protections via a crafted HTML page. All Chrome versions prior to 153.0.8010.36 are affected. This is a chained exploit step: an attacker must first achieve renderer code execution (via a separate vulnerability), then leverage this incorrect authorization flaw to break site isolation and access data from other origins. No public exploit or CISA KEV listing exists at time of analysis.
Sandbox escape in Google Chrome's Extensions component (versions prior to 153.0.8010.36) permits an attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via crafted network traffic. The missing authorization check (CWE-862) in the Extensions subsystem fails to enforce inter-process privilege boundaries, converting a renderer-level foothold into host-level code execution. No public exploit or active exploitation has been identified; EPSS sits at 0.19%, though SSVC rates the technical impact as 'total' given successful exploitation fully bypasses Chrome's sandbox isolation.
Sandbox escape via incorrect authorization in the WebView component of Google Chrome on Android (prior to 153.0.8010.36) allows a network-based attacker to execute arbitrary code outside the Chrome renderer sandbox. Exploitation is a two-stage process: the attacker must first compromise the renderer process, then leverage the CWE-863 authorization flaw in WebView to break out of the sandbox via a crafted HTML page. No public exploit or KEV listing has been identified at time of analysis; EPSS is low at 0.30%, consistent with the complexity barrier of requiring a prior renderer compromise.
Sandbox-escape via race condition in Google Chrome's Updater component on Windows allows a local, unprivileged attacker to execute arbitrary code outside the Chrome sandbox. Affected versions are all Chrome releases for Windows prior to 153.0.8010.36, fixed in the September 2026 stable channel update. No public exploit has been identified and EPSS sits at 0.10% (1st percentile), but successful exploitation yields full C:H/I:H/A:H impact beyond the sandbox boundary. Chromium's own rating of 'Medium' reflects the high attack complexity imposed by the race condition timing requirement.
Site isolation bypass in Google Chrome's FileAPI component allows a remote attacker who has already compromised the renderer process to escape Chrome's cross-origin isolation boundary via a crafted HTML page. Affected versions are all Chrome releases prior to 153.0.8010.36. This is a second-stage exploit - the FileAPI race condition (CWE-367, TOCTOU) enables escalation from a sandboxed renderer compromise into full cross-origin data access, making it a critical link in a multi-stage sandbox escape chain. No public exploit or CISA KEV listing is identified at time of analysis; EPSS is 0.24% (16th percentile), consistent with the high complexity of the required exploit chain.
Privilege elevation in Chrome's WebUI component prior to version 153.0.8010.36 enables sandbox escape and arbitrary code execution outside the browser sandbox when the renderer process has already been compromised. This is a second-stage, chained exploit: an attacker must first achieve renderer-level code execution (e.g., via a separate renderer bug) and then leverage this WebUI flaw (CWE-250 - execution with unnecessary privileges) to break out of the sandbox. No public exploit code has been identified and no CISA KEV listing exists; SSVC rates automatable exploitation as 'no', consistent with the multi-step chain requirement.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from incorrect reference resolution in the FileSystem component, letting a remote attacker who lures a victim into visiting a crafted HTML page run arbitrary code outside the renderer sandbox. Reported by Google's own Chrome team and patched in the 2026-09 stable-channel desktop update; no public exploit is identified and SSVC lists exploitation as none, with EPSS at a modest 0.32%. Note a signal conflict: Chromium rates this 'Medium' while the assigned CVSS is 9.6, and the description requires user interaction (social engineering), so real-world risk is lower than the raw score suggests.
Sandbox escape via improper input validation in Chrome's SiteIsolation component allows an attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox. Affected versions are all Chrome releases prior to 153.0.8010.36. Exploitation requires chaining this flaw with a separate renderer compromise - an attacker must first gain control of the renderer (typically via another renderer-targeted vulnerability), then use this SiteIsolation validation flaw to break out of the sandbox and execute code in a more privileged process context. No public exploit code or active exploitation has been identified at time of analysis.
Site isolation authorization bypass in Google Chrome prior to 153.0.8010.36 allows a remote attacker who has already compromised the renderer process to escape cross-origin boundaries via a crafted HTML page. The flaw (CWE-862, Missing Authorization) resides in the SiteIsolation component, which enforces process-level separation between web origins; with that enforcement missing, a controlled renderer can access data belonging to other sites. No public exploit has been identified and EPSS sits at 0.18%, consistent with this vulnerability's role as a second-stage link in a chained browser attack rather than a standalone entry point.
Type confusion (CWE-843) in Chrome's XML processing component allows remote attackers to execute arbitrary code within the Chrome renderer sandbox by enticing a target to visit a crafted HTML page. All Chrome desktop versions prior to 153.0.8010.36 are affected across Windows, macOS, and Linux. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; the impact is further bounded by Chrome's sandbox architecture, which prevents direct OS-level code execution without a secondary sandbox-escape primitive.
Use-after-free in Chrome's Chromecast component allows remote attackers to execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. Affected are all Google Chrome releases prior to 153.0.8010.36 across desktop platforms. Exploitation is sandboxed - code execution is confined to the renderer process - but the C:H/I:H/A:H impact rating reflects full compromise of data accessible within that context. No active exploitation has been confirmed and no public proof-of-concept code is known at time of analysis.
Sandbox escape in Google Chrome's FileSystem component prior to 153.0.8010.36 stems from missing authorization checks (CWE-862), allowing arbitrary code execution outside the renderer sandbox. The attack is multi-stage: an attacker must first compromise the renderer process via a separate exploit, then serve a crafted HTML page using social engineering to trigger the authorization gap and escape the sandbox. No active exploitation is confirmed (not in CISA KEV; EPSS 0.34% at 27th percentile; SSVC exploitation: none), and the renderer pre-compromise requirement substantially limits real-world attack surface.
Sandbox-escaping remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the browser's Core component that a remote attacker can trigger through a maliciously crafted Chrome extension. Successful exploitation lets attacker-controlled code run outside the renderer sandbox with the browser process's privileges, but it requires convincing the victim to install or interact with the malicious extension (social engineering). There is no public exploit identified at time of analysis, EPSS is low (0.24%, 15th percentile), and CISA SSVC records exploitation as none, so the risk is high-impact but currently unproven in the wild.
Remote code execution in Google Chrome before 153.0.8010.36 stems from a use-after-free in the browser's Payments component, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Chromium rates the severity High, and the supplied CVSS is 9.6 reflecting the sandbox-escape scope change. EPSS is low (0.35%, 29th percentile) and no public exploit is identified at time of analysis.
Remote code execution inside the Chrome sandbox is possible in Google Chrome versions prior to 153.0.8010.36 via a use-after-free vulnerability in the V8 JavaScript engine, triggered by a specially crafted HTML page. An unauthenticated remote attacker who can lure a user to a malicious page can execute arbitrary code within the Chrome renderer process sandbox - a significant foothold even without a sandbox escape. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.21% reflects low observed exploitation activity, though V8 UAF primitives are historically attractive to threat actors.
Type confusion in V8 (CWE-843) in Google Chrome prior to 153.0.8010.36 allows a remote attacker to achieve arbitrary code execution within the Chrome renderer sandbox by delivering a crafted HTML page. All desktop Chrome installations on unpatched versions are affected, exploitable via drive-by browsing without any authentication or special privileges beyond convincing the victim to visit a malicious page. No public exploit or CISA KEV listing has been confirmed at time of analysis; SSVC rates technical impact as total but exploitation as none, consistent with a low EPSS of 0.23%.
Sandbox-escape code execution in Google Chrome's Printing subsystem (all versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via a crafted HTML page, leveraging a use-after-free in the print handling path. This is a secondary exploit in a multi-stage chain: renderer compromise is a hard prerequisite, not something this bug alone provides. No public exploit code has been identified and CISA KEV does not list this vulnerability as actively exploited.
Sandbox-escaping remote code execution in Google Chrome's Payments component (versions prior to 153.0.8010.36) lets a remote attacker who successfully social-engineers a victim into visiting a crafted HTML page trigger a use-after-free and potentially run arbitrary code outside the renderer sandbox. Chromium rates the security severity 'High'; the supplied CVSS is 9.6 reflecting scope change and full CIA impact. No public exploit is identified at time of analysis and EPSS is low (0.26%, 17th percentile), and CISA SSVC records exploitation status as none.
Remote code execution in Google Chrome on macOS prior to 153.0.8010.36 stems from a use-after-free in the Payments component, letting a remote attacker who lures a user to a crafted HTML page execute arbitrary code outside the browser sandbox. The provided CVSS vector (9.6) reflects a scope-changing sandbox escape requiring user interaction (a page visit), while Chromium rated the underlying bug 'High' rather than 'Critical'. A vendor patch is available; EPSS is low (0.30%, 22th percentile) and no public exploit is identified.
Sandbox-escape remote code execution in Google Chrome's Device component on macOS (versions prior to 153.0.8010.36) allows a remote attacker to potentially run arbitrary code outside the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) reported by Google's own Chrome team; Chromium assigned it 'High' severity while the CVSS base score is 9.6. No public exploit identified at time of analysis, and EPSS is low (0.26%).
Site isolation bypass in Google Chrome's Network component prior to 153.0.8010.36 enables an attacker who has already compromised the renderer process to read and modify cross-origin data by exploiting incorrect authorization checks. The vulnerability requires a user to visit a crafted HTML page, making it a second-stage component in a renderer-compromise exploit chain. No public exploit code and no CISA KEV listing are associated with this CVE; EPSS is 0.18% (7th percentile), consistent with no observed widespread exploitation at time of analysis.
Use-after-free in V8, Chrome's JavaScript engine, enables remote code execution within the browser's renderer sandbox when a victim visits a crafted HTML page. All Chrome releases prior to 153.0.8010.36 are affected across desktop platforms. No public exploit has been identified and EPSS sits at 0.21% (12th percentile), but SSVC rates the technical impact as total, and the Chromium security team classified this as High severity.
Use-after-free in Chrome's WebPackaging component enables full sandbox escape to arbitrary code execution for attackers who have already established a foothold in the renderer process. All Chrome desktop releases prior to 153.0.8010.36 are affected. No public exploit code has been identified and EPSS is low (0.34%), but the scope-changed CVSS vector (S:C, C:H/I:H/A:H) confirms that successful exploitation fully escapes Chrome's multi-process sandbox, translating a renderer compromise into OS-level code execution.
Use-after-free in Chrome's Input component enables in-sandbox remote code execution against all Chrome versions prior to 153.0.8010.36. The vulnerability is triggered when a victim visits a crafted HTML page, requiring no authentication and no special configuration - only a single browse action. Google has rated this High severity, the patch is available in 153.0.8010.36, and no public exploit has been identified at time of analysis, with EPSS at 0.21%.
Use-after-free in Chrome's Platform component (all versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a crafted HTML page. The Chromium team rated this 'High' severity - consistent with the CVSS 8.8 score and distinguishing it from Critical-rated full sandbox-escape vulnerabilities addressed in the same release cycle. No public exploit code has been identified, and the EPSS score of 0.21% (12th percentile) reflects limited observed exploitation activity at this time; no CISA KEV listing exists.
DevTools injection (CWE-74) in Google Chrome prior to 153.0.8010.36 enables a remote attacker who has already compromised the renderer process to escape the Chromium sandbox and execute arbitrary code on the host system via a crafted HTML page. Chromium rated this 'High' severity; the CVSS 3.1 score of 8.3 (AC:H/S:C) accurately reflects the elevated complexity imposed by the prerequisite renderer compromise and the full scope-change impact. No public exploit code has been identified and CISA has not listed this in the KEV catalog; EPSS at 0.25% (16th percentile) confirms low current exploitation probability.
Sandbox-escaping remote code execution in Google Chrome before 153.0.8010.36 stems from improper array-index validation (CWE-129) in ANGLE, Chrome's graphics abstraction layer. A remote attacker who lures a victim to a crafted HTML page can potentially corrupt memory and execute arbitrary code outside the renderer sandbox. Chromium rates this 'High'; no public exploit is identified at time of analysis and EPSS is low (0.21%).
Remote code execution outside the browser sandbox affects Google Chrome versions prior to 153.0.8010.36 through a use-after-free flaw in the Web Authentication (WebAuthn) component. A remote attacker who lures a victim to a crafted HTML page can corrupt memory and execute arbitrary code with the privileges of the browser process, escaping the renderer sandbox (scope change). No public exploit has been identified at time of analysis and EPSS is low (0.34%), but the sandbox-escape RCE nature and Chrome's enormous install base make prompt patching important.
Remote code execution in Google Chrome's ANGLE graphics component on Windows (versions prior to 153.0.8010.36) allows a remote attacker to trigger an out-of-bounds write and potentially execute arbitrary code outside the browser sandbox via a crafted HTML page. Rated Chromium 'High' with a CVSS of 9.6 reflecting a scope-changing sandbox escape, though exploitation requires the victim to load malicious web content. No public exploit identified at time of analysis, and EPSS is low (0.21%), consistent with CISA SSVC scoring exploitation as 'none'.
Out-of-bounds read in ANGLE, Chrome's cross-platform graphics abstraction layer, enables sandbox escape and potential remote code execution on the host system for Chrome versions prior to 153.0.8010.36. This is a staged, second-phase exploit: an attacker must first compromise the renderer process through a separate vulnerability before leveraging this ANGLE flaw to break out of Chrome's sandbox via a crafted HTML page. No public exploit has been identified and no CISA KEV listing exists; EPSS at 0.21% (12th percentile) reflects minimal observed exploitation activity at time of analysis.
Backend connection hijacking in Traefik reverse proxy (2.11.0 through 2.11.56 and 3.0.0 through 3.7.12) lets an unauthenticated remote client impersonate another user over HTTP/3. Because the HTTP/3 entrypoint never calls service.AddTransportOnContext, the kerberosRoundTripper falls back to a shared backend transport instead of one bound to each frontend connection, so when a backend uses connection-bound NTLM or Negotiate authentication with keep-alive, an unrelated client can reuse a backend connection already authenticated for a victim, read the victim's data, and act as the victim without ever obtaining their credentials. No public exploit is identified at time of analysis, though the fix PR ships a regression test that effectively demonstrates the flaw.
Traefik's header-security defenses (aliasHeadersStrategy, underscoreHeadersStrategy, forwardedHeaders) inspect req.Header but not req.Trailer, allowing unauthenticated clients on versions 3.2.0 through 3.7.12 to smuggle security-sensitive header values through HTTP/1.1 chunked trailers or HTTP/2 trailers. When retry or buffering middleware is active in the routing chain, attacker-controlled trailer values become accessible before the request is cloned for the backend; backends that merge trailers into their header namespace then receive the spoofed values, bypassing Traefik's documented delete or reject behavior. No public exploit code has been identified and this CVE is not in CISA KEV, but the impact on identity and routing integrity at the backend is classified high by the CVSS 4.0 subsequent-system metrics.
Container escape in crun >= 1.29, when built with libkrun and started rootful with passt networking (krun.use_passt), allows an attacker who controls the container image to execute arbitrary code with host root privileges. This is a regression introduced in crun 1.29, meaning environments that recently upgraded are at risk while those on earlier versions are not. No public exploit code or CISA KEV listing has been identified at time of analysis, but successful exploitation yields full host compromise via container escape.
Template injection in Velociraptor's notebook backup restoration pipeline allows a low-privileged NOTEBOOK_EDITOR user to execute arbitrary VQL queries at elevated server-level permissions. The daily backup feature - enabled by default - captures notebook cell content verbatim; when an administrator later restores the backup, that content is interpolated into a Go template without ACL enforcement, breaking the privilege boundary between analyst and server roles. No public exploit has been identified at time of analysis, but the chained attack path (plant payload, wait for restore) represents a credible insider or compromised-analyst escalation vector against DFIR infrastructure.
Privilege escalation in Rapid7 Velociraptor lets any user permitted to schedule client monitoring artifacts run otherwise-restricted artifacts - including Linux.Sys.BashShell - to execute arbitrary commands on managed endpoints. The server enforced the EXECVE permission for scheduling command-execution artifacts through normal collection, but applied no equivalent permission or CLIENT_EVENTS-type check on the client monitoring path, so a low-privileged operator can bypass the gate entirely. No public exploit identified at time of analysis, though the upstream fix (PR #4967) makes the missing check straightforward to reconstruct.
HTTP request smuggling via inconsistent request framing in Puma's native http11_parser (reported range Puma 5.0.0 through 8.0.3) allows a remote, unauthenticated attacker to desynchronize request boundaries between Puma and an upstream HTTP intermediary, enabling request hijacking, cache poisoning, or bypass of front-end access controls; the description's claim of arbitrary code execution is unverified and inconsistent with CWE-444. Exploitation is deployment-dependent: it requires a reverse proxy, CDN, or load balancer whose parsing of ambiguous Content-Length/Transfer-Encoding framing diverges from Puma's, which is why our independent assessment rates it AV:N/AC:H/PR:N/UI:N/S:C rather than the published 9.1. Risk signals are weak and conflicting - EPSS is 0.17% (6th percentile), there is no CISA KEV listing and no confirmed public exploit code, and the only third-party reference is an unverified GitHub issue - so raw severity should be discounted.
Cross-tenant IDOR in identrail's GitHub App connection-completion endpoint allows any authenticated tenant to hijack another customer's GitHub App installation and read their organization's private repositories. The flaw exists at POST /v1/workspaces/:workspace_id/projects/:project_id/github/connect/complete, where the client-supplied installation_id is accepted and persisted with no ownership verification-despite the co-located state token being rigorously bound to {TenantID, WorkspaceID, ProjectID}. Fixed in v1.0.2; no public exploit code or CISA KEV listing identified at time of analysis.
Arbitrary code execution in Joker (the Clojure/ClojureScript linter) before v1.8.2 allows an attacker who controls files within a repository to execute arbitrary Clojure code on any developer or CI runner that lints that repository. The linter's directory-walking behavior automatically located and executed project-local `.jokerd/linter.*` files before processing any source file, treating attacker-controlled repository content as trusted configuration. Because editor integrations and CI pipelines commonly invoke `joker --lint` automatically on checked-out code, this creates a reliable developer-toolchain attack surface. No public exploit or CISA KEV listing has been identified; vendor-confirmed fix is available in v1.8.2.
A double-free in the CalDAV calendar worker of Cyrus IMAP before 3.12.4 lets an authenticated calendar user crash that worker by sending a WebDAV PATCH request carrying PATCH-ACTION="BYPARAM@..." against a calendar resource that holds two or more properties of the matched kind. The vulnerability is reachable only with valid credentials and with the CalDAV/calendar component enabled (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H, CWE-415), and the assessed outcome is a worker crash/restart rather than data disclosure or code execution. No public exploit code has been identified and EPSS is low at 0.22% (12th percentile); CISA SSVC rates exploitation as 'none' and the issue as not automatable, so this is a bounded availability bug rather than a critical-priority one.
The krb5 crypto subsystem in the Linux kernel fails to zero derived Kerberos key material before freeing memory buffers, leaving sensitive cryptographic keys resident in freed slab allocator objects. Both `crypto_krb5_prepare_encryption()` and `crypto_krb5_prepare_checksum()` call plain `kfree()` instead of the security-aware `kfree_sensitive()` wrapper, which would first zero the allocation. Systems using Kerberos-authenticated kernel services - primarily NFSv4 with sec=krb5 or CIFS/SMB with Kerberos - on kernel versions from commit 3936f02b through the stable fixes are affected; no public exploit or active exploitation has been identified.
Unauthorized cryptographic hardware access in KVM for s390 (IBM Z) nested virtualization allows a low-privileged nested guest to access AP queues (hardware crypto devices) that were explicitly revoked from its allocation. When the KVM VSIE subsystem shadows a format0 APCB (Adjunct Processor Control Block) from a crycb type 0 or 1 structure, it only copies bits 0-63 but leaves bits 64-255 unchanged from whatever stale state existed in the vsie shadow page. A nested (L2) guest exploiting this retains access to cryptographic devices beyond those granted by the host hypervisor, potentially exposing cryptographic keys and operations belonging to other workloads. No public exploit has been identified at time of analysis and no CISA KEV listing exists.
Use-after-free in the Linux kernel Bluetooth ISO stack allows an adjacent unauthenticated attacker to corrupt kernel memory and potentially execute arbitrary code. The flaw is a race condition in iso_conn_ready(): when a BIS listener socket is concurrently closed while an incoming Bluetooth Isochronous connection is being processed, a child socket is allocated that holds a dangling pointer to the now-freed parent socket, which is later dereferenced during disconnect via iso_chan_del() and bt_accept_unlink(). Patches are available across multiple stable kernel branches (6.12.109, 7.2.4, 6.18.50, and 7.3-rc1); no public exploit code or active exploitation has been identified at time of analysis.
Use-after-free in zstd-jni versions 1.3.8-4 through 1.5.7-13 allows callers to invoke setDict, setLongMax, setLevel, and setRefMultipleDDicts on already-closed stream objects, writing through freed native (JNI) pointers into arbitrary JVM memory. The root cause is missing closed-state validation in stream classes such as BaseZstdBufferDecompressingStreamNoFinalizer and ZstdInputStreamNoFinalizer, meaning the JNI layer operates on native context structures that have already been released. Exploitation can corrupt unrelated heap objects or terminate the JVM process entirely. No public exploit code or CISA KEV listing is identified at time of analysis.
Use-after-free in zstd-jni versions 1.3.8-4 through 1.5.7-13 allows attackers to trigger silent data corruption or JVM crashes by closing a Zstandard dictionary after it has been associated with a stream or context. The library's locking design released the dictionary's shared lock immediately after the load call, leaving the stream holding a native pointer to freed memory; subsequent read or write operations on that stream then access freed native heap, producing undefined behavior at the JVM/native boundary. No public exploit has been identified at time of analysis, and a patched release (v1.5.7-14) is available with two upstream commits.
Out-of-bounds memory access in zstd-jni versions 1.3.3-1 through 1.5.7-13 enables unauthenticated network-accessible attackers to crash the JVM by supplying crafted sample-size arrays to the Zstd.trainFromBufferDirect dictionary-training API. The native C implementation (jni_zdict.c) failed to sum caller-supplied sample lengths against the DirectBuffer's actual capacity before iterating, allowing the native code to walk past the buffer allocation boundary and trigger a hard JVM termination. A patched release (v1.5.7-14) is available; no public exploit has been identified at time of analysis.
Out-of-bounds memory reads in zstd-jni versions 1.1.1 through 1.5.7-13 allow unauthenticated remote attackers to crash the JVM or extract arbitrary frame-size data from unintended memory regions by supplying crafted Zstandard-compressed input with negative or integer-overflowing offset values. Three JNI native methods - findDirectByteBufferFrame, decompressedDirectByteBuffer, and getDirectByteBufferFrame - perform 32-bit signed bounds checks without first validating that src_offset or src_size are non-negative, allowing values near Integer.MIN_VALUE to pass the comparison and drive native code to read unmapped memory. The CVSS 4.0 score of 8.8 reflects a high availability impact (JVM termination) and limited confidentiality impact; no public exploit or KEV listing has been identified at time of analysis.
Heap out-of-bounds write in VLC Media Player 3.0.0 through 3.0.23 allows a local attacker to corrupt memory by tricking a user into opening a crafted PNG file with attacker-controlled dimensions. The root cause is a 32-bit integer overflow in AllocatePicture() where plane pitch-times-lines multiplication wraps before widening to the size_t accumulator, causing both overflow guards to pass on the already-corrupted value; aligned_alloc then reserves a small wrapped buffer while the PNG decoder writes full-dimension scanlines past its end. No public exploit has been identified at time of analysis, and EPSS indicates 0.30% exploitation probability over the next 30 days.
Regular expression denial of service in GitPython before 3.1.60 allows unauthenticated remote attackers to exhaust server CPU resources by supplying a crafted commit with a malformed author or committer field. The vulnerable regex Actor.name_email_regex exhibits quadratic backtracking when processing an unterminated angle bracket in the author string, stalling affected processes for over two minutes per commit access. Any application that reads attacker-influenced git repositories using GitPython is exposed; no public exploit or active exploitation (CISA KEV) has been identified at time of analysis.
Argument injection in GitPython 3.1.59's high-level diff API allows low-privileged remote attackers to read arbitrary filesystem paths by passing the unsanitized `--no-index` flag to the underlying git diff command. By chaining `--no-index` with the `-I`/`--ignore-matching-lines` regex filter, an attacker can construct a content-dependent Boolean oracle - issuing repeated queries that distinguish between regex match and mismatch responses to recover single-line secrets from local files. No active exploitation has been confirmed (not in CISA KEV), but the technique is deterministic and requires only authenticated API access. Patch-upgraded version 3.1.60 is available.
Arbitrary code execution in GitPython before 3.1.60 is possible when a victim application calls index.commit() on an attacker-controlled repository. The root cause is insufficient validation of the git directory location: GitPython trusts tracked files such as gitdir, commondir, and HEAD to resolve the effective git directory, allowing a crafted repository to redirect that resolution to an attacker-controlled path containing a malicious pre-commit hook. No public exploit has been identified at time of analysis, but the attack is realistic in any Python-based DevOps pipeline, CI/CD system, or tooling that opens and commits to externally sourced repositories.
Out-of-bounds read in zstd-jni versions 1.2.0 through 1.5.7-13 allows attackers who can supply dictionary constructor parameters to crash the JVM and potentially read limited native heap memory. The ZstdDictCompress constructor passed unvalidated offset and length values directly to the C JNI layer, where out-of-range values cause the native code to read beyond the allocated Java heap array. No CISA KEV listing or public exploit has been identified; the CVSS 4.0 score of 8.8 reflects high availability impact via reliable JVM crash and limited confidentiality exposure from native heap reads.
Plaintext recovery and content forgery in OpenIDC/cjose 0.6.1 through 0.6.2.5 occurs because the library zero-fills the content-encryption key (CEK) instead of randomizing it whenever a JWE is built with an AES-CBC-HMAC enc (A128CBC-HS256/A192CBC-HS384/A256CBC-HS512) and a key-management algorithm that generates a fresh CEK. Every affected ciphertext is therefore encrypted and authenticated under an all-zero, publicly known key, so anyone who obtains the JWE can decrypt it and forge or modify its contents. Fixed in 0.6.2.6; no public exploit identified at time of analysis, but the flaw is trivially demonstrable and confirmed by the vendor GitHub Security Advisory.
Heap buffer overflow in OpenIDC/cjose versions prior to 0.6.2.5 allows a remote unauthenticated attacker to corrupt process heap memory by submitting a crafted JWE token with an oversized `encrypted_key` segment targeting the AES Key Wrap decryption path. The `cjose_jwe_import()` and `cjose_jwe_decrypt()` functions are pre-authentication entry points that accept fully attacker-controlled input, making every application that decrypts AES-KW JWEs with this library directly reachable. Impact ranges from a reliable denial of service (process crash) to potential memory-corruption-based code execution depending on heap layout and allocator behavior. No public exploit has been identified at time of analysis, but the patch commit confirms the exact boundary condition and includes a regression test demonstrating the overflow trigger.
Heap-based buffer overflow in Google Chrome's WebRTC component (all versions prior to 153.0.8010.36) enables a remote unauthenticated attacker to potentially execute arbitrary code within the Chrome renderer sandbox by luring a target to a crafted HTML page. The vulnerability is classified CWE-122 and carries a CVSS base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); however, Chromium's own internal severity rating is 'Low,' which is notably discordant and implies that exploitation is constrained to within-sandbox code execution rather than full OS compromise. No public exploit code and no CISA KEV listing have been identified at the time of analysis.
Incorrect authorization in the Extensions component of Google Chrome before 153.0.8010.36 allows a remote attacker to bypass system access restrictions and reach a privileged internal page by luring a victim to a crafted HTML page. Google credits its own team with discovery, and a fixed build is available; no public exploit has been identified at time of analysis, and Chromium rated the underlying issue only Low severity despite the 9.8 NVD score.
Race-condition-triggered code execution in Google Chrome's V8 JavaScript engine (all versions prior to 153.0.8010.36) allows a remote unauthenticated attacker to execute arbitrary code inside the Chrome renderer sandbox by serving a crafted HTML page to a victim. Exploitation is constrained to the Chrome sandbox process rather than the underlying OS, which aligns with Chromium's own internal severity rating of 'Low' despite the CVSS base score of 7.5. No public exploit code or CISA KEV listing is present at time of analysis; the high attack complexity metric reflects the timing-sensitive nature of race-condition exploitation.
Improper certificate validation in Chrome's Federated Credential Management (FedCM) component — fixed in Chrome 153.0.8010.36 — lets a remote attacker who controls crafted network traffic, combined with social engineering of the victim, bypass web origin policy and expose cross-origin identity data. The flaw is a confidentiality-only issue (no integrity or availability impact) and Chrome rates it security severity Low, despite a 7.5 CVSS base score; EPSS is only 0.15% (4th percentile), it is not in CISA KEV, and no public exploit code has been identified at time of analysis. Vendor-released patch: 153.0.8010.36.
Memory corruption in V8, Chrome's JavaScript engine, allows an attacker who can get a user to install a crafted Chrome extension to execute arbitrary code confined within the Chrome sandbox, affecting all Chrome versions prior to 153.0.8010.36. Despite the CVSS 8.8 base score, Chromium's own security team rates this 'Low' severity, reflecting that exploitation is bounded by Chrome's sandbox and does not constitute a full OS-level compromise without a separate sandbox escape primitive. No public exploit code or active exploitation has been identified at time of analysis. Vendor-released patch is available.
Sandbox escape via incorrect authorization in the Chrome Updater component on Windows allows a local attacker to execute arbitrary code outside the browser's sandbox using a crafted local program. Affected versions are all Google Chrome releases prior to 153.0.8010.36 on Windows. The Chromium team rates internal severity as 'Low' - notably lower than the CVSS 8.1 score - suggesting that while the impact is high if exploited, real-world attack complexity limits practical risk. No public exploit or active exploitation has been identified at time of analysis.
Use-after-free in Google Chrome's DevTools component (versions prior to 153.0.8010.36) enables arbitrary code execution within the renderer sandbox when a victim is socially engineered into visiting a crafted HTML page. The CVSS score of 8.8 reflects full C/I/A impact, but Chromium's own internal severity classification of 'Low' signals that exploitation is sandboxed - OS-level compromise requires an additional chained sandbox escape. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Remote code execution in Google Chrome's DevTools component before 153.0.8010.36 stems from a use-after-free (CWE-416) that, per the advisory, allows a crafted HTML page to execute arbitrary code outside the browser sandbox. All desktop Chrome builds prior to the fixed stable release are affected; the flaw was reported internally by the Chrome team, is fixed in the stable channel, and has no public exploit identified at time of analysis. Notably, the assigned CVSS is 9.6 (Critical) while Chromium itself rated the security severity only 'Low', a significant conflict discussed below.
Server-side request forgery in Google Chrome for Mobile (builds prior to 153.0.8010.36) allows a remote attacker who successfully social-engineers a victim into opening a crafted HTML page to induce the browser to issue requests that bypass system access restrictions. Exploitation is not a drive-by: user interaction is mandatory, and the authoritative reassessment scores this as CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N (confidentiality/access-restriction bypass only), so the widely circulated 9.8 vector overstates the real-world impact; Chromium itself rates the issue Low. EPSS is 0.18% (7th percentile) and no public exploit identified at time of analysis, while a vendor-released patch (153.0.8010.36) is already available.
Sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The flaw resides in the Storage component's incorrect reference resolution (CWE-706), making this a second-stage exploit that chains with a separate renderer compromise to achieve full sandbox breakout. No public exploit has been identified at time of analysis, and the fix is available in the stable channel release 153.0.8010.36.
Sandbox-escaping remote code execution in Google Chrome's WebPackaging component affects all desktop versions prior to 153.0.8010.36. A use-after-free (CWE-416) reachable from a crafted HTML page can let a remote attacker potentially execute arbitrary code outside the renderer sandbox with no authentication, requiring only that the victim visit a malicious page. No public exploit has been identified at time of analysis; Chromium's own internal triage rated the security severity 'Low', which sits in notable tension with the 9.6 CVSS assigned to the record.
Remote code execution in Google Chrome on iOS before 153.0.8010.36 stems from a use-after-free in the Sharing component (CWE-416), letting a remote attacker who lures a victim to crafted network content execute arbitrary code outside the browser sandbox. Google has shipped a patched Chrome build; no public exploit is identified at time of analysis, and Google/Chromium rated the underlying bug 'Medium' severity even though the assigned CVSS base score is 9.6.
Remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the Passwords component that, when triggered via crafted UI interaction and social engineering, can let a remote attacker escape the renderer sandbox and run arbitrary code. All Chrome desktop builds before the 153.0.8010.36 stable release are affected. No public exploit identified at time of analysis, and no EPSS or KEV data was provided; note that Google's Chromium team rated the underlying bug only 'Medium' severity, which sits in tension with the supplied CVSS 9.6.
Sandbox-escaping remote code execution in Google Chrome's Aura windowing layer affects all desktop builds prior to 153.0.8010.36. A remote attacker who lures a victim to a crafted HTML page can trigger a use-after-free (CWE-416) and potentially execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the fix ships in the stable-channel desktop update.
Out-of-bounds write in the Media component of Google Chrome before 153.0.8010.36 allows a remote attacker to potentially execute arbitrary code outside the browser's renderer sandbox by luring a victim to a crafted HTML page. The scope-changing memory-corruption bug carries a CVSS of 9.6 despite Chromium's own 'Medium' severity rating, and a vendor patch is available. There is no public exploit identified at time of analysis.
Remote code execution in Google Chrome on Windows prior to 153.0.8010.36 arises from a type-confusion bug in the browser's Rust code, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Google shipped a fixed build via the Stable channel, and the flaw was reported internally by the Chrome team. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though sandbox-escape memory-corruption bugs in Chrome are historically high-value exploitation targets.
Sandbox-escape remote code execution affects Google Chrome on macOS prior to 153.0.8010.36, where an improper quantity-validation flaw (CWE-1284) in Tint, the WebGPU/WGSL shader compiler in Chromium's Dawn graphics stack, lets a crafted HTML page break out of the renderer sandbox. A remote attacker who lures a victim to a malicious web page can potentially execute arbitrary code with the privileges of the browser process on the host. Google reports a fix is shipped; there is no public exploit identified at time of analysis, and Chromium internally rated the issue Medium severity despite the high provided CVSS.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from a numeric truncation error in the Media component, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. The vendor patch is available via the September 2026 stable-channel update; no public exploit is identified at time of analysis. Note a signal conflict: Chromium rated this 'Medium' severity while the supplied CVSS base score is 9.6 Critical.
Remote code execution in Google Chrome for macOS prior to 153.0.8010.36 stems from a use-after-free in the Extensions component, letting a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw carries a CVSS 9.6 (scope-changed, network vector with user interaction), though Chromium's own security team rated it 'Medium'. No public exploit has been identified at time of analysis, and the fix is available in the stable channel.
FileAPI improper input validation in Google Chrome prior to 153.0.8010.36 enables an attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code on the underlying host system. The flaw, tracked in Chromium issue 532957878, was addressed in the September 2026 stable channel release. With an EPSS of 0.30% and no confirmed active exploitation, this functions as a second-stage sandbox-escape primitive rather than a standalone remote attack.
Use-after-free in Chrome's V8 JavaScript engine allows a remote attacker who can socially engineer a victim into installing a crafted Chrome extension to execute arbitrary code within the browser's renderer sandbox, affecting all Chrome versions prior to 153.0.8010.36. The vulnerability is constrained to in-sandbox execution - it does not constitute a standalone sandbox escape - which aligns with the S:U CVSS metric and Chromium's internal 'Medium' severity rating despite the 8.8 base score. No public exploit code or active exploitation has been identified at time of analysis, and Google has shipped a patch in the stable channel.
Missing authorization in the Extensions subsystem of Google Chrome prior to 153.0.8010.36 enables a remote attacker to obtain sensitive browser information by delivering a crafted Chrome extension that bypasses access control checks. The vulnerability is classified CWE-862 (Missing Authorization), meaning the runtime fails to enforce proper permission boundaries between extension capabilities and protected browser data. No public exploit code or active exploitation has been identified at time of analysis; Chromium's own internal severity rating of 'Medium' reflects practical exploitation barriers not fully captured by the NVD CVSS 7.5 High rating.
Use-after-free in Google Chrome's DevTools component prior to 153.0.8010.36 enables a local attacker to escape the browser sandbox and execute arbitrary code at the host OS level via a crafted local program. Chromium's own severity rating is 'Medium', reflecting the local access prerequisite, while the CVSS 8.1 score captures the high-impact sandbox-escape outcome once exploitation succeeds. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the EPSS score (0.12%, 2nd percentile) confirms low observed exploitation probability.
Sandbox escape via incorrect authorization in the Views component of Google Chrome on Windows (versions prior to 153.0.8010.36) enables arbitrary code execution outside the browser sandbox. Exploitation requires an attacker to first compromise the renderer process and then leverage social engineering to induce user interaction with a crafted HTML page. No public exploit or KEV listing exists at time of analysis; Chromium's own severity rating of Medium contrasts with the CVSS 8.3 score, reflecting the difficult two-stage attack chain.
Sandbox escape via improper initialization (CWE-665) in Google Chrome's Views UI framework on Windows, prior to version 153.0.8010.36, can lead to arbitrary code execution outside the browser sandbox. The attack is chained: an adversary must first compromise the renderer process through a separate vulnerability, then leverage social engineering to trigger the Views initialization flaw, elevating from renderer-level code execution to full host OS access. No public exploit code has been identified and EPSS sits at 0.28% (20th percentile), consistent with the multi-step prerequisite bar, though the C:H/I:H/A:H impact profile warrants prompt patching.
Sandbox-escaping remote code execution in Google Chrome's Browser process on Windows (all versions prior to 153.0.8010.36) stems from a use-after-free flaw. A remote attacker who lures a victim into opening a crafted HTML page can corrupt reclaimed heap memory in the privileged browser process and execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the vendor has shipped a fixed stable build.
Uncontrolled search path element in Chrome's Windows CredentialProvider component (CWE-427) enables a local attacker to execute arbitrary code outside the browser sandbox on Windows systems running Chrome prior to 153.0.8010.36. The flaw is a DLL or executable search-order hijacking issue: Chrome's CredentialProvider resolves a dependency by searching an attacker-controllable path, allowing a malicious local program to intercept and execute in place of a legitimate component, with the result escaping Chrome's sandbox entirely. No public exploit code or CISA KEV listing has been identified at time of analysis.
Site isolation bypass in Google Chrome's FileSystem component allows a remote attacker who has already achieved renderer process compromise to escape cross-origin boundaries via a crafted PDF file. Affected versions are all Chrome releases prior to 153.0.8010.36 on desktop platforms. The vulnerability (CWE-863, Incorrect Authorization) enables the attacker to read or modify data belonging to other origins, undermining Chrome's core sandboxing guarantee. No public exploit or active exploitation (CISA KEV) has been identified; EPSS is 0.16%, consistent with the SSVC 'Exploitation: none' rating.
Incorrect authorization in Google Chrome's Permissions subsystem before version 153.0.8010.36 enables remote attackers to exfiltrate sensitive browser information through a crafted Chrome extension that requires social engineering to install. The flaw (CWE-863) causes Chrome's permission brokering layer to incorrectly authorize an extension's access to protected browser data, resulting in high-confidence confidentiality impact with no integrity or availability consequence. No public exploit has been identified and EPSS sits at 0.18%, consistent with the social-engineering prerequisite that constrains mass opportunistic exploitation.
Site isolation bypass in Google Chrome prior to 153.0.8010.36 allows a remote attacker who has already compromised the renderer process to escape Chrome's cross-site isolation boundary via a crafted file combined with social engineering. The flaw is rooted in incorrect authorization (CWE-863) within the SiteIsolation component, meaning the browser fails to properly enforce origin-based access controls once the renderer is under attacker control. Vendor-released patch 153.0.8010.36 is available; no public exploit has been identified and EPSS sits at 0.16% (6th percentile), consistent with the Chromium team's 'Medium' severity rating despite the CVSS 8.8 base score.
Sandbox-escape remote code execution in Google Chrome for Android before 153.0.8010.36 arises from an integer overflow in the GPU process, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. Fixed in the same 153.0.8010.36 Stable Channel release that addressed several other GPU/media memory-safety bugs; no public exploit identified at time of analysis. Note the rating tension: the input CVSS is 9.6 (Critical) while Google's own Chromium severity is only Medium.
Missing authorization in the WebView component of Google Chrome on Android before 153.0.8010.36 lets a remote attacker who first tricks a user via social engineering bypass system access restrictions through crafted network traffic. The flaw is tracked as CWE-862 (missing authorization) and was reported by Google's Chrome team; a vendor patch is available. Chromium rates the security severity as Medium, EPSS is low (0.17%), and no public exploit or CISA KEV listing has been identified.
Use-after-free in Chrome's ANGLE graphics layer on Windows enables sandbox escape and arbitrary code execution when a renderer process has already been compromised. Affected versions are all Chrome releases prior to 153.0.8010.36 on Windows; exploitation requires an attacker to first compromise the renderer and then deliver a crafted HTML page triggering the ANGLE memory corruption. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.28% (20th percentile) reflects low observed exploitation probability.
Chrome's Extensions subsystem prior to 153.0.8010.36 fails to correctly enforce security policies when inputs originate from a compromised renderer process (CWE-807), enabling a two-stage sandbox escape that results in arbitrary code execution outside the Chrome sandbox on the host OS. Exploitation chains a prior renderer compromise with social engineering to bypass Extensions-mediated policy decisions. No public exploit code exists and EPSS is low (0.30%, 22nd percentile), consistent with Chromium's internal 'Medium' severity rating despite the CVSS 8.3 score - reflecting the substantial pre-condition barrier.
Heap-based buffer overflow in the WebRTC component of Google Chrome prior to 153.0.8010.36 allows a remote unauthenticated attacker to execute arbitrary code within the Chrome renderer sandbox by luring a user to a crafted HTML page. The RCE is sandbox-confined (CVSS S:U), meaning a chained sandbox-escape exploit would be needed for full host-level compromise. No public exploit or active exploitation has been identified at time of analysis, and EPSS sits at a low 0.24% (15th percentile), consistent with Chromium's own 'Medium' severity designation despite the 8.8 CVSS base score.
Sandbox-escape remote code execution in Google Chrome's Extensions component (versions prior to 153.0.8010.36) lets a remote attacker potentially run arbitrary code outside the renderer sandbox by delivering crafted network traffic. The root cause is incorrect reference resolution (CWE-706), where a name or reference is resolved to the wrong target. Google has shipped a fix; there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.20%).
Sandbox escape via confused deputy in Chrome's DataTransfer component allows an attacker who has already compromised the renderer process to execute arbitrary code outside the sandbox by directing the victim to a crafted HTML page. Fixed in Chrome 153.0.8010.36, this is classified 'Medium' severity by the Chromium team despite the CVSS 8.3 score with full scope change (S:C, C:H/I:H/A:H), reflecting that renderer pre-compromise is required. No public exploit code or CISA KEV listing exists at time of analysis, and EPSS is 0.25% (16th percentile).
Site isolation bypass in Google Chrome's ServiceWorker implementation allows a remote attacker who has already compromised the renderer process to escape cross-origin protections via a crafted HTML page. All Chrome versions prior to 153.0.8010.36 are affected. This is a chained exploit step: an attacker must first achieve renderer code execution (via a separate vulnerability), then leverage this incorrect authorization flaw to break site isolation and access data from other origins. No public exploit or CISA KEV listing exists at time of analysis.
Sandbox escape in Google Chrome's Extensions component (versions prior to 153.0.8010.36) permits an attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via crafted network traffic. The missing authorization check (CWE-862) in the Extensions subsystem fails to enforce inter-process privilege boundaries, converting a renderer-level foothold into host-level code execution. No public exploit or active exploitation has been identified; EPSS sits at 0.19%, though SSVC rates the technical impact as 'total' given successful exploitation fully bypasses Chrome's sandbox isolation.
Sandbox escape via incorrect authorization in the WebView component of Google Chrome on Android (prior to 153.0.8010.36) allows a network-based attacker to execute arbitrary code outside the Chrome renderer sandbox. Exploitation is a two-stage process: the attacker must first compromise the renderer process, then leverage the CWE-863 authorization flaw in WebView to break out of the sandbox via a crafted HTML page. No public exploit or KEV listing has been identified at time of analysis; EPSS is low at 0.30%, consistent with the complexity barrier of requiring a prior renderer compromise.
Sandbox-escape via race condition in Google Chrome's Updater component on Windows allows a local, unprivileged attacker to execute arbitrary code outside the Chrome sandbox. Affected versions are all Chrome releases for Windows prior to 153.0.8010.36, fixed in the September 2026 stable channel update. No public exploit has been identified and EPSS sits at 0.10% (1st percentile), but successful exploitation yields full C:H/I:H/A:H impact beyond the sandbox boundary. Chromium's own rating of 'Medium' reflects the high attack complexity imposed by the race condition timing requirement.
Site isolation bypass in Google Chrome's FileAPI component allows a remote attacker who has already compromised the renderer process to escape Chrome's cross-origin isolation boundary via a crafted HTML page. Affected versions are all Chrome releases prior to 153.0.8010.36. This is a second-stage exploit - the FileAPI race condition (CWE-367, TOCTOU) enables escalation from a sandboxed renderer compromise into full cross-origin data access, making it a critical link in a multi-stage sandbox escape chain. No public exploit or CISA KEV listing is identified at time of analysis; EPSS is 0.24% (16th percentile), consistent with the high complexity of the required exploit chain.
Privilege elevation in Chrome's WebUI component prior to version 153.0.8010.36 enables sandbox escape and arbitrary code execution outside the browser sandbox when the renderer process has already been compromised. This is a second-stage, chained exploit: an attacker must first achieve renderer-level code execution (e.g., via a separate renderer bug) and then leverage this WebUI flaw (CWE-250 - execution with unnecessary privileges) to break out of the sandbox. No public exploit code has been identified and no CISA KEV listing exists; SSVC rates automatable exploitation as 'no', consistent with the multi-step chain requirement.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from incorrect reference resolution in the FileSystem component, letting a remote attacker who lures a victim into visiting a crafted HTML page run arbitrary code outside the renderer sandbox. Reported by Google's own Chrome team and patched in the 2026-09 stable-channel desktop update; no public exploit is identified and SSVC lists exploitation as none, with EPSS at a modest 0.32%. Note a signal conflict: Chromium rates this 'Medium' while the assigned CVSS is 9.6, and the description requires user interaction (social engineering), so real-world risk is lower than the raw score suggests.
Sandbox escape via improper input validation in Chrome's SiteIsolation component allows an attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox. Affected versions are all Chrome releases prior to 153.0.8010.36. Exploitation requires chaining this flaw with a separate renderer compromise - an attacker must first gain control of the renderer (typically via another renderer-targeted vulnerability), then use this SiteIsolation validation flaw to break out of the sandbox and execute code in a more privileged process context. No public exploit code or active exploitation has been identified at time of analysis.
Site isolation authorization bypass in Google Chrome prior to 153.0.8010.36 allows a remote attacker who has already compromised the renderer process to escape cross-origin boundaries via a crafted HTML page. The flaw (CWE-862, Missing Authorization) resides in the SiteIsolation component, which enforces process-level separation between web origins; with that enforcement missing, a controlled renderer can access data belonging to other sites. No public exploit has been identified and EPSS sits at 0.18%, consistent with this vulnerability's role as a second-stage link in a chained browser attack rather than a standalone entry point.
Type confusion (CWE-843) in Chrome's XML processing component allows remote attackers to execute arbitrary code within the Chrome renderer sandbox by enticing a target to visit a crafted HTML page. All Chrome desktop versions prior to 153.0.8010.36 are affected across Windows, macOS, and Linux. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; the impact is further bounded by Chrome's sandbox architecture, which prevents direct OS-level code execution without a secondary sandbox-escape primitive.
Use-after-free in Chrome's Chromecast component allows remote attackers to execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. Affected are all Google Chrome releases prior to 153.0.8010.36 across desktop platforms. Exploitation is sandboxed - code execution is confined to the renderer process - but the C:H/I:H/A:H impact rating reflects full compromise of data accessible within that context. No active exploitation has been confirmed and no public proof-of-concept code is known at time of analysis.
Sandbox escape in Google Chrome's FileSystem component prior to 153.0.8010.36 stems from missing authorization checks (CWE-862), allowing arbitrary code execution outside the renderer sandbox. The attack is multi-stage: an attacker must first compromise the renderer process via a separate exploit, then serve a crafted HTML page using social engineering to trigger the authorization gap and escape the sandbox. No active exploitation is confirmed (not in CISA KEV; EPSS 0.34% at 27th percentile; SSVC exploitation: none), and the renderer pre-compromise requirement substantially limits real-world attack surface.
Sandbox-escaping remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the browser's Core component that a remote attacker can trigger through a maliciously crafted Chrome extension. Successful exploitation lets attacker-controlled code run outside the renderer sandbox with the browser process's privileges, but it requires convincing the victim to install or interact with the malicious extension (social engineering). There is no public exploit identified at time of analysis, EPSS is low (0.24%, 15th percentile), and CISA SSVC records exploitation as none, so the risk is high-impact but currently unproven in the wild.
Remote code execution in Google Chrome before 153.0.8010.36 stems from a use-after-free in the browser's Payments component, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Chromium rates the severity High, and the supplied CVSS is 9.6 reflecting the sandbox-escape scope change. EPSS is low (0.35%, 29th percentile) and no public exploit is identified at time of analysis.
Remote code execution inside the Chrome sandbox is possible in Google Chrome versions prior to 153.0.8010.36 via a use-after-free vulnerability in the V8 JavaScript engine, triggered by a specially crafted HTML page. An unauthenticated remote attacker who can lure a user to a malicious page can execute arbitrary code within the Chrome renderer process sandbox - a significant foothold even without a sandbox escape. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.21% reflects low observed exploitation activity, though V8 UAF primitives are historically attractive to threat actors.
Type confusion in V8 (CWE-843) in Google Chrome prior to 153.0.8010.36 allows a remote attacker to achieve arbitrary code execution within the Chrome renderer sandbox by delivering a crafted HTML page. All desktop Chrome installations on unpatched versions are affected, exploitable via drive-by browsing without any authentication or special privileges beyond convincing the victim to visit a malicious page. No public exploit or CISA KEV listing has been confirmed at time of analysis; SSVC rates technical impact as total but exploitation as none, consistent with a low EPSS of 0.23%.
Sandbox-escape code execution in Google Chrome's Printing subsystem (all versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via a crafted HTML page, leveraging a use-after-free in the print handling path. This is a secondary exploit in a multi-stage chain: renderer compromise is a hard prerequisite, not something this bug alone provides. No public exploit code has been identified and CISA KEV does not list this vulnerability as actively exploited.
Sandbox-escaping remote code execution in Google Chrome's Payments component (versions prior to 153.0.8010.36) lets a remote attacker who successfully social-engineers a victim into visiting a crafted HTML page trigger a use-after-free and potentially run arbitrary code outside the renderer sandbox. Chromium rates the security severity 'High'; the supplied CVSS is 9.6 reflecting scope change and full CIA impact. No public exploit is identified at time of analysis and EPSS is low (0.26%, 17th percentile), and CISA SSVC records exploitation status as none.
Remote code execution in Google Chrome on macOS prior to 153.0.8010.36 stems from a use-after-free in the Payments component, letting a remote attacker who lures a user to a crafted HTML page execute arbitrary code outside the browser sandbox. The provided CVSS vector (9.6) reflects a scope-changing sandbox escape requiring user interaction (a page visit), while Chromium rated the underlying bug 'High' rather than 'Critical'. A vendor patch is available; EPSS is low (0.30%, 22th percentile) and no public exploit is identified.
Sandbox-escape remote code execution in Google Chrome's Device component on macOS (versions prior to 153.0.8010.36) allows a remote attacker to potentially run arbitrary code outside the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) reported by Google's own Chrome team; Chromium assigned it 'High' severity while the CVSS base score is 9.6. No public exploit identified at time of analysis, and EPSS is low (0.26%).
Site isolation bypass in Google Chrome's Network component prior to 153.0.8010.36 enables an attacker who has already compromised the renderer process to read and modify cross-origin data by exploiting incorrect authorization checks. The vulnerability requires a user to visit a crafted HTML page, making it a second-stage component in a renderer-compromise exploit chain. No public exploit code and no CISA KEV listing are associated with this CVE; EPSS is 0.18% (7th percentile), consistent with no observed widespread exploitation at time of analysis.
Use-after-free in V8, Chrome's JavaScript engine, enables remote code execution within the browser's renderer sandbox when a victim visits a crafted HTML page. All Chrome releases prior to 153.0.8010.36 are affected across desktop platforms. No public exploit has been identified and EPSS sits at 0.21% (12th percentile), but SSVC rates the technical impact as total, and the Chromium security team classified this as High severity.
Use-after-free in Chrome's WebPackaging component enables full sandbox escape to arbitrary code execution for attackers who have already established a foothold in the renderer process. All Chrome desktop releases prior to 153.0.8010.36 are affected. No public exploit code has been identified and EPSS is low (0.34%), but the scope-changed CVSS vector (S:C, C:H/I:H/A:H) confirms that successful exploitation fully escapes Chrome's multi-process sandbox, translating a renderer compromise into OS-level code execution.
Use-after-free in Chrome's Input component enables in-sandbox remote code execution against all Chrome versions prior to 153.0.8010.36. The vulnerability is triggered when a victim visits a crafted HTML page, requiring no authentication and no special configuration - only a single browse action. Google has rated this High severity, the patch is available in 153.0.8010.36, and no public exploit has been identified at time of analysis, with EPSS at 0.21%.
Use-after-free in Chrome's Platform component (all versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a crafted HTML page. The Chromium team rated this 'High' severity - consistent with the CVSS 8.8 score and distinguishing it from Critical-rated full sandbox-escape vulnerabilities addressed in the same release cycle. No public exploit code has been identified, and the EPSS score of 0.21% (12th percentile) reflects limited observed exploitation activity at this time; no CISA KEV listing exists.
DevTools injection (CWE-74) in Google Chrome prior to 153.0.8010.36 enables a remote attacker who has already compromised the renderer process to escape the Chromium sandbox and execute arbitrary code on the host system via a crafted HTML page. Chromium rated this 'High' severity; the CVSS 3.1 score of 8.3 (AC:H/S:C) accurately reflects the elevated complexity imposed by the prerequisite renderer compromise and the full scope-change impact. No public exploit code has been identified and CISA has not listed this in the KEV catalog; EPSS at 0.25% (16th percentile) confirms low current exploitation probability.
Sandbox-escaping remote code execution in Google Chrome before 153.0.8010.36 stems from improper array-index validation (CWE-129) in ANGLE, Chrome's graphics abstraction layer. A remote attacker who lures a victim to a crafted HTML page can potentially corrupt memory and execute arbitrary code outside the renderer sandbox. Chromium rates this 'High'; no public exploit is identified at time of analysis and EPSS is low (0.21%).
Remote code execution outside the browser sandbox affects Google Chrome versions prior to 153.0.8010.36 through a use-after-free flaw in the Web Authentication (WebAuthn) component. A remote attacker who lures a victim to a crafted HTML page can corrupt memory and execute arbitrary code with the privileges of the browser process, escaping the renderer sandbox (scope change). No public exploit has been identified at time of analysis and EPSS is low (0.34%), but the sandbox-escape RCE nature and Chrome's enormous install base make prompt patching important.
Remote code execution in Google Chrome's ANGLE graphics component on Windows (versions prior to 153.0.8010.36) allows a remote attacker to trigger an out-of-bounds write and potentially execute arbitrary code outside the browser sandbox via a crafted HTML page. Rated Chromium 'High' with a CVSS of 9.6 reflecting a scope-changing sandbox escape, though exploitation requires the victim to load malicious web content. No public exploit identified at time of analysis, and EPSS is low (0.21%), consistent with CISA SSVC scoring exploitation as 'none'.
Out-of-bounds read in ANGLE, Chrome's cross-platform graphics abstraction layer, enables sandbox escape and potential remote code execution on the host system for Chrome versions prior to 153.0.8010.36. This is a staged, second-phase exploit: an attacker must first compromise the renderer process through a separate vulnerability before leveraging this ANGLE flaw to break out of Chrome's sandbox via a crafted HTML page. No public exploit has been identified and no CISA KEV listing exists; EPSS at 0.21% (12th percentile) reflects minimal observed exploitation activity at time of analysis.