Suse
Monthly
The Linux kernel ims-pcu USB driver exposes sysfs device attributes on the secondary data interface in addition to the intended primary control interface, allowing local users to trigger kernel crashes or undefined behavior by accessing those attributes on the data interface, which lacks the descriptors and internal state the driver requires. Affected systems must have an IMS Passenger Control Unit USB device physically connected and run a kernel version between commit 204d18a7a0c67352857dee1bbac517ed63f01d8e and the respective fix commits. No public exploit code exists, and the EPSS score of 0.17% (6th percentile) reflects the extreme hardware rarity required for exploitation; no CISA KEV listing exists.
Corrupted xattr entry handling in the Linux kernel's f2fs filesystem driver exposes local users to kernel memory disclosure and potential corruption. When f2fs_listxattr() processes a crafted or corrupted filesystem image containing malformed extended attribute entries that fall outside the valid xattr storage area, the kernel previously returned a partial success result without validating entry boundaries. This flaw affects a wide range of kernel stable branches from the commit introducing the bug (688078e7f36c293dae25b338ddc9e0a2790f6e06) through the backported fixes. No public exploit code exists and EPSS is 0.18% (7th percentile), indicating low exploitation probability at time of analysis.
HTTP method confusion in grpc-ecosystem's grpc-gateway v2.28.0 lets remote clients bypass method-based access controls enforced by an upstream WAF or reverse proxy. The ServeMux honors a client-supplied X-HTTP-Method-Override header on POST requests carrying Content-Type application/x-www-form-urlencoded, rewriting the request method to any attacker-chosen verb (e.g. DELETE, PUT) before routing, so a proxy that only permits POST is fooled while the gateway dispatches to a restricted handler. No public exploit identified at time of analysis, and EPSS is low (0.18%), but the upstream fix is confirmed via commit 72123cd4.
Use-after-free in Redis's TLS pending-data handler (`tlsProcessPendingData()`) enables remote attackers to potentially execute arbitrary commands at the privilege level of the Redis server process. The flaw spans all major active Redis release lines and is confirmed fixed in versions 6.2.24, 7.2.16, 7.4.11, 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1 - exploitation is gated on TLS being explicitly configured, which is non-default. A public proof-of-concept exists; SSVC rates technical impact as total but automation as not feasible, and the vulnerability is not currently listed in CISA KEV.
Grafana Alloy's prometheus.operator.servicemonitors component exposes an arbitrary local file read path that leads to credential theft and potential Kubernetes privilege escalation. Any Kubernetes user with ServiceMonitor create or modify rights in a namespace watched by Alloy can point the bearerTokenFile field at any file accessible to the Alloy process - most critically Alloy's own projected Kubernetes service account token - and receive that file's contents exfiltrated via HTTP Bearer token to an attacker-controlled scrape endpoint. The CVSS 7.7 Scope:Changed rating correctly reflects that successful exploitation transcends the compromised namespace, potentially granting the attacker cluster-level API access commensurate with Alloy's own RBAC permissions. No public exploit has been identified at time of analysis.
Path traversal in NLTK through version 3.10.3 allows attackers who control caller-supplied file paths to read or write files outside the boundaries enforced by the pathsec sandbox module. The affected APIs - TransitionParser, AveragedPerceptron, PerceptronTagger, and maxent parameter loading - perform raw file I/O directly on caller-provided paths without routing through pathsec enforcement, undermining the intended access control boundary. The CVSS 4.0 score of 8.3 reflects high confidentiality impact; no public exploit code or CISA KEV listing has been identified at time of analysis.
CPU-pinning denial of service in NLTK's PorterStemmer component (versions ≤ 3.10.2) allows a remote unauthenticated attacker to exhaust a CPU core for seconds to minutes by submitting a single crafted token. The root cause is quadratic algorithmic complexity: _is_consonant() re-walks trailing 'y' characters on every invocation, and _measure() calls it once per stem position, resulting in O(n²) processing time. Any service that passes untrusted text through PorterStemmer.stem() without input length validation is vulnerable; a ~20-50 KB payload of repeated 'y' characters followed by a matching suffix such as 'ness' is sufficient to trigger the condition. No public exploit code is identified at time of analysis, but the attack primitive is trivially constructable from the public description. Fix is available in NLTK 3.10.3.
Heap-based buffer overflow in FFmpeg's libswscale library enables unauthenticated remote attackers to crash media-processing applications via a crafted input file. The vulnerable function ff_sws_alphablendaway, invoked during alpha channel compositing in git-master commit 722a217, mishandles attacker-controlled input and corrupts heap memory, producing a Denial of Service. No active exploitation is confirmed - EPSS stands at 0.15% (5th percentile) with no CISA KEV listing - indicating this is currently a crash risk rather than a weaponized threat.
NULL pointer dereference in FFmpeg development snapshot N-122528-gdd2976b9e1 crashes the FFmpeg process when parsing a maliciously crafted video file via the get_min_buffer_size function in libswscale/slice.c. Any application or automated pipeline using this FFmpeg build to process untrusted video input is exposed to unauthenticated remote denial of service, as confirmed by the AV:N/AC:L/PR:N/UI:N CVSS vector. No public exploit code exists at time of analysis, and EPSS at 0.15% (4th percentile) signals low current threat-actor activity.
Heap-based buffer overflow in the Dia diagram editor's WPG file importer allows arbitrary code execution or process crash when a user opens a crafted WPG file. The WPG color palette buffer is allocated for exactly 256 entries (768 bytes), but the COLORMAP record parser fails to validate that the supplied start index (i16) or total entry count (iNum16) stay within that bound, allowing a malicious file to drive fread() to write beyond the heap allocation. Affecting all Dia versions on the upstream master branch through at least 2026-08-21, no public exploit or patch version has been confirmed at time of analysis, though the description provides sufficient detail to construct proof-of-concept input.
Out-of-bounds memory write in the Linux kernel's ASoC lpass-tx-macro audio codec driver allows a local low-privileged user to corrupt kernel memory via misconfigured ALSA enum kcontrol access, with potential for privilege escalation. The driver's get and put handlers for DEC0-DEC7 MODE controls incorrectly access the 8-byte integer union field instead of the 4-byte enumerated union field, writing 4 bytes beyond the intended boundary on 64-bit systems. No public exploit code has been identified at time of analysis, but the pattern mirrors two previously fixed sibling drivers (rx-macro, va-macro), confirming the root cause is well-understood.
PMD huge page mapping boundary violation in the Linux kernel's drm/shmem_helper subsystem allows local users with low privileges to trigger out-of-bounds memory mappings via the DRM ->huge_fault handler. The handler installs PMD-level Transparent Huge Page mappings without verifying they remain within Virtual Memory Area boundaries, triggering a VM_BUG_ON_VMA() assertion when the mapping subsequently reaches copy_pmd_range() during fork or remap operations. Patches have been committed to Linux 7.1.10 and 7.2 stable branches; no public exploit has been identified at time of analysis.
Out-of-bounds memory access in the Linux kernel's cs40l50-vibra haptic driver allows a local low-privileged user to read or write beyond allocated kernel buffers by submitting a crafted force-feedback effect via EVIOCSFF ioctl. The driver's cs40l50_add() function fails to validate user-supplied custom_len before dereferencing custom_data[0] and custom_data[1], and an integer sign-wrap in bank type handling permits negative array indexing into vib->dsp.banks[]. Three distinct code paths are exploitable: zero-length allocation returning ZERO_SIZE_PTR, single-word allocation followed by a two-word read, and s16 overflow enabling out-of-bounds bank array access. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV.
Heap buffer overflow in the Linux kernel synaptics-rmi4 driver allows local low-privileged users to overwrite kernel heap memory by exploiting stale state in the F54 diagnostics function. Affected systems must have Synaptics RMI4 touchpad hardware present and the driver loaded; exploitation involves manipulating V4L2 buffer sizes to trigger the overflow after an error condition leaves f54->report_size containing a stale value from a prior successful operation. Patches are available across all supported stable branches; no public exploit or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Out-of-bounds memory write in the Linux kernel's synaptics-rmi4 input driver allows a local attacker with access to a malicious or malfunctioning RMI4 touchpad device to corrupt kernel memory, potentially enabling privilege escalation or information disclosure. The root cause is a mismatch between the F54 report buffer allocation size (derived from F54 electrode counts) and the transfer size computed from F55 electrode counts - both sourced directly from device queries with no cross-validation. Vendor patches are confirmed across multiple stable kernel branches; no public exploit or CISA KEV listing has been identified at time of analysis.
Heap buffer overflow in the Linux kernel's synaptics-rmi4 driver allows a local low-privileged user to trigger memory corruption by issuing VIDIOC_S_INPUT while the V4L2 diagnostic queue is actively streaming. The F54 function allocates V4L2 buffers sized to the report type at stream start; switching the input mid-stream to a larger report type overflows those buffers, enabling potential privilege escalation to root. Patches have been released across all active stable kernel branches; no public exploit code or CISA KEV listing has been identified at time of analysis.
Incorrect error-path logic in the Linux kernel's Qualcomm Crypto Engine (QCE) driver allows a local attacker with low privileges on Qualcomm SoC-based hardware to potentially trigger memory corruption via a use-after-free or improper resource release condition. The flaw resides in `devm_qce_register_algs`, where a failed `ops->register_algs()` call causes the cleanup loop to repeatedly invoke `ops->unregister_algs()` on the failed slot rather than iterating over previously successfully registered algorithm slots - leaving registered algorithms unreleased and potentially double-freeing or corrupting state. No public exploit identified at time of analysis, and the flaw is not listed in the CISA Known Exploited Vulnerabilities catalog.
Local privilege escalation in the Linux kernel's OpenRISC signal return path allows any unprivileged local user to disable the Data MMU and gain arbitrary physical memory read/write access. The flaw exists in restore_sigcontext() on the OpenRISC (or1k) architecture, which fails to filter privileged Supervision Register (SR) bits copied from a user-controlled signal frame on sigreturn. Patched stable releases are available across all maintained kernel branches (5.10 through 7.2); no public exploit identified at time of analysis, though a verification proof-of-concept is documented in the fix description.
Race condition and error-path corruption in the Linux kernel sur40 input driver allow a local low-privileged user with access to an attached Samsung SUR40 multi-touch device to crash the kernel or corrupt input core state. The driver registers the input device in sur40_probe() before V4L2 video and vb2_queue components are fully initialized; any userspace process opening the input node immediately after registration can trigger the sur40_poll() worker thread, which dereferences the still-uninitialized vb2_queue and causes a data race leading to a potential system crash. A secondary error-path bug calls input_free_device() on an already-registered device instead of input_unregister_device(), corrupting input subsystem state if V4L2 initialization subsequently fails. No public exploit is identified at time of analysis.
Use-after-free race condition in the Linux kernel atmel-mci MMC/SD controller driver allows a local privileged user to corrupt freed kernel memory by racing module removal against queued bottom-half work items. Systems running Linux on Atmel AT91 or AVR32 SoC hardware with the atmel-mci driver loaded are exclusively affected; x86/x64 deployments are unaffected by design. Patch commits are confirmed available for stable branches 6.12.x, 6.18.x, 7.1.x, and 7.2, with no public exploit identified at time of analysis.
Memory leak in the Linux kernel s390/vfio_ccw subsystem enables a guest VM user to exhaust host kernel memory by submitting crafted channel programs that trigger cp_init() failure paths, leaving ccwchain segments unfreed. Affected deployments are IBM s390 (mainframe) KVM hosts that have vfio channel command word (CCW) device passthrough configured, making the attack surface highly specific. No public exploit has been identified and the vulnerability is not listed in the CISA KEV catalog; CVSS 7.1 with S:C reflects the guest-to-host cross-boundary availability impact.
Error propagation failure in the Linux kernel's XFS realtime filesystem subsystem corrupts filesystem state during xfs_growfs operations. The function xfs_rtginode_ensure() silently discards all non-ENOENT errors returned by xfs_rtginode_load(), leaving the realtime group inode pointer unset while growfs proceeds as though load succeeded - producing a null pointer dereference, kernel panic, or realtime subvolume metadata corruption. Patch commits targeting Linux 6.18.46, 7.1.10, and 7.2 are available via kernel.org stable branches; no public exploit or CISA KEV listing exists at time of analysis.
Slab-out-of-bounds write in the Linux kernel XFS real-time refcount B-tree (rtrefcountbt) subsystem allows a local attacker to trigger a kernel panic or potentially escalate privileges by mounting a crafted XFS filesystem image with the rtreflink feature set. The flaw is an off-by-one in on-disk root level validation - two check paths use '>' instead of '>=' - permitting an illegal bb_level that causes the cursor's bc_nlevels to exceed bc_maxlevels by one, indexing a 2-byte write 8 bytes past the end of a 216-byte slab object during the first B-tree operation. No public exploit or CISA KEV listing exists, but the guaranteed kernel panic and kernel heap write primitive make this a meaningful local risk on affected configurations.
Use-After-Free in the XFS filesystem online repair subsystem of the Linux kernel allows a local low-privileged user to potentially achieve full kernel memory corruption and privilege escalation to root. The flaw in `xrep_tempfile_create` leaves `sc->tempip` as a dangling pointer when tempfile creation fails partway through, enabling subsequent dereference of freed memory. No public exploit has been identified at time of analysis, but the AV:L/AC:L/PR:L/C:H/I:H/A:H CVSS vector indicates any authenticated local user on an XFS-backed system can attempt exploitation with low complexity.
Out-of-bounds array access in the Linux kernel's ASoC tas2562 audio driver allows local, low-privileged users to trigger kernel memory corruption by supplying unvalidated volume control values via the ALSA interface. The tas2562_volume_control_put() function accepts arbitrary userspace-supplied integers and uses them as unchecked array indices to look up a fixed-size table, potentially reading out-of-bounds kernel memory and writing that value to the TAS2562 hardware device over I2C. No public exploit code has been identified and the vulnerability is absent from CISA KEV; patched stable kernel releases are available across all affected branches.
The SpacemiT K3 clock driver in the Linux kernel fails to mark the HDMA clock as CLK_IS_CRITICAL, allowing the kernel's Common Clock Framework to gate it during power management. On SpacemiT K3 SoCs running an X100 RISC-V core, this produces an irrecoverable system hang whenever TCM-dependent operations - such as page fault handling triggered by vector instructions - are attempted while the HDMA clock is inactive. No public exploit has been identified at time of analysis and exposure is strictly bounded to SpacemiT K3 hardware; upstream fix commits are confirmed available for affected stable branches.
NULL pointer dereference in the Linux kernel's in-kernel OpenVPN data-plane module (ovpn) allows a network-reachable peer to crash the kernel by triggering key removal against a crypto slot that is not populated. Affected kernels span the ovpn-enabled range from commit 89d3c0e4612afa1c6429ed68d298e35592fbe208 through versions prior to 6.18.46, 7.1.10, and 7.2. No public exploit code and no CISA KEV listing have been identified at time of analysis; exploitation impact is full availability loss of the VPN gateway via kernel panic.
A use-after-free / lifetime race in the Linux kernel's ovpn (in-kernel OpenVPN data-channel offload) module lets crypto completion callbacks outlive the peer and netdev they depend on. Because the callback holds both key-slot and peer references, dropping the last peer reference too early can schedule an RCU callback backed by already-freed module text after ovpn_cleanup's rcu_barrier has run, corrupting kernel memory during peer teardown or module removal. There is no public exploit identified at time of analysis, and despite the input's 9.8 CVSS this is a teardown-path race, not a remote unauthenticated RCE.
Out-of-bounds read in the RISC-V ZBB-optimized strnlen() routine of the Linux kernel allows the aligned-word loop to load one machine word past the caller-supplied count boundary; when the source is aligned and count is a multiple of the register size, the extra load lands exactly at s+count and faults if that address sits on an unmapped page boundary. The affected code path only runs on RISC-V hardware exposing the Zbb bitmanip extension. This has been fixed upstream (stable commits e697e30f and 5d588c68); no public exploit identified at time of analysis, and the CNA's 9.4 network-vector scoring is inconsistent with an arch-local kernel string-length primitive.
Indefinite TX queue stall in the Linux kernel veth driver allows a denial-of-service condition against multi-queue virtual Ethernet interfaces running GRO without an XDP program attached. The root cause is that veth_poll() incorrectly uses rq->xdp_rxq.queue_index to determine which peer TX queue to wake - a field that is zero-initialized and only populated when XDP is active - causing all NAPI instances to wake peer TX queue 0 instead of the correct queue. In a multi-queue veth setup, a stopped TX queue (e.g., queue 1 halted due to ptr_ring saturation) is never woken, producing an indefinite transmit stall with no watchdog recovery because veth implements no ndo_tx_timeout. No public exploit is identified at time of analysis; reproduction scripts are publicly available from the reporter.
NULL pointer dereference in the Linux kernel ngbe (Wangxun) network driver crashes the kernel when the NIC operates in non-MSI-X interrupt mode (legacy INTx or single MSI). Systems running affected kernel versions with Wangxun WX1860-series NICs configured in non-MSI-X mode are exposed to a kernel panic, resulting in complete system availability loss. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; however, patch commits are available across multiple stable kernel branches.
Denial of service in the Linux kernel's TI AM65 CPSW NUSS Ethernet driver (am65-cpsw-nuss) allows sporadic kernel crashes because the driver treats the full 16-bit RX DMA descriptor Source Tag as the MAC port ID, when only the lower 8 bits are valid. On affected TI Sitara/K3 (AM65x-class) hardware, the arbitrary hardware-reserved upper 8 bits produce an invalid port_id that subsequent driver code uses to access out-of-bound memory, causing kernel panics. No public exploit is identified and it is not on CISA KEV; the vendor-tagged impact is Denial Of Service, not the remote code execution implied by the automated 9.8 score.
Cross-namespace privilege escalation in Kyverno 1.18.0-1.18.1 lets any tenant who can create a NamespacedMutatingPolicy in their own namespace force the cluster-privileged admission controller to generate resources (ConfigMaps, Secrets, NetworkPolicies, RoleBindings) in arbitrary namespaces, including kube-system. The nmpol CEL compiler unintentionally exposes the generator library to matchConditions, and neither the mpol validator nor GenerateResources enforces namespace scope on the generator.apply() target. A working proof-of-concept is published in the vendor advisory (GHSA-79gf-7frw-68m9); there is no KEV listing or evidence of active exploitation, and the issue is fixed in 1.18.2.
Stack-based buffer overflow in GNOME Dia diagram editor (0.98.0 and earlier) permits stack exhaustion and potential return-address corruption when a victim opens a crafted .dia XML file containing a Bus object with an attacker-controlled bus_handles value and then moves a handle in the diagram. The root cause - an unbounded g_alloca() call driven by an unvalidated file attribute - is also present in objects/Misc/tree.c via Tree objects, widening the attack surface. No public exploit or CISA KEV listing exists at time of analysis, but the GitLab issue provides sufficient technical detail for proof-of-concept development.
Stack-based buffer overflow in BlueZ, the Linux Bluetooth protocol stack, allows any unauthenticated attacker within Bluetooth radio range to crash the bluetoothd service and potentially execute arbitrary code. The flaw is triggered when a target device with Bluetooth discovery enabled processes a malicious Extended Inquiry Response (EIR) packet. No active exploitation has been confirmed (not in CISA KEV), and no public proof-of-concept is identified at time of analysis.
Uncontrolled resource consumption in Apache Tomcat's HTTP/2 implementation allows remote unauthenticated attackers to exhaust server memory by repeatedly opening and resetting HTTP/2 streams, exploiting an allocation leak in the backlog tracking mechanism that fails to release memory on stream reset. Affected branches span Tomcat 9.0.39-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24, with EOL branch 8.5.59-8.5.100 also confirmed vulnerable but unpatchable. No public exploit has been identified at time of analysis; EPSS stands at a low 0.22%, but the unauthenticated network vector and high availability impact make this operationally significant for any HTTP/2-enabled Tomcat deployment.
Authorization bypass in Apache Tomcat's FORM-based authentication lets attackers reach protected resources that a security constraint was meant to restrict, defeating rules that grant a role POST access but withhold GET (or vice versa) on the same URL. It affects Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, plus EOL 8.5.0-8.5.100 and 7.0.0-7.0.109. There is no public exploit identified at time of analysis, and EPSS is low (0.28%), but CISA SSVC rates the technical impact as total and the attack as automatable.
Improper Authorization in Apache Tomcat causes security-role-ref mappings - intended only for servlet-level isUserInRole() checks - to be incorrectly applied as role aliases within the Realm's authorization logic, allowing authenticated low-privileged users to access resources protected by higher-privileged roles. Supported branches 9.0.25-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24 are confirmed affected, along with EOL branches 7.0.97-7.0.109 and 8.5.46-8.5.100. No public exploit identified at time of analysis, and EPSS probability stands at 0.20% (10th percentile), though the CVSS 8.1 score reflects meaningful integrity and availability exposure in deployments relying on Realm-enforced role separation.
Rewrite valve processing in Apache Tomcat contains an off-by-one error (CWE-193) in the handling of the [N] (Next) flag, causing rule iteration to restart from the second rewrite rule instead of the first, which can produce unintended looping behavior and result in a denial-of-service condition. Affected supported versions span Tomcat 9.0.0.M1 through 9.0.120, 10.1.0-M1 through 10.1.57, and 11.0.0-M1 through 11.0.24; the EOL 8.5.x branch is also affected but will not receive a fix. No active exploitation is confirmed (not in CISA KEV), EPSS stands at 0.20% (10th percentile), and no public exploit code has been identified at time of analysis.
Authentication bypass in Apache Tomcat's DIGEST authenticator lets a network attacker who has captured a valid DIGEST-authenticated request replay it once when its nonceCount sits on the upper boundary of the replay window and fewer than windowSize requests have since been made. It affects Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, plus EOL 8.5.x and 7.0.x branches, but only where DIGEST authentication is actually enabled. No public exploit identified at time of analysis; EPSS is low at 0.28% (20th percentile), so the assigned 9.8 overstates practical risk.
Improper input validation in Apache Tomcat 9.0.115-9.0.120, 10.1.53-10.1.57, and 11.0.20-11.0.24 stems from an incomplete fix for CVE-2026-32990 and, per its CVSS:3.1 vector, permits remote unauthenticated attackers to compromise confidentiality, integrity, and availability of the servlet container. Reported by the Apache security team, it carries a critical 9.8 base score, though vendor tagging labels the impact as Information Disclosure, which is narrower than the vector implies. No public exploit identified at time of analysis, and EPSS estimates exploitation probability at just 0.21% (11th percentile).
Apache Tomcat's Unix domain socket creation path exposes a TOCTOU race condition across versions 9.0.42-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24, enabling an unauthorized local OS user to seize the socket before Tomcat finalizes access permissions. The vendor-assigned CVSS 8.1 with AV:N directly conflicts with the description's explicit 'local user' constraint and the inherently host-local nature of Unix domain sockets - the effective attack surface is limited to users with OS-level access on Tomcat hosts. No public exploit code or active exploitation has been identified; EPSS sits at 0.16% (5th percentile), indicating negligible real-world exploitation pressure at time of analysis.
Security constraint bypass in Apache Tomcat (7.0.x through 11.0.x) lets remote unauthenticated attackers reach protected resources when a broader security constraint for a longer path is declared ahead of a more restrictive constraint for a shorter sub-path, causing the wrong constraint to be applied. The flaw (CVSS 9.1, CWE-284) exposes access-controlled application paths without valid credentials. No public exploit identified at time of analysis, and EPSS is low (0.23%), but the network-reachable, no-interaction profile makes it a meaningful patch priority.
Sandbox-escaping remote code execution is possible in Google Chrome for iOS before 152.0.7977.65, where a use-after-free in the Sync component can be triggered by a victim visiting a crafted HTML page, potentially letting a remote attacker run arbitrary code outside the renderer sandbox. Google has shipped a fixed stable build, and there is no public exploit identified at time of analysis; the flaw is not listed in CISA KEV and SSVC records exploitation status as none. Notably, Chromium's own severity rating for this bug is Low, which stands in sharp contrast to the 9.6 CVSS score in the input.
Race condition in Google Chrome Enterprise on Windows prior to version 152.0.7977.65 enables an adjacent network attacker to potentially escape the browser sandbox and execute arbitrary code on the host system via crafted network traffic. No public exploit code has been identified and CISA has not listed this in the Known Exploited Vulnerabilities catalog. Despite a CVSS base score of 7.5, Google's Chromium team assigned an internal severity of Low, and SSVC analysis independently rates exploitation as none with non-automatable attack conditions - together suggesting constrained real-world impact relative to raw score.
Web origin policy bypass in Google Chrome for Android before 152.0.7977.65 lets a malicious co-installed app abuse the CustomTabs component to escape same-origin restrictions and access content it should not. The flaw is a local privilege/authorization issue (Chromium-rated Low severity) requiring a second attacker-controlled app already present on the device; no public exploit has been identified and EPSS probability is very low (0.11%).
Information disclosure in Google Chrome's DevTools (versions prior to 152.0.7977.65) lets a remote attacker who convinces a user to install a crafted Chrome extension read adjacent memory inside the renderer sandbox via an off-by-one error. Chromium rates the security severity as Low, and there is no public exploit identified at time of analysis; SSVC lists exploitation status as none and EPSS is negligible (0.16%, 6th percentile).
Remote code execution within the Chrome sandbox is achievable in Google Chrome prior to 152.0.7977.65 through a use-after-free vulnerability in V8, Chrome's JavaScript engine, triggered by a crafted HTML page. Any unauthenticated remote attacker who can induce a user to visit a malicious URL can exploit this flaw; however, execution is confined to the Chrome sandbox, meaning a chained sandbox escape would be required for full host-system compromise. No public exploit code or confirmed active exploitation is documented at time of analysis, and SSVC assessment lists exploitation as none, tempering urgency despite the high CVSS base score.
Type confusion in Chrome's V8 JavaScript engine exposes memory contents within the browser sandbox to remote attackers who can socially engineer victims into visiting a crafted HTML page. All Chrome desktop releases prior to 152.0.7977.65 are affected, confirmed by the Chrome Stable Channel advisory linked in references. Despite the vendor-assigned CVSS 8.8, Chromium's own security team rated this 'Low' severity - reflecting the sandboxed scope of the memory disclosure and the required social engineering step - and EPSS probability stands at only 0.26% (18th percentile) with no CISA KEV listing, consistent with SSVC 'Exploitation: none'.
Integer overflow (CWE-190) in Chromium's file-processing code exposes all desktop Google Chrome versions prior to 152.0.7977.65 to in-sandbox memory disclosure when a user opens a specially crafted file, requiring no authentication (PR:N) but requiring user interaction (UI:R). A critical data conflict across sources warrants attention: the NVD CVSS score is 8.8 with C:H/I:H/A:H, yet Google's Chromium team rates this Low severity, and the EPSS is 0.16% (5th percentile) with SSVC Exploitation:none - collectively suggesting the attack impact is bounded to memory readable within the sandboxed renderer, without sandbox escape. No public exploit identified at time of analysis.
Use-after-free in the Animation component of Google Chrome prior to 152.0.7977.65 enables arbitrary code execution within the browser's renderer sandbox when a user visits a crafted HTML page. The flaw scores 8.8 CVSS HIGH, though Google's own internal Chromium severity rating is Low - a notable discrepancy that reflects the sandboxed containment of the impact. No public exploit code has been identified, SSVC indicates no active exploitation, and a vendor patch is confirmed available in Chrome 152.0.7977.65.
Remote code execution in Google Chrome desktop before 152.0.7977.65 arises from a use-after-free in the ServiceWorker subsystem that a crafted HTML page can trigger to run attacker code outside the renderer sandbox. Any user browsing to a malicious page with a vulnerable build is exposed, and successful exploitation yields full compromise of the host user context. No public exploit identified at time of analysis and the issue is not in CISA KEV; notably, Chromium's own severity rating is Low even though the NVD CVSS base score is 9.6, a discrepancy defenders should weigh.
Type confusion in Chrome's V8 JavaScript engine (versions prior to 152.0.7977.65) enables remote code execution within the browser sandbox when a victim is socially engineered into visiting a crafted HTML page. The vulnerability arises from a CWE-843 type confusion flaw in V8, allowing an attacker to manipulate object type assumptions at runtime to achieve arbitrary code execution. Importantly, execution is constrained to the Chrome sandbox, which Chromium's own severity rating of 'Low' reflects; no public exploit code or CISA KEV listing has been identified at time of analysis.
UI spoofing in Google Chrome's Passwords component (versions prior to 152.0.7977.65) lets a remote attacker who has already compromised the renderer process present forged interface elements via a crafted HTML page, enabling deception such as credential phishing. Chromium rated this severity Low, and no public exploit or active exploitation has been identified; EPSS is low at 0.23% (14th percentile). The headline NVD CVSS of 9.1 substantially overstates the practical impact given the required renderer compromise.
Privilege-management weakness in Google Chrome's Actor component (versions prior to 152.0.7977.65) lets a remote attacker who successfully socially-engineers a user into loading a crafted HTML page bypass system access restrictions. Chromium rates the underlying severity as Low, and no public exploit or active exploitation has been identified; EPSS is 0.21% (11th percentile). Note a sharp signal conflict: the NVD-style CVSS base score is 9.8 (critical) while the vendor's own severity rating is Low and the description requires user interaction.
Use-after-free in Google Chrome's PDF rendering subsystem (all versions prior to 152.0.7977.65) allows a remote attacker to execute arbitrary code confined within the Chrome sandbox by delivering a crafted PDF file. The vulnerability is triggered through normal user interaction - opening a malicious PDF - requiring no privileges or authentication. While CVSS scores this 8.8 (High), Chrome's own severity rating is 'Low', reflecting the critical nuance that code execution is sandboxed and does not directly achieve host-level compromise. No public exploit exists and SSVC confirms no known exploitation at time of analysis.
Integer overflow in the WebRTC component of Google Chrome prior to 152.0.7977.65 enables remote code execution confined to the browser's sandbox via a crafted HTML page. The flaw requires no authentication (PR:N) and no special browser configuration, as WebRTC is enabled by default, but it does require the victim to visit an attacker-controlled page (UI:R). No public exploit code has been identified and EPSS places exploitation probability at 0.35%, consistent with SSVC's assessment of no current exploitation; notably, Google's own internal Chromium severity rating for this issue is 'Low,' suggesting the sandbox boundary and exploit reliability considerations factor into their triage.
Remote code execution inside the Chrome sandbox is possible through a race condition in the Extensions component, exploitable via crafted network traffic against Google Chrome versions prior to 152.0.7977.65. Despite a CVSS score of 8.1, Chrome's own team rates this vulnerability Low severity - a notable divergence explained by the sandbox constraint: successful exploitation yields in-sandbox code execution rather than full OS-level compromise. No public exploit identified at time of analysis, and SSVC confirms no known active exploitation and that the attack cannot be automated reliably.
Use-after-free in Google Chrome's DevTools component (all versions prior to 152.0.7977.65) enables remote attackers to execute arbitrary code inside the Chrome sandbox by distributing a crafted extension through social engineering. The CVSS 8.8 score reflects high confidentiality, integrity, and availability impact within the process scope, though exploitation is constrained by the mandatory user interaction required to install the malicious extension. No public exploit code exists and SSVC rates active exploitation as none at time of analysis, placing real-world urgency below what the raw score implies.
Improper state validation in Google Chrome's HTML parser (all versions prior to 152.0.7977.65) enables remote code execution within the browser's renderer sandbox when a user visits a crafted HTML page. The flaw (CWE-754) requires no authentication and minimal user interaction - simply loading malicious HTML is sufficient - but execution is constrained to the renderer sandbox (scope unchanged, S:U). Despite an 8.8 CVSS score, EPSS sits at 0.21% (12th percentile) and CISA SSVC confirms no current exploitation, with no public exploit or KEV listing identified at time of analysis.
Remote code execution in Google Chrome prior to 152.0.7977.65 stems from improper input validation in the browser's Media component, enabling a remote attacker to potentially execute arbitrary code outside the sandbox when a user visits a crafted HTML page. The vulnerability carries a CVSS base score of 8.8, affects all desktop Chrome builds below 152.0.7977.65 across Windows, macOS, and Linux, and is classified under CWE-20. No public exploit has been identified at time of analysis, and CISA SSVC rates current exploitation as none despite a total technical impact rating.
Remote code execution outside the browser sandbox is achievable in Google Chrome prior to 152.0.7977.65 via improper input validation in the Media component, triggered by visiting a crafted HTML page. The sandbox escape aspect is the critical differentiator here - Chrome's multi-process sandbox is its primary defense-in-depth layer, so bypassing it yields native OS-level code execution under the victim's account. No public exploit identified at time of analysis, and SSVC classifies exploitation as none with the attack non-automatable due to required user interaction.
Sandbox escape in Google Chrome's Media component on Windows allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox via a crafted HTML page. Affected versions are all Chrome releases on Windows prior to 152.0.7977.65. No public exploit code or active exploitation has been identified at time of analysis; SSVC assessment confirms exploitation status as none, and EPSS probability is low at 0.26% (17th percentile), though SSVC technical impact is rated total given full sandbox bypass capability.
Insufficient control flow management in Google Chrome's DevTools component (versions prior to 152.0.7977.65) enables remote attackers to execute arbitrary code inside the browser sandbox by tricking a user into loading a crafted HTML page via social engineering. The flaw is rooted in CWE-691 and permits attacker-controlled code paths within the DevTools subsystem, with execution constrained to within the Chrome sandbox (S:U). No public exploit code has been identified at time of analysis, and both EPSS (0.21%, 12th percentile) and SSVC (exploitation: none, automatable: no) indicate low current exploitation probability despite the high CVSS 8.8 base score.
Type confusion in Google Chrome's DevTools component prior to version 152.0.7977.65 enables remote code execution within the browser sandbox when a victim is social-engineered into visiting a crafted HTML page. The flaw affects all Chrome platforms where DevTools is accessible and results in high confidentiality, integrity, and availability impact to the sandboxed process. No public exploit code has been identified at time of analysis, and SSVC assessment confirms no observed active exploitation, though the technical impact rating is classified as total.
Use-after-free in V8, Google Chrome's JavaScript engine, prior to version 152.0.7977.65 enables remote attackers to execute arbitrary code within the Chrome sandbox by luring a user to a crafted HTML page. The CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R) confirms low-complexity, unauthenticated network delivery requiring only a single user visit, with high confidentiality, integrity, and availability impact scoped to the renderer process. No public exploit code has been identified at time of analysis, and SSVC rates exploitation as none with a non-automatable attack path, though technical impact is assessed as total within the sandbox.
Remote code execution within the Chrome sandbox is achievable via a race condition in the V8 JavaScript engine, affecting all Google Chrome versions prior to 152.0.7977.65. An unauthenticated remote attacker (per CVSS PR:N) can trigger the vulnerability by luring a user to a crafted HTML page, exploiting a timing window in V8's memory management to execute arbitrary code. No public exploit code or active exploitation has been identified at time of analysis; EPSS sits at 0.24th percentile and CISA SSVC records exploitation status as none, classifying this as a theoretical-but-patched risk for organizations that deploy promptly.
Use-after-free in Chrome's Chromoting (remote desktop) component allows a remote, unauthenticated attacker to potentially execute arbitrary code outside the browser sandbox via crafted network traffic, affecting all Chrome versions prior to 152.0.7977.65. The sandbox-escape dimension elevates this beyond a typical renderer vulnerability, as successful exploitation could yield code execution in a broader process context. No public exploit identified at time of analysis and SSVC indicates no observed exploitation, but the technical impact is rated total.
Sandbox-escaping remote code execution affects Google Chrome on macOS before 152.0.7977.65 through a use-after-free in the browser's Bluetooth component (CVE-2026-79091). A remote attacker who lures a victim into opening a crafted HTML page can trigger the freed-memory reuse to run arbitrary code outside the renderer sandbox, giving control of the host process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the sandbox-escape scope change drives a 9.6 CVSS base score despite Chromium's own Medium severity rating.
Sandbox-escaping remote code execution affects Google Chrome desktop before 152.0.7977.65, where a use-after-free in the ServiceWorker component lets a remote attacker run arbitrary code outside the renderer sandbox when a victim opens a crafted HTML page. The CVSS 3.1 score of 9.6 reflects the scope change (sandbox escape) and full CIA impact, though Google rated the Chromium severity only Medium and CISA's SSVC framework marks exploitation as none. No public exploit or CISA KEV listing exists at time of analysis, so risk is currently theoretical but high-impact.
Sandbox-escaping remote code execution affects Google Chrome on macOS prior to 152.0.7977.65, where a use-after-free in the Network component lets a remote attacker who convinces a victim to install a crafted extension run arbitrary code outside the renderer sandbox. Google rates the Chromium severity Medium, but the CVSS 9.6 reflects the scope-changing sandbox escape. No public exploit is identified at time of analysis and it is not on CISA KEV; EPSS is low at 0.24%.
Remote code execution outside Chrome's renderer sandbox is possible on macOS in all Chrome builds prior to 152.0.7977.65, triggered by improper input validation in the ANGLE graphics engine. An unauthenticated remote attacker (confirmed by PR:N in the provided CVSS vector) can exploit this by directing a macOS user to a specially crafted HTML page, which causes ANGLE to process malformed graphics input and execute attacker-controlled code outside the sandbox boundary. No CISA KEV listing or public exploit code exists at time of analysis, and an EPSS of 0.21% (12th percentile) indicates low current exploitation probability, though the zero-privilege-required, low-complexity attack path warrants prompt patching.
Out-of-bounds read in Google Chrome's ANGLE graphics engine on Windows prior to version 152.0.7977.65 enables remote attackers to potentially execute arbitrary code outside the browser sandbox. Exploitation requires no authentication and only that a victim navigate to a crafted HTML page, yielding a CVSS 8.8 score with high impact across confidentiality, integrity, and availability. A vendor-released patch is available; no public exploit or confirmed active exploitation has been identified at time of analysis.
Use-after-free in Chrome's UI layer allows a local attacker who has already achieved code execution inside the renderer process to escape the Chrome sandbox and execute arbitrary code on the underlying host system. All Google Chrome desktop releases prior to 152.0.7977.65 are affected per CPE cpe:2.3:a:google:chrome. No public exploit or CISA KEV listing exists at time of analysis, and EPSS sits at 0.12% (2nd percentile), consistent with a sophisticated chained exploit rather than mass exploitation; however, the Scope:Changed CVSS vector confirms this is a full sandbox escape with critical C/I/A impact once the preconditions are met.
Use-after-free in Google Chrome's DevTools component (all versions prior to 152.0.7977.65) allows a remote attacker to execute arbitrary code within the browser's renderer sandbox. Exploitation requires the victim to be socially engineered into installing and activating a crafted Chrome extension, making this a user-interaction-dependent attack rather than a passive drive-by. No active exploitation has been confirmed via CISA KEV, and SSVC classifies the exploitation status as none; however, SSVC also rates technical impact as total, meaning successful exploitation fully compromises confidentiality, integrity, and availability within the sandbox boundary.
Sandbox escape in Google Chrome's Media component (prior to 152.0.7977.65) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. Google has released a patched stable channel build (152.0.7977.65), with no public exploit code or active exploitation confirmed at time of analysis. EPSS sits at 0.21% (12th percentile) and SSVC rates the exploitation status as none with automatable: no, indicating this is a low-immediacy but technically severe sandbox escape requiring a two-stage attack chain.
Use-after-free in Chrome's Views UI component enables sandbox escape to arbitrary code execution outside the browser sandbox, affecting all Google Chrome versions prior to 152.0.7977.65. Exploitation requires an attacker who has already achieved renderer process compromise - making this a chained, second-stage attack rather than a direct initial access vector. No public exploit code has been identified and SSVC assessment confirms no active exploitation at time of analysis, though the technical impact is rated total due to the scope change across the sandbox boundary.
Incorrect authorization in the Chromoting component of Google Chrome on Windows prior to version 152.0.7977.65 enables a local attacker with standard user privileges to bypass system access restrictions by executing a crafted local program. The flaw (CWE-863) undermines Chrome Remote Desktop's authorization enforcement on Windows, allowing unauthorized access to protected system resources with both high confidentiality and integrity impact. No public exploit has been identified at time of analysis, and the EPSS score of 0.11% places this in the 1st percentile, indicating very low current exploitation probability despite the 7.1 CVSS base score.
GPU improper input validation in Google Chrome on Android (prior to 152.0.7977.65) enables a remote attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code at the OS level via a crafted HTML page. This is a chained sandbox escape - a second-stage exploit requiring a separate renderer compromise as a prerequisite, which the AC:H CVSS rating accurately reflects. No public exploit code has been identified and the vulnerability is absent from CISA KEV, but the full S:C/C:H/I:H/A:H impact ratings indicate that a successful chain yields complete browser compromise on Android.
Type confusion in Chrome's ANGLE graphics abstraction layer (all versions prior to 152.0.7977.65) enables remote attackers to potentially execute arbitrary code outside the browser sandbox by directing a user to a specially crafted HTML page. The CVSS 8.8 score reflects network-accessible delivery with no privilege requirements, full confidentiality, integrity, and availability impact, though user interaction is necessary. No public exploit identified at time of analysis; SSVC rates exploitation as 'none', yet technical impact is rated 'total' given the sandbox-escape language in the description.
Out-of-bounds write in ANGLE (Chrome's graphics abstraction layer) prior to version 152.0.7977.65 enables remote attackers to execute arbitrary code outside the browser sandbox by serving a crafted HTML page. The vulnerability carries a CVSS score of 8.8 and targets Chrome's Almost Native Graphics Layer Engine, a critical rendering subsystem, making exploitation viable against any unpatched Chrome user who visits a malicious page. No public exploit code or CISA KEV listing exists at time of analysis; EPSS probability is low at 0.30%, and SSVC assesses exploitation as 'none', suggesting real-world exploitation remains limited despite the high theoretical severity.
Out-of-bounds read in Chrome's Skia graphics library, affecting all versions prior to 152.0.7977.65, allows a remote unauthenticated attacker to leak sandbox-contained memory by delivering a crafted media file to a victim. The CVSS 8.1 score reflects high confidentiality and availability impact, though exploitation is bounded by Chrome's renderer sandbox. No public exploit or CISA KEV listing exists at time of analysis; a vendor patch is available and should be deployed via Chrome's standard update channel.
Remote code execution outside the browser sandbox is achievable in Google Chrome prior to 152.0.7977.65 via a race condition in ANGLE, the graphics API translation layer. Exploitation requires a victim to visit a crafted HTML page (UI:R), and the high attack complexity (AC:H) reflects the timing-sensitive, probabilistic nature of race condition exploitation. No public exploit code has been identified and CISA KEV does not list this CVE, though SSVC rates technical impact as total if exploitation succeeds.
Sandbox escape in Google Chrome for Android (versions prior to 152.0.7977.65) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox by delivering a crafted HTML page to the victim. The vulnerability stems from improper input validation in Chrome's Input subsystem on Android, confirmed by the CVSS scope-change metric (S:C) indicating the exploit crosses the sandbox boundary. No public exploit code or CISA KEV listing has been identified at time of analysis, and EPSS of 0.25% reflects the low automated exploitation probability attributable to the chained attack requirement.
Remote code execution outside the browser sandbox is potentially achievable in Google Chrome versions prior to 152.0.7977.65 through an integer overflow in the WebGL graphics subsystem triggered by visiting a crafted HTML page. The vulnerability affects all Chrome desktop platforms with a high-impact CVSS score of 8.8, though Chromium's internal severity rating of Medium and a low EPSS score of 0.25% (16th percentile) together suggest real-world exploitation remains uncommon at time of analysis. No public exploit code and no confirmed active exploitation have been identified; a vendor-released patch is available in stable channel update 152.0.7977.65.
Improper privilege management in Chrome's Regional Capabilities component allows remote attackers to bypass system access restrictions by delivering a crafted Chrome extension through social engineering. Affected versions are all Chrome releases prior to 152.0.7977.65 across desktop platforms. Despite a CVSS base score of 8.8, EPSS exploitation probability is very low at 0.21% (11th percentile), no active exploitation is confirmed in CISA KEV, and no public exploit code has been identified at time of analysis.
Remote code execution within the Chrome sandbox is possible in Google Chrome prior to 152.0.7977.65 via a stack-based buffer overflow in the V8 JavaScript engine, triggered by a crafted HTML page visited by an unpatched user. The vulnerability requires no authentication or elevated privileges from the victim - only that they visit an attacker-controlled page - and achieves arbitrary code execution within Chrome's renderer sandbox. No public exploit has been identified at time of analysis, and EPSS at 0.39% (31st percentile) indicates low current exploitation probability despite the 8.8 CVSS score; notably, Google's own internal severity rating is Medium, reflecting the sandbox containment.
Sandbox escape via a TOCTOU race condition in Google Chrome's Start component on Android prior to 152.0.7977.65 allows a local attacker to execute arbitrary code outside Chrome's sandbox. Exploitation requires a co-installed malicious application placed via social engineering, making opportunistic mass exploitation infeasible despite a CVSS base score of 8.1. No public exploit code exists and this vulnerability is absent from CISA KEV; EPSS sits at 0.15% (4th percentile), confirming low observed exploitation pressure. Vendor patch is available at version 152.0.7977.65.
Heap buffer overflow in Google Chrome's Media component prior to version 152.0.7977.65 enables remote code execution inside the renderer sandbox when a user visits a crafted HTML page. The CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U) reflects low attack complexity and no authentication requirement, but the unchanged scope (S:U) confirms execution is sandboxed - a full system compromise would require a separate sandbox escape not described in this CVE. No public exploit code has been identified and no CISA KEV listing exists; EPSS of 0.28% (20th percentile) indicates low observed exploitation activity, which is consistent with a patch-and-monitor posture rather than emergency response.
Heap-based buffer overflow in Google Chrome's WebRTC component (versions prior to 152.0.7977.65) enables a remote attacker to execute arbitrary code inside the Chrome renderer sandbox by delivering a crafted HTML page to a victim user. The CVSS score of 8.8 reflects broad impact (C:H/I:H/A:H) with no authentication prerequisite, though code execution is initially sandboxed and scope is unchanged (S:U). No public exploit code has been identified at time of analysis; SSVC records exploitation status as none and EPSS probability is low at 0.28% (20th percentile), suggesting this has not yet been leveraged at scale despite the high-severity rating.
The Linux kernel ims-pcu USB driver exposes sysfs device attributes on the secondary data interface in addition to the intended primary control interface, allowing local users to trigger kernel crashes or undefined behavior by accessing those attributes on the data interface, which lacks the descriptors and internal state the driver requires. Affected systems must have an IMS Passenger Control Unit USB device physically connected and run a kernel version between commit 204d18a7a0c67352857dee1bbac517ed63f01d8e and the respective fix commits. No public exploit code exists, and the EPSS score of 0.17% (6th percentile) reflects the extreme hardware rarity required for exploitation; no CISA KEV listing exists.
Corrupted xattr entry handling in the Linux kernel's f2fs filesystem driver exposes local users to kernel memory disclosure and potential corruption. When f2fs_listxattr() processes a crafted or corrupted filesystem image containing malformed extended attribute entries that fall outside the valid xattr storage area, the kernel previously returned a partial success result without validating entry boundaries. This flaw affects a wide range of kernel stable branches from the commit introducing the bug (688078e7f36c293dae25b338ddc9e0a2790f6e06) through the backported fixes. No public exploit code exists and EPSS is 0.18% (7th percentile), indicating low exploitation probability at time of analysis.
HTTP method confusion in grpc-ecosystem's grpc-gateway v2.28.0 lets remote clients bypass method-based access controls enforced by an upstream WAF or reverse proxy. The ServeMux honors a client-supplied X-HTTP-Method-Override header on POST requests carrying Content-Type application/x-www-form-urlencoded, rewriting the request method to any attacker-chosen verb (e.g. DELETE, PUT) before routing, so a proxy that only permits POST is fooled while the gateway dispatches to a restricted handler. No public exploit identified at time of analysis, and EPSS is low (0.18%), but the upstream fix is confirmed via commit 72123cd4.
Use-after-free in Redis's TLS pending-data handler (`tlsProcessPendingData()`) enables remote attackers to potentially execute arbitrary commands at the privilege level of the Redis server process. The flaw spans all major active Redis release lines and is confirmed fixed in versions 6.2.24, 7.2.16, 7.4.11, 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1 - exploitation is gated on TLS being explicitly configured, which is non-default. A public proof-of-concept exists; SSVC rates technical impact as total but automation as not feasible, and the vulnerability is not currently listed in CISA KEV.
Grafana Alloy's prometheus.operator.servicemonitors component exposes an arbitrary local file read path that leads to credential theft and potential Kubernetes privilege escalation. Any Kubernetes user with ServiceMonitor create or modify rights in a namespace watched by Alloy can point the bearerTokenFile field at any file accessible to the Alloy process - most critically Alloy's own projected Kubernetes service account token - and receive that file's contents exfiltrated via HTTP Bearer token to an attacker-controlled scrape endpoint. The CVSS 7.7 Scope:Changed rating correctly reflects that successful exploitation transcends the compromised namespace, potentially granting the attacker cluster-level API access commensurate with Alloy's own RBAC permissions. No public exploit has been identified at time of analysis.
Path traversal in NLTK through version 3.10.3 allows attackers who control caller-supplied file paths to read or write files outside the boundaries enforced by the pathsec sandbox module. The affected APIs - TransitionParser, AveragedPerceptron, PerceptronTagger, and maxent parameter loading - perform raw file I/O directly on caller-provided paths without routing through pathsec enforcement, undermining the intended access control boundary. The CVSS 4.0 score of 8.3 reflects high confidentiality impact; no public exploit code or CISA KEV listing has been identified at time of analysis.
CPU-pinning denial of service in NLTK's PorterStemmer component (versions ≤ 3.10.2) allows a remote unauthenticated attacker to exhaust a CPU core for seconds to minutes by submitting a single crafted token. The root cause is quadratic algorithmic complexity: _is_consonant() re-walks trailing 'y' characters on every invocation, and _measure() calls it once per stem position, resulting in O(n²) processing time. Any service that passes untrusted text through PorterStemmer.stem() without input length validation is vulnerable; a ~20-50 KB payload of repeated 'y' characters followed by a matching suffix such as 'ness' is sufficient to trigger the condition. No public exploit code is identified at time of analysis, but the attack primitive is trivially constructable from the public description. Fix is available in NLTK 3.10.3.
Heap-based buffer overflow in FFmpeg's libswscale library enables unauthenticated remote attackers to crash media-processing applications via a crafted input file. The vulnerable function ff_sws_alphablendaway, invoked during alpha channel compositing in git-master commit 722a217, mishandles attacker-controlled input and corrupts heap memory, producing a Denial of Service. No active exploitation is confirmed - EPSS stands at 0.15% (5th percentile) with no CISA KEV listing - indicating this is currently a crash risk rather than a weaponized threat.
NULL pointer dereference in FFmpeg development snapshot N-122528-gdd2976b9e1 crashes the FFmpeg process when parsing a maliciously crafted video file via the get_min_buffer_size function in libswscale/slice.c. Any application or automated pipeline using this FFmpeg build to process untrusted video input is exposed to unauthenticated remote denial of service, as confirmed by the AV:N/AC:L/PR:N/UI:N CVSS vector. No public exploit code exists at time of analysis, and EPSS at 0.15% (4th percentile) signals low current threat-actor activity.
Heap-based buffer overflow in the Dia diagram editor's WPG file importer allows arbitrary code execution or process crash when a user opens a crafted WPG file. The WPG color palette buffer is allocated for exactly 256 entries (768 bytes), but the COLORMAP record parser fails to validate that the supplied start index (i16) or total entry count (iNum16) stay within that bound, allowing a malicious file to drive fread() to write beyond the heap allocation. Affecting all Dia versions on the upstream master branch through at least 2026-08-21, no public exploit or patch version has been confirmed at time of analysis, though the description provides sufficient detail to construct proof-of-concept input.
Out-of-bounds memory write in the Linux kernel's ASoC lpass-tx-macro audio codec driver allows a local low-privileged user to corrupt kernel memory via misconfigured ALSA enum kcontrol access, with potential for privilege escalation. The driver's get and put handlers for DEC0-DEC7 MODE controls incorrectly access the 8-byte integer union field instead of the 4-byte enumerated union field, writing 4 bytes beyond the intended boundary on 64-bit systems. No public exploit code has been identified at time of analysis, but the pattern mirrors two previously fixed sibling drivers (rx-macro, va-macro), confirming the root cause is well-understood.
PMD huge page mapping boundary violation in the Linux kernel's drm/shmem_helper subsystem allows local users with low privileges to trigger out-of-bounds memory mappings via the DRM ->huge_fault handler. The handler installs PMD-level Transparent Huge Page mappings without verifying they remain within Virtual Memory Area boundaries, triggering a VM_BUG_ON_VMA() assertion when the mapping subsequently reaches copy_pmd_range() during fork or remap operations. Patches have been committed to Linux 7.1.10 and 7.2 stable branches; no public exploit has been identified at time of analysis.
Out-of-bounds memory access in the Linux kernel's cs40l50-vibra haptic driver allows a local low-privileged user to read or write beyond allocated kernel buffers by submitting a crafted force-feedback effect via EVIOCSFF ioctl. The driver's cs40l50_add() function fails to validate user-supplied custom_len before dereferencing custom_data[0] and custom_data[1], and an integer sign-wrap in bank type handling permits negative array indexing into vib->dsp.banks[]. Three distinct code paths are exploitable: zero-length allocation returning ZERO_SIZE_PTR, single-word allocation followed by a two-word read, and s16 overflow enabling out-of-bounds bank array access. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV.
Heap buffer overflow in the Linux kernel synaptics-rmi4 driver allows local low-privileged users to overwrite kernel heap memory by exploiting stale state in the F54 diagnostics function. Affected systems must have Synaptics RMI4 touchpad hardware present and the driver loaded; exploitation involves manipulating V4L2 buffer sizes to trigger the overflow after an error condition leaves f54->report_size containing a stale value from a prior successful operation. Patches are available across all supported stable branches; no public exploit or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Out-of-bounds memory write in the Linux kernel's synaptics-rmi4 input driver allows a local attacker with access to a malicious or malfunctioning RMI4 touchpad device to corrupt kernel memory, potentially enabling privilege escalation or information disclosure. The root cause is a mismatch between the F54 report buffer allocation size (derived from F54 electrode counts) and the transfer size computed from F55 electrode counts - both sourced directly from device queries with no cross-validation. Vendor patches are confirmed across multiple stable kernel branches; no public exploit or CISA KEV listing has been identified at time of analysis.
Heap buffer overflow in the Linux kernel's synaptics-rmi4 driver allows a local low-privileged user to trigger memory corruption by issuing VIDIOC_S_INPUT while the V4L2 diagnostic queue is actively streaming. The F54 function allocates V4L2 buffers sized to the report type at stream start; switching the input mid-stream to a larger report type overflows those buffers, enabling potential privilege escalation to root. Patches have been released across all active stable kernel branches; no public exploit code or CISA KEV listing has been identified at time of analysis.
Incorrect error-path logic in the Linux kernel's Qualcomm Crypto Engine (QCE) driver allows a local attacker with low privileges on Qualcomm SoC-based hardware to potentially trigger memory corruption via a use-after-free or improper resource release condition. The flaw resides in `devm_qce_register_algs`, where a failed `ops->register_algs()` call causes the cleanup loop to repeatedly invoke `ops->unregister_algs()` on the failed slot rather than iterating over previously successfully registered algorithm slots - leaving registered algorithms unreleased and potentially double-freeing or corrupting state. No public exploit identified at time of analysis, and the flaw is not listed in the CISA Known Exploited Vulnerabilities catalog.
Local privilege escalation in the Linux kernel's OpenRISC signal return path allows any unprivileged local user to disable the Data MMU and gain arbitrary physical memory read/write access. The flaw exists in restore_sigcontext() on the OpenRISC (or1k) architecture, which fails to filter privileged Supervision Register (SR) bits copied from a user-controlled signal frame on sigreturn. Patched stable releases are available across all maintained kernel branches (5.10 through 7.2); no public exploit identified at time of analysis, though a verification proof-of-concept is documented in the fix description.
Race condition and error-path corruption in the Linux kernel sur40 input driver allow a local low-privileged user with access to an attached Samsung SUR40 multi-touch device to crash the kernel or corrupt input core state. The driver registers the input device in sur40_probe() before V4L2 video and vb2_queue components are fully initialized; any userspace process opening the input node immediately after registration can trigger the sur40_poll() worker thread, which dereferences the still-uninitialized vb2_queue and causes a data race leading to a potential system crash. A secondary error-path bug calls input_free_device() on an already-registered device instead of input_unregister_device(), corrupting input subsystem state if V4L2 initialization subsequently fails. No public exploit is identified at time of analysis.
Use-after-free race condition in the Linux kernel atmel-mci MMC/SD controller driver allows a local privileged user to corrupt freed kernel memory by racing module removal against queued bottom-half work items. Systems running Linux on Atmel AT91 or AVR32 SoC hardware with the atmel-mci driver loaded are exclusively affected; x86/x64 deployments are unaffected by design. Patch commits are confirmed available for stable branches 6.12.x, 6.18.x, 7.1.x, and 7.2, with no public exploit identified at time of analysis.
Memory leak in the Linux kernel s390/vfio_ccw subsystem enables a guest VM user to exhaust host kernel memory by submitting crafted channel programs that trigger cp_init() failure paths, leaving ccwchain segments unfreed. Affected deployments are IBM s390 (mainframe) KVM hosts that have vfio channel command word (CCW) device passthrough configured, making the attack surface highly specific. No public exploit has been identified and the vulnerability is not listed in the CISA KEV catalog; CVSS 7.1 with S:C reflects the guest-to-host cross-boundary availability impact.
Error propagation failure in the Linux kernel's XFS realtime filesystem subsystem corrupts filesystem state during xfs_growfs operations. The function xfs_rtginode_ensure() silently discards all non-ENOENT errors returned by xfs_rtginode_load(), leaving the realtime group inode pointer unset while growfs proceeds as though load succeeded - producing a null pointer dereference, kernel panic, or realtime subvolume metadata corruption. Patch commits targeting Linux 6.18.46, 7.1.10, and 7.2 are available via kernel.org stable branches; no public exploit or CISA KEV listing exists at time of analysis.
Slab-out-of-bounds write in the Linux kernel XFS real-time refcount B-tree (rtrefcountbt) subsystem allows a local attacker to trigger a kernel panic or potentially escalate privileges by mounting a crafted XFS filesystem image with the rtreflink feature set. The flaw is an off-by-one in on-disk root level validation - two check paths use '>' instead of '>=' - permitting an illegal bb_level that causes the cursor's bc_nlevels to exceed bc_maxlevels by one, indexing a 2-byte write 8 bytes past the end of a 216-byte slab object during the first B-tree operation. No public exploit or CISA KEV listing exists, but the guaranteed kernel panic and kernel heap write primitive make this a meaningful local risk on affected configurations.
Use-After-Free in the XFS filesystem online repair subsystem of the Linux kernel allows a local low-privileged user to potentially achieve full kernel memory corruption and privilege escalation to root. The flaw in `xrep_tempfile_create` leaves `sc->tempip` as a dangling pointer when tempfile creation fails partway through, enabling subsequent dereference of freed memory. No public exploit has been identified at time of analysis, but the AV:L/AC:L/PR:L/C:H/I:H/A:H CVSS vector indicates any authenticated local user on an XFS-backed system can attempt exploitation with low complexity.
Out-of-bounds array access in the Linux kernel's ASoC tas2562 audio driver allows local, low-privileged users to trigger kernel memory corruption by supplying unvalidated volume control values via the ALSA interface. The tas2562_volume_control_put() function accepts arbitrary userspace-supplied integers and uses them as unchecked array indices to look up a fixed-size table, potentially reading out-of-bounds kernel memory and writing that value to the TAS2562 hardware device over I2C. No public exploit code has been identified and the vulnerability is absent from CISA KEV; patched stable kernel releases are available across all affected branches.
The SpacemiT K3 clock driver in the Linux kernel fails to mark the HDMA clock as CLK_IS_CRITICAL, allowing the kernel's Common Clock Framework to gate it during power management. On SpacemiT K3 SoCs running an X100 RISC-V core, this produces an irrecoverable system hang whenever TCM-dependent operations - such as page fault handling triggered by vector instructions - are attempted while the HDMA clock is inactive. No public exploit has been identified at time of analysis and exposure is strictly bounded to SpacemiT K3 hardware; upstream fix commits are confirmed available for affected stable branches.
NULL pointer dereference in the Linux kernel's in-kernel OpenVPN data-plane module (ovpn) allows a network-reachable peer to crash the kernel by triggering key removal against a crypto slot that is not populated. Affected kernels span the ovpn-enabled range from commit 89d3c0e4612afa1c6429ed68d298e35592fbe208 through versions prior to 6.18.46, 7.1.10, and 7.2. No public exploit code and no CISA KEV listing have been identified at time of analysis; exploitation impact is full availability loss of the VPN gateway via kernel panic.
A use-after-free / lifetime race in the Linux kernel's ovpn (in-kernel OpenVPN data-channel offload) module lets crypto completion callbacks outlive the peer and netdev they depend on. Because the callback holds both key-slot and peer references, dropping the last peer reference too early can schedule an RCU callback backed by already-freed module text after ovpn_cleanup's rcu_barrier has run, corrupting kernel memory during peer teardown or module removal. There is no public exploit identified at time of analysis, and despite the input's 9.8 CVSS this is a teardown-path race, not a remote unauthenticated RCE.
Out-of-bounds read in the RISC-V ZBB-optimized strnlen() routine of the Linux kernel allows the aligned-word loop to load one machine word past the caller-supplied count boundary; when the source is aligned and count is a multiple of the register size, the extra load lands exactly at s+count and faults if that address sits on an unmapped page boundary. The affected code path only runs on RISC-V hardware exposing the Zbb bitmanip extension. This has been fixed upstream (stable commits e697e30f and 5d588c68); no public exploit identified at time of analysis, and the CNA's 9.4 network-vector scoring is inconsistent with an arch-local kernel string-length primitive.
Indefinite TX queue stall in the Linux kernel veth driver allows a denial-of-service condition against multi-queue virtual Ethernet interfaces running GRO without an XDP program attached. The root cause is that veth_poll() incorrectly uses rq->xdp_rxq.queue_index to determine which peer TX queue to wake - a field that is zero-initialized and only populated when XDP is active - causing all NAPI instances to wake peer TX queue 0 instead of the correct queue. In a multi-queue veth setup, a stopped TX queue (e.g., queue 1 halted due to ptr_ring saturation) is never woken, producing an indefinite transmit stall with no watchdog recovery because veth implements no ndo_tx_timeout. No public exploit is identified at time of analysis; reproduction scripts are publicly available from the reporter.
NULL pointer dereference in the Linux kernel ngbe (Wangxun) network driver crashes the kernel when the NIC operates in non-MSI-X interrupt mode (legacy INTx or single MSI). Systems running affected kernel versions with Wangxun WX1860-series NICs configured in non-MSI-X mode are exposed to a kernel panic, resulting in complete system availability loss. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; however, patch commits are available across multiple stable kernel branches.
Denial of service in the Linux kernel's TI AM65 CPSW NUSS Ethernet driver (am65-cpsw-nuss) allows sporadic kernel crashes because the driver treats the full 16-bit RX DMA descriptor Source Tag as the MAC port ID, when only the lower 8 bits are valid. On affected TI Sitara/K3 (AM65x-class) hardware, the arbitrary hardware-reserved upper 8 bits produce an invalid port_id that subsequent driver code uses to access out-of-bound memory, causing kernel panics. No public exploit is identified and it is not on CISA KEV; the vendor-tagged impact is Denial Of Service, not the remote code execution implied by the automated 9.8 score.
Cross-namespace privilege escalation in Kyverno 1.18.0-1.18.1 lets any tenant who can create a NamespacedMutatingPolicy in their own namespace force the cluster-privileged admission controller to generate resources (ConfigMaps, Secrets, NetworkPolicies, RoleBindings) in arbitrary namespaces, including kube-system. The nmpol CEL compiler unintentionally exposes the generator library to matchConditions, and neither the mpol validator nor GenerateResources enforces namespace scope on the generator.apply() target. A working proof-of-concept is published in the vendor advisory (GHSA-79gf-7frw-68m9); there is no KEV listing or evidence of active exploitation, and the issue is fixed in 1.18.2.
Stack-based buffer overflow in GNOME Dia diagram editor (0.98.0 and earlier) permits stack exhaustion and potential return-address corruption when a victim opens a crafted .dia XML file containing a Bus object with an attacker-controlled bus_handles value and then moves a handle in the diagram. The root cause - an unbounded g_alloca() call driven by an unvalidated file attribute - is also present in objects/Misc/tree.c via Tree objects, widening the attack surface. No public exploit or CISA KEV listing exists at time of analysis, but the GitLab issue provides sufficient technical detail for proof-of-concept development.
Stack-based buffer overflow in BlueZ, the Linux Bluetooth protocol stack, allows any unauthenticated attacker within Bluetooth radio range to crash the bluetoothd service and potentially execute arbitrary code. The flaw is triggered when a target device with Bluetooth discovery enabled processes a malicious Extended Inquiry Response (EIR) packet. No active exploitation has been confirmed (not in CISA KEV), and no public proof-of-concept is identified at time of analysis.
Uncontrolled resource consumption in Apache Tomcat's HTTP/2 implementation allows remote unauthenticated attackers to exhaust server memory by repeatedly opening and resetting HTTP/2 streams, exploiting an allocation leak in the backlog tracking mechanism that fails to release memory on stream reset. Affected branches span Tomcat 9.0.39-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24, with EOL branch 8.5.59-8.5.100 also confirmed vulnerable but unpatchable. No public exploit has been identified at time of analysis; EPSS stands at a low 0.22%, but the unauthenticated network vector and high availability impact make this operationally significant for any HTTP/2-enabled Tomcat deployment.
Authorization bypass in Apache Tomcat's FORM-based authentication lets attackers reach protected resources that a security constraint was meant to restrict, defeating rules that grant a role POST access but withhold GET (or vice versa) on the same URL. It affects Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, plus EOL 8.5.0-8.5.100 and 7.0.0-7.0.109. There is no public exploit identified at time of analysis, and EPSS is low (0.28%), but CISA SSVC rates the technical impact as total and the attack as automatable.
Improper Authorization in Apache Tomcat causes security-role-ref mappings - intended only for servlet-level isUserInRole() checks - to be incorrectly applied as role aliases within the Realm's authorization logic, allowing authenticated low-privileged users to access resources protected by higher-privileged roles. Supported branches 9.0.25-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24 are confirmed affected, along with EOL branches 7.0.97-7.0.109 and 8.5.46-8.5.100. No public exploit identified at time of analysis, and EPSS probability stands at 0.20% (10th percentile), though the CVSS 8.1 score reflects meaningful integrity and availability exposure in deployments relying on Realm-enforced role separation.
Rewrite valve processing in Apache Tomcat contains an off-by-one error (CWE-193) in the handling of the [N] (Next) flag, causing rule iteration to restart from the second rewrite rule instead of the first, which can produce unintended looping behavior and result in a denial-of-service condition. Affected supported versions span Tomcat 9.0.0.M1 through 9.0.120, 10.1.0-M1 through 10.1.57, and 11.0.0-M1 through 11.0.24; the EOL 8.5.x branch is also affected but will not receive a fix. No active exploitation is confirmed (not in CISA KEV), EPSS stands at 0.20% (10th percentile), and no public exploit code has been identified at time of analysis.
Authentication bypass in Apache Tomcat's DIGEST authenticator lets a network attacker who has captured a valid DIGEST-authenticated request replay it once when its nonceCount sits on the upper boundary of the replay window and fewer than windowSize requests have since been made. It affects Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, plus EOL 8.5.x and 7.0.x branches, but only where DIGEST authentication is actually enabled. No public exploit identified at time of analysis; EPSS is low at 0.28% (20th percentile), so the assigned 9.8 overstates practical risk.
Improper input validation in Apache Tomcat 9.0.115-9.0.120, 10.1.53-10.1.57, and 11.0.20-11.0.24 stems from an incomplete fix for CVE-2026-32990 and, per its CVSS:3.1 vector, permits remote unauthenticated attackers to compromise confidentiality, integrity, and availability of the servlet container. Reported by the Apache security team, it carries a critical 9.8 base score, though vendor tagging labels the impact as Information Disclosure, which is narrower than the vector implies. No public exploit identified at time of analysis, and EPSS estimates exploitation probability at just 0.21% (11th percentile).
Apache Tomcat's Unix domain socket creation path exposes a TOCTOU race condition across versions 9.0.42-9.0.120, 10.1.0-M1-10.1.57, and 11.0.0-M1-11.0.24, enabling an unauthorized local OS user to seize the socket before Tomcat finalizes access permissions. The vendor-assigned CVSS 8.1 with AV:N directly conflicts with the description's explicit 'local user' constraint and the inherently host-local nature of Unix domain sockets - the effective attack surface is limited to users with OS-level access on Tomcat hosts. No public exploit code or active exploitation has been identified; EPSS sits at 0.16% (5th percentile), indicating negligible real-world exploitation pressure at time of analysis.
Security constraint bypass in Apache Tomcat (7.0.x through 11.0.x) lets remote unauthenticated attackers reach protected resources when a broader security constraint for a longer path is declared ahead of a more restrictive constraint for a shorter sub-path, causing the wrong constraint to be applied. The flaw (CVSS 9.1, CWE-284) exposes access-controlled application paths without valid credentials. No public exploit identified at time of analysis, and EPSS is low (0.23%), but the network-reachable, no-interaction profile makes it a meaningful patch priority.
Sandbox-escaping remote code execution is possible in Google Chrome for iOS before 152.0.7977.65, where a use-after-free in the Sync component can be triggered by a victim visiting a crafted HTML page, potentially letting a remote attacker run arbitrary code outside the renderer sandbox. Google has shipped a fixed stable build, and there is no public exploit identified at time of analysis; the flaw is not listed in CISA KEV and SSVC records exploitation status as none. Notably, Chromium's own severity rating for this bug is Low, which stands in sharp contrast to the 9.6 CVSS score in the input.
Race condition in Google Chrome Enterprise on Windows prior to version 152.0.7977.65 enables an adjacent network attacker to potentially escape the browser sandbox and execute arbitrary code on the host system via crafted network traffic. No public exploit code has been identified and CISA has not listed this in the Known Exploited Vulnerabilities catalog. Despite a CVSS base score of 7.5, Google's Chromium team assigned an internal severity of Low, and SSVC analysis independently rates exploitation as none with non-automatable attack conditions - together suggesting constrained real-world impact relative to raw score.
Web origin policy bypass in Google Chrome for Android before 152.0.7977.65 lets a malicious co-installed app abuse the CustomTabs component to escape same-origin restrictions and access content it should not. The flaw is a local privilege/authorization issue (Chromium-rated Low severity) requiring a second attacker-controlled app already present on the device; no public exploit has been identified and EPSS probability is very low (0.11%).
Information disclosure in Google Chrome's DevTools (versions prior to 152.0.7977.65) lets a remote attacker who convinces a user to install a crafted Chrome extension read adjacent memory inside the renderer sandbox via an off-by-one error. Chromium rates the security severity as Low, and there is no public exploit identified at time of analysis; SSVC lists exploitation status as none and EPSS is negligible (0.16%, 6th percentile).
Remote code execution within the Chrome sandbox is achievable in Google Chrome prior to 152.0.7977.65 through a use-after-free vulnerability in V8, Chrome's JavaScript engine, triggered by a crafted HTML page. Any unauthenticated remote attacker who can induce a user to visit a malicious URL can exploit this flaw; however, execution is confined to the Chrome sandbox, meaning a chained sandbox escape would be required for full host-system compromise. No public exploit code or confirmed active exploitation is documented at time of analysis, and SSVC assessment lists exploitation as none, tempering urgency despite the high CVSS base score.
Type confusion in Chrome's V8 JavaScript engine exposes memory contents within the browser sandbox to remote attackers who can socially engineer victims into visiting a crafted HTML page. All Chrome desktop releases prior to 152.0.7977.65 are affected, confirmed by the Chrome Stable Channel advisory linked in references. Despite the vendor-assigned CVSS 8.8, Chromium's own security team rated this 'Low' severity - reflecting the sandboxed scope of the memory disclosure and the required social engineering step - and EPSS probability stands at only 0.26% (18th percentile) with no CISA KEV listing, consistent with SSVC 'Exploitation: none'.
Integer overflow (CWE-190) in Chromium's file-processing code exposes all desktop Google Chrome versions prior to 152.0.7977.65 to in-sandbox memory disclosure when a user opens a specially crafted file, requiring no authentication (PR:N) but requiring user interaction (UI:R). A critical data conflict across sources warrants attention: the NVD CVSS score is 8.8 with C:H/I:H/A:H, yet Google's Chromium team rates this Low severity, and the EPSS is 0.16% (5th percentile) with SSVC Exploitation:none - collectively suggesting the attack impact is bounded to memory readable within the sandboxed renderer, without sandbox escape. No public exploit identified at time of analysis.
Use-after-free in the Animation component of Google Chrome prior to 152.0.7977.65 enables arbitrary code execution within the browser's renderer sandbox when a user visits a crafted HTML page. The flaw scores 8.8 CVSS HIGH, though Google's own internal Chromium severity rating is Low - a notable discrepancy that reflects the sandboxed containment of the impact. No public exploit code has been identified, SSVC indicates no active exploitation, and a vendor patch is confirmed available in Chrome 152.0.7977.65.
Remote code execution in Google Chrome desktop before 152.0.7977.65 arises from a use-after-free in the ServiceWorker subsystem that a crafted HTML page can trigger to run attacker code outside the renderer sandbox. Any user browsing to a malicious page with a vulnerable build is exposed, and successful exploitation yields full compromise of the host user context. No public exploit identified at time of analysis and the issue is not in CISA KEV; notably, Chromium's own severity rating is Low even though the NVD CVSS base score is 9.6, a discrepancy defenders should weigh.
Type confusion in Chrome's V8 JavaScript engine (versions prior to 152.0.7977.65) enables remote code execution within the browser sandbox when a victim is socially engineered into visiting a crafted HTML page. The vulnerability arises from a CWE-843 type confusion flaw in V8, allowing an attacker to manipulate object type assumptions at runtime to achieve arbitrary code execution. Importantly, execution is constrained to the Chrome sandbox, which Chromium's own severity rating of 'Low' reflects; no public exploit code or CISA KEV listing has been identified at time of analysis.
UI spoofing in Google Chrome's Passwords component (versions prior to 152.0.7977.65) lets a remote attacker who has already compromised the renderer process present forged interface elements via a crafted HTML page, enabling deception such as credential phishing. Chromium rated this severity Low, and no public exploit or active exploitation has been identified; EPSS is low at 0.23% (14th percentile). The headline NVD CVSS of 9.1 substantially overstates the practical impact given the required renderer compromise.
Privilege-management weakness in Google Chrome's Actor component (versions prior to 152.0.7977.65) lets a remote attacker who successfully socially-engineers a user into loading a crafted HTML page bypass system access restrictions. Chromium rates the underlying severity as Low, and no public exploit or active exploitation has been identified; EPSS is 0.21% (11th percentile). Note a sharp signal conflict: the NVD-style CVSS base score is 9.8 (critical) while the vendor's own severity rating is Low and the description requires user interaction.
Use-after-free in Google Chrome's PDF rendering subsystem (all versions prior to 152.0.7977.65) allows a remote attacker to execute arbitrary code confined within the Chrome sandbox by delivering a crafted PDF file. The vulnerability is triggered through normal user interaction - opening a malicious PDF - requiring no privileges or authentication. While CVSS scores this 8.8 (High), Chrome's own severity rating is 'Low', reflecting the critical nuance that code execution is sandboxed and does not directly achieve host-level compromise. No public exploit exists and SSVC confirms no known exploitation at time of analysis.
Integer overflow in the WebRTC component of Google Chrome prior to 152.0.7977.65 enables remote code execution confined to the browser's sandbox via a crafted HTML page. The flaw requires no authentication (PR:N) and no special browser configuration, as WebRTC is enabled by default, but it does require the victim to visit an attacker-controlled page (UI:R). No public exploit code has been identified and EPSS places exploitation probability at 0.35%, consistent with SSVC's assessment of no current exploitation; notably, Google's own internal Chromium severity rating for this issue is 'Low,' suggesting the sandbox boundary and exploit reliability considerations factor into their triage.
Remote code execution inside the Chrome sandbox is possible through a race condition in the Extensions component, exploitable via crafted network traffic against Google Chrome versions prior to 152.0.7977.65. Despite a CVSS score of 8.1, Chrome's own team rates this vulnerability Low severity - a notable divergence explained by the sandbox constraint: successful exploitation yields in-sandbox code execution rather than full OS-level compromise. No public exploit identified at time of analysis, and SSVC confirms no known active exploitation and that the attack cannot be automated reliably.
Use-after-free in Google Chrome's DevTools component (all versions prior to 152.0.7977.65) enables remote attackers to execute arbitrary code inside the Chrome sandbox by distributing a crafted extension through social engineering. The CVSS 8.8 score reflects high confidentiality, integrity, and availability impact within the process scope, though exploitation is constrained by the mandatory user interaction required to install the malicious extension. No public exploit code exists and SSVC rates active exploitation as none at time of analysis, placing real-world urgency below what the raw score implies.
Improper state validation in Google Chrome's HTML parser (all versions prior to 152.0.7977.65) enables remote code execution within the browser's renderer sandbox when a user visits a crafted HTML page. The flaw (CWE-754) requires no authentication and minimal user interaction - simply loading malicious HTML is sufficient - but execution is constrained to the renderer sandbox (scope unchanged, S:U). Despite an 8.8 CVSS score, EPSS sits at 0.21% (12th percentile) and CISA SSVC confirms no current exploitation, with no public exploit or KEV listing identified at time of analysis.
Remote code execution in Google Chrome prior to 152.0.7977.65 stems from improper input validation in the browser's Media component, enabling a remote attacker to potentially execute arbitrary code outside the sandbox when a user visits a crafted HTML page. The vulnerability carries a CVSS base score of 8.8, affects all desktop Chrome builds below 152.0.7977.65 across Windows, macOS, and Linux, and is classified under CWE-20. No public exploit has been identified at time of analysis, and CISA SSVC rates current exploitation as none despite a total technical impact rating.
Remote code execution outside the browser sandbox is achievable in Google Chrome prior to 152.0.7977.65 via improper input validation in the Media component, triggered by visiting a crafted HTML page. The sandbox escape aspect is the critical differentiator here - Chrome's multi-process sandbox is its primary defense-in-depth layer, so bypassing it yields native OS-level code execution under the victim's account. No public exploit identified at time of analysis, and SSVC classifies exploitation as none with the attack non-automatable due to required user interaction.
Sandbox escape in Google Chrome's Media component on Windows allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox via a crafted HTML page. Affected versions are all Chrome releases on Windows prior to 152.0.7977.65. No public exploit code or active exploitation has been identified at time of analysis; SSVC assessment confirms exploitation status as none, and EPSS probability is low at 0.26% (17th percentile), though SSVC technical impact is rated total given full sandbox bypass capability.
Insufficient control flow management in Google Chrome's DevTools component (versions prior to 152.0.7977.65) enables remote attackers to execute arbitrary code inside the browser sandbox by tricking a user into loading a crafted HTML page via social engineering. The flaw is rooted in CWE-691 and permits attacker-controlled code paths within the DevTools subsystem, with execution constrained to within the Chrome sandbox (S:U). No public exploit code has been identified at time of analysis, and both EPSS (0.21%, 12th percentile) and SSVC (exploitation: none, automatable: no) indicate low current exploitation probability despite the high CVSS 8.8 base score.
Type confusion in Google Chrome's DevTools component prior to version 152.0.7977.65 enables remote code execution within the browser sandbox when a victim is social-engineered into visiting a crafted HTML page. The flaw affects all Chrome platforms where DevTools is accessible and results in high confidentiality, integrity, and availability impact to the sandboxed process. No public exploit code has been identified at time of analysis, and SSVC assessment confirms no observed active exploitation, though the technical impact rating is classified as total.
Use-after-free in V8, Google Chrome's JavaScript engine, prior to version 152.0.7977.65 enables remote attackers to execute arbitrary code within the Chrome sandbox by luring a user to a crafted HTML page. The CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R) confirms low-complexity, unauthenticated network delivery requiring only a single user visit, with high confidentiality, integrity, and availability impact scoped to the renderer process. No public exploit code has been identified at time of analysis, and SSVC rates exploitation as none with a non-automatable attack path, though technical impact is assessed as total within the sandbox.
Remote code execution within the Chrome sandbox is achievable via a race condition in the V8 JavaScript engine, affecting all Google Chrome versions prior to 152.0.7977.65. An unauthenticated remote attacker (per CVSS PR:N) can trigger the vulnerability by luring a user to a crafted HTML page, exploiting a timing window in V8's memory management to execute arbitrary code. No public exploit code or active exploitation has been identified at time of analysis; EPSS sits at 0.24th percentile and CISA SSVC records exploitation status as none, classifying this as a theoretical-but-patched risk for organizations that deploy promptly.
Use-after-free in Chrome's Chromoting (remote desktop) component allows a remote, unauthenticated attacker to potentially execute arbitrary code outside the browser sandbox via crafted network traffic, affecting all Chrome versions prior to 152.0.7977.65. The sandbox-escape dimension elevates this beyond a typical renderer vulnerability, as successful exploitation could yield code execution in a broader process context. No public exploit identified at time of analysis and SSVC indicates no observed exploitation, but the technical impact is rated total.
Sandbox-escaping remote code execution affects Google Chrome on macOS before 152.0.7977.65 through a use-after-free in the browser's Bluetooth component (CVE-2026-79091). A remote attacker who lures a victim into opening a crafted HTML page can trigger the freed-memory reuse to run arbitrary code outside the renderer sandbox, giving control of the host process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the sandbox-escape scope change drives a 9.6 CVSS base score despite Chromium's own Medium severity rating.
Sandbox-escaping remote code execution affects Google Chrome desktop before 152.0.7977.65, where a use-after-free in the ServiceWorker component lets a remote attacker run arbitrary code outside the renderer sandbox when a victim opens a crafted HTML page. The CVSS 3.1 score of 9.6 reflects the scope change (sandbox escape) and full CIA impact, though Google rated the Chromium severity only Medium and CISA's SSVC framework marks exploitation as none. No public exploit or CISA KEV listing exists at time of analysis, so risk is currently theoretical but high-impact.
Sandbox-escaping remote code execution affects Google Chrome on macOS prior to 152.0.7977.65, where a use-after-free in the Network component lets a remote attacker who convinces a victim to install a crafted extension run arbitrary code outside the renderer sandbox. Google rates the Chromium severity Medium, but the CVSS 9.6 reflects the scope-changing sandbox escape. No public exploit is identified at time of analysis and it is not on CISA KEV; EPSS is low at 0.24%.
Remote code execution outside Chrome's renderer sandbox is possible on macOS in all Chrome builds prior to 152.0.7977.65, triggered by improper input validation in the ANGLE graphics engine. An unauthenticated remote attacker (confirmed by PR:N in the provided CVSS vector) can exploit this by directing a macOS user to a specially crafted HTML page, which causes ANGLE to process malformed graphics input and execute attacker-controlled code outside the sandbox boundary. No CISA KEV listing or public exploit code exists at time of analysis, and an EPSS of 0.21% (12th percentile) indicates low current exploitation probability, though the zero-privilege-required, low-complexity attack path warrants prompt patching.
Out-of-bounds read in Google Chrome's ANGLE graphics engine on Windows prior to version 152.0.7977.65 enables remote attackers to potentially execute arbitrary code outside the browser sandbox. Exploitation requires no authentication and only that a victim navigate to a crafted HTML page, yielding a CVSS 8.8 score with high impact across confidentiality, integrity, and availability. A vendor-released patch is available; no public exploit or confirmed active exploitation has been identified at time of analysis.
Use-after-free in Chrome's UI layer allows a local attacker who has already achieved code execution inside the renderer process to escape the Chrome sandbox and execute arbitrary code on the underlying host system. All Google Chrome desktop releases prior to 152.0.7977.65 are affected per CPE cpe:2.3:a:google:chrome. No public exploit or CISA KEV listing exists at time of analysis, and EPSS sits at 0.12% (2nd percentile), consistent with a sophisticated chained exploit rather than mass exploitation; however, the Scope:Changed CVSS vector confirms this is a full sandbox escape with critical C/I/A impact once the preconditions are met.
Use-after-free in Google Chrome's DevTools component (all versions prior to 152.0.7977.65) allows a remote attacker to execute arbitrary code within the browser's renderer sandbox. Exploitation requires the victim to be socially engineered into installing and activating a crafted Chrome extension, making this a user-interaction-dependent attack rather than a passive drive-by. No active exploitation has been confirmed via CISA KEV, and SSVC classifies the exploitation status as none; however, SSVC also rates technical impact as total, meaning successful exploitation fully compromises confidentiality, integrity, and availability within the sandbox boundary.
Sandbox escape in Google Chrome's Media component (prior to 152.0.7977.65) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. Google has released a patched stable channel build (152.0.7977.65), with no public exploit code or active exploitation confirmed at time of analysis. EPSS sits at 0.21% (12th percentile) and SSVC rates the exploitation status as none with automatable: no, indicating this is a low-immediacy but technically severe sandbox escape requiring a two-stage attack chain.
Use-after-free in Chrome's Views UI component enables sandbox escape to arbitrary code execution outside the browser sandbox, affecting all Google Chrome versions prior to 152.0.7977.65. Exploitation requires an attacker who has already achieved renderer process compromise - making this a chained, second-stage attack rather than a direct initial access vector. No public exploit code has been identified and SSVC assessment confirms no active exploitation at time of analysis, though the technical impact is rated total due to the scope change across the sandbox boundary.
Incorrect authorization in the Chromoting component of Google Chrome on Windows prior to version 152.0.7977.65 enables a local attacker with standard user privileges to bypass system access restrictions by executing a crafted local program. The flaw (CWE-863) undermines Chrome Remote Desktop's authorization enforcement on Windows, allowing unauthorized access to protected system resources with both high confidentiality and integrity impact. No public exploit has been identified at time of analysis, and the EPSS score of 0.11% places this in the 1st percentile, indicating very low current exploitation probability despite the 7.1 CVSS base score.
GPU improper input validation in Google Chrome on Android (prior to 152.0.7977.65) enables a remote attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code at the OS level via a crafted HTML page. This is a chained sandbox escape - a second-stage exploit requiring a separate renderer compromise as a prerequisite, which the AC:H CVSS rating accurately reflects. No public exploit code has been identified and the vulnerability is absent from CISA KEV, but the full S:C/C:H/I:H/A:H impact ratings indicate that a successful chain yields complete browser compromise on Android.
Type confusion in Chrome's ANGLE graphics abstraction layer (all versions prior to 152.0.7977.65) enables remote attackers to potentially execute arbitrary code outside the browser sandbox by directing a user to a specially crafted HTML page. The CVSS 8.8 score reflects network-accessible delivery with no privilege requirements, full confidentiality, integrity, and availability impact, though user interaction is necessary. No public exploit identified at time of analysis; SSVC rates exploitation as 'none', yet technical impact is rated 'total' given the sandbox-escape language in the description.
Out-of-bounds write in ANGLE (Chrome's graphics abstraction layer) prior to version 152.0.7977.65 enables remote attackers to execute arbitrary code outside the browser sandbox by serving a crafted HTML page. The vulnerability carries a CVSS score of 8.8 and targets Chrome's Almost Native Graphics Layer Engine, a critical rendering subsystem, making exploitation viable against any unpatched Chrome user who visits a malicious page. No public exploit code or CISA KEV listing exists at time of analysis; EPSS probability is low at 0.30%, and SSVC assesses exploitation as 'none', suggesting real-world exploitation remains limited despite the high theoretical severity.
Out-of-bounds read in Chrome's Skia graphics library, affecting all versions prior to 152.0.7977.65, allows a remote unauthenticated attacker to leak sandbox-contained memory by delivering a crafted media file to a victim. The CVSS 8.1 score reflects high confidentiality and availability impact, though exploitation is bounded by Chrome's renderer sandbox. No public exploit or CISA KEV listing exists at time of analysis; a vendor patch is available and should be deployed via Chrome's standard update channel.
Remote code execution outside the browser sandbox is achievable in Google Chrome prior to 152.0.7977.65 via a race condition in ANGLE, the graphics API translation layer. Exploitation requires a victim to visit a crafted HTML page (UI:R), and the high attack complexity (AC:H) reflects the timing-sensitive, probabilistic nature of race condition exploitation. No public exploit code has been identified and CISA KEV does not list this CVE, though SSVC rates technical impact as total if exploitation succeeds.
Sandbox escape in Google Chrome for Android (versions prior to 152.0.7977.65) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox by delivering a crafted HTML page to the victim. The vulnerability stems from improper input validation in Chrome's Input subsystem on Android, confirmed by the CVSS scope-change metric (S:C) indicating the exploit crosses the sandbox boundary. No public exploit code or CISA KEV listing has been identified at time of analysis, and EPSS of 0.25% reflects the low automated exploitation probability attributable to the chained attack requirement.
Remote code execution outside the browser sandbox is potentially achievable in Google Chrome versions prior to 152.0.7977.65 through an integer overflow in the WebGL graphics subsystem triggered by visiting a crafted HTML page. The vulnerability affects all Chrome desktop platforms with a high-impact CVSS score of 8.8, though Chromium's internal severity rating of Medium and a low EPSS score of 0.25% (16th percentile) together suggest real-world exploitation remains uncommon at time of analysis. No public exploit code and no confirmed active exploitation have been identified; a vendor-released patch is available in stable channel update 152.0.7977.65.
Improper privilege management in Chrome's Regional Capabilities component allows remote attackers to bypass system access restrictions by delivering a crafted Chrome extension through social engineering. Affected versions are all Chrome releases prior to 152.0.7977.65 across desktop platforms. Despite a CVSS base score of 8.8, EPSS exploitation probability is very low at 0.21% (11th percentile), no active exploitation is confirmed in CISA KEV, and no public exploit code has been identified at time of analysis.
Remote code execution within the Chrome sandbox is possible in Google Chrome prior to 152.0.7977.65 via a stack-based buffer overflow in the V8 JavaScript engine, triggered by a crafted HTML page visited by an unpatched user. The vulnerability requires no authentication or elevated privileges from the victim - only that they visit an attacker-controlled page - and achieves arbitrary code execution within Chrome's renderer sandbox. No public exploit has been identified at time of analysis, and EPSS at 0.39% (31st percentile) indicates low current exploitation probability despite the 8.8 CVSS score; notably, Google's own internal severity rating is Medium, reflecting the sandbox containment.
Sandbox escape via a TOCTOU race condition in Google Chrome's Start component on Android prior to 152.0.7977.65 allows a local attacker to execute arbitrary code outside Chrome's sandbox. Exploitation requires a co-installed malicious application placed via social engineering, making opportunistic mass exploitation infeasible despite a CVSS base score of 8.1. No public exploit code exists and this vulnerability is absent from CISA KEV; EPSS sits at 0.15% (4th percentile), confirming low observed exploitation pressure. Vendor patch is available at version 152.0.7977.65.
Heap buffer overflow in Google Chrome's Media component prior to version 152.0.7977.65 enables remote code execution inside the renderer sandbox when a user visits a crafted HTML page. The CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U) reflects low attack complexity and no authentication requirement, but the unchanged scope (S:U) confirms execution is sandboxed - a full system compromise would require a separate sandbox escape not described in this CVE. No public exploit code has been identified and no CISA KEV listing exists; EPSS of 0.28% (20th percentile) indicates low observed exploitation activity, which is consistent with a patch-and-monitor posture rather than emergency response.
Heap-based buffer overflow in Google Chrome's WebRTC component (versions prior to 152.0.7977.65) enables a remote attacker to execute arbitrary code inside the Chrome renderer sandbox by delivering a crafted HTML page to a victim user. The CVSS score of 8.8 reflects broad impact (C:H/I:H/A:H) with no authentication prerequisite, though code execution is initially sandboxed and scope is unchanged (S:U). No public exploit code has been identified at time of analysis; SSVC records exploitation status as none and EPSS probability is low at 0.28% (20th percentile), suggesting this has not yet been leveraged at scale despite the high-severity rating.