macOS
Monthly
Sandbox escape in Google Chrome on macOS lets an attacker who has already compromised the renderer process execute arbitrary code outside the browser sandbox by delivering a crafted extension that abuses incorrect reference resolution in the Extensions subsystem, affecting all Mac builds prior to 155.0.8059.79. Google rates the issue High (Chromium severity: High) and has shipped a vendor fix, and there is no public exploit identified at time of analysis, with the CISA SSVC assessment recording exploitation as none. The impact is total once the chain fires (Scope:Changed, C:H/I:H/A:H), but high attack complexity (AC:H), required user interaction (UI:R) and the hard prerequisite of a prior renderer compromise make this a targeted second-stage escalation rather than a standalone remote exploit.
Incomplete cleanup in the Chromoting (Chrome Remote Desktop) component of Google Chrome on macOS before 155.0.8059.39 lets a remote, unauthenticated attacker bypass system access restrictions using crafted network traffic, per the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N vector. Impact is materially constrained: only macOS hosts on an affected build with Chromoting enabled and reachable are in scope, and the realistic outcome is limited information exposure rather than full compromise, which is consistent with the vendor's 'Low' Chromium severity rating. Risk signals conflict sharply - the supplied CVSS score of 9.1 (C:H/I:N/A:H) and the authoritative assessed vector of C:L/I:N/A:N disagree - and must be reconciled before prioritization; EPSS is negligible at 0.17% (6th percentile), there is no KEV listing, and no public exploit identified at time of analysis. Vendor-released patch: Chrome 155.0.8059.39.
Authorization bypass in the Chromoting (Chrome Remote Desktop) host component of Google Chrome on macOS prior to 155.0.8059.39 lets remote attackers circumvent macOS system access restrictions by sending crafted network traffic to the remoting service; the provided CVSS vector is AV:N/PR:N/UI:N so the flaw is treated as network-reachable and unauthenticated. Exploitation is conditional rather than opportunistic: it requires Chrome Remote Desktop (Chromoting) to be installed, enabled and network-reachable on a macOS host, and Google's Chromium team rated the underlying defect only 'Low' severity, which is why our independent assessment reduces impact to C:L/I:L/A:N with AC:H instead of the vendor's 9.1. No public exploit code or confirmed active exploitation has been identified at time of analysis, and EPSS is low at 0.21% (10th percentile), so this should not be triaged as a 9.1-equivalent emergency even though the vendor score is high.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where incorrect reference resolution in the WebAppInstalls component allows crafted network traffic to cross a process trust boundary. Exploitation is not standalone: the attacker must already have compromised the Chrome renderer process, which makes this a second-stage sandbox-escape primitive in a larger exploit chain rather than a directly reachable remote compromise, and the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects that non-trivial precondition. A vendor-released patch (Chrome 155.0.8059.39) is available, and no public exploit code was identified at the time of analysis.
Sandbox escape in Google Chrome on macOS, affecting releases prior to 155.0.8059.39, allows an attacker who has already compromised the browser's renderer process to execute arbitrary code outside the sandbox when the victim views a crafted HTML page. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H, base 8.3) confirms a network-reachable, scope-changing escape that requires user interaction and carries high confidentiality, integrity and availability impact once triggered, but the AC:H rating and CISA SSVC 'Automatable: no' reflect that it cannot be used standalone - a prior renderer compromise is a hard prerequisite. Per the authoritative assessment this is a chained second-stage exploit limited to macOS; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where a timing-dependent race condition (CWE-367) in the Core component can be won to break out of the renderer's sandbox. Exploitation is conditional rather than a single remote shot: the attacker must already have compromised the renderer process, must socially engineer the victim into opening and interacting with a crafted HTML page (UI:R), and must win a non-deterministic race that the AC:H rating and CISA's SSVC assessment (Exploitation: none, Automatable: no) indicate is unreliable and not readily scriptable. No public exploit code has been identified at time of analysis, and Google has shipped a fixed build, 155.0.8059.39; because the mandatory pre-existing renderer compromise is a high bar, this is best treated as a conditional priority to be handled through normal patching cadence rather than an emergency.
Local privilege escalation in ClamXAV versions 3.3 through 3.11 allows an attacker who already holds a low-privileged local account on a macOS host to execute arbitrary code with system privileges by winning a race condition in the bundled Privileged Helper Tool that combines with insufficient file validation. Exploitation is timing-dependent (AV:L/AC:H/PR:L/UI:N in the assessed vector, with high confidentiality, integrity, and availability impact) and typically requires repeated attempts rather than a single deterministic trigger, making this a credible but not emergency-tier priority; no public exploit code has been identified at time of analysis, and ClamXAV 3.11.1 fully remediates the flaw.
Heap-based buffer overflow in TeamViewer Full Client and Host for Linux and macOS before version 15.82 allows arbitrary code execution at the victim user's privilege level when a crafted .tvs session recording is opened through the 'Play or convert recorded session…' feature. Exploitation is gated by heavy prerequisites: the attacker must land the malicious file on the target host and socially engineer the user into opening it (CVSS 3.1 7.8, AV:L/AC:L/PR:N/UI:R), and the resulting code runs only as the current user with no privilege escalation and no network-reachable path. No public exploit code or confirmed active exploitation is identified at time of analysis, so real-world risk is materially below the raw score.
Out-of-bounds write in Apple's iOS, iPadOS, and macOS file-parsing code lets remote attackers achieve arbitrary code execution when a victim opens a maliciously crafted file, scoring CVSS 8.8 (AV:N/AC:L/PR:N/UI:R, CWE-787). Apple fixed the flaw in iOS 26.7.1, iPadOS 26.7.1, macOS Sequoia 15.8.1, and macOS Tahoe 26.7.1, and states it is aware of a report that the issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 27. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment records an exploitation value of 'none' with the attack assessed as non-automatable.
Local privilege escalation in Extegrity Exam4 on macOS lets any unprivileged local user escalate to full root by abusing command injection in the root-running com.extegrity.LogTool privileged helper, which is reachable over XPC. An attacker with a low-privileged local session (PR:L, AV:L, no user interaction required, UI:N) can send crafted XPC messages that reach [ConsoleLogHelper copyConsoleIntoFileFromStartDate:], where attacker-controlled parameters are passed into a syslog command without sanitization and executed with root privileges via LaunchSynchronous, yielding complete confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, HIGH). Exploitation requires the helper to be installed, registered, and reachable on the host; remote exploitation is not possible, and no public exploit code was identified at time of analysis.
A sandbox escape in Apple macOS allows a locally running sandboxed application to break out of its sandbox on unpatched versions below macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27, gaining full read, write, and execute privileges across the system. The flaw is a protection mechanism failure (CWE-693) in macOS sandbox enforcement logic, and the CVSS score of 8.8 reflects a scope change (S:C) with high confidentiality, integrity, and availability impact. No public exploit code or active exploitation is known at time of analysis, and EPSS is low at 0.17% (6th percentile).
Kernel memory corruption in Apple macOS disk image handling allows an attacker to crash the system or corrupt kernel memory when a user mounts a maliciously crafted disk image; affected versions are all macOS releases before Sequoia 15.8, Tahoe 26.7, and Golden Gate 27. Exploitation requires the victim to actively mount the image (UI:R) with no authentication needed (PR:N), and no public exploit code has been identified at time of analysis. Apple has released fixes, and EPSS is low (0.21%, 12th percentile), making this a genuine but not urgent patch priority.
An out-of-bounds read in the macOS kernel NFS client can terminate the system or corrupt kernel memory when the host connects to a malicious NFS server, and it affects macOS releases before Golden Gate 27, Tahoe 26.7, and Sequoia 15.8. The vendor rates it 7.5 (AV:N/AC:L/PR:N/UI:N), while our assessment adjusts to require user interaction (UI:R) because the victim host must mount or auto-mount an attacker-controlled NFS export - this is a client-side, attacker-server-initiated condition, not a remote hit against a listening service. No public exploit code was identified at time of analysis and EPSS is 0.20% (10th percentile); demonstrated impact is availability only, since code execution is not established. Apple has released vendor fixes.
Processing a maliciously crafted disk image on an unpatched Apple macOS system can trigger an out-of-bounds read that terminates the affected application unexpectedly. The issue affects macOS releases before Golden Gate 27, Sequoia 15.8, and Tahoe 26.7, and requires a local user with no privileges (PR:N) to open or mount the crafted image, meaning user interaction (UI:R) is the trigger rather than remote network access. Apple has shipped fixes in the three affected release trains, and there is no public exploit identified at time of analysis; EPSS is low at 0.17% (6th percentile), reflecting the local, interaction-dependent nature of the issue.
Kernel memory corruption in the macOS Apple Filing Protocol client (afpfs) can be triggered when a user connects to a malicious AFP server, for example by following an afp:// link or using 'Connect to Server'; the underlying out-of-bounds write is fixed in macOS Sequoia 15.7.8, macOS Sonoma 14.8.8 and macOS Tahoe 26.6. Exploitation is conditional rather than broadly wormable: the attacker is unauthenticated (PR:N) but must still induce the victim to initiate the AFP connection (UI:R), and any host running the patched builds is not affected. No public exploit code or confirmed active exploitation has been identified at time of analysis, and EPSS is low at 0.20% (10th percentile), so this is a genuine but socially mediated client-side kernel flaw rather than a mass-exploitation candidate.
An out-of-bounds read in Apple macOS lets a locally running application read kernel memory or trigger unexpected system termination, and is fixed in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. Exploitation is bounded by the CVSS vector (AV:L/AC:L/PR:L/UI:N) - the attacker must already have code executing as a local app on the host and no user interaction is needed - making this a post-access information-disclosure and denial-of-service primitive rather than a remote entry point. EPSS is only 0.17% (6th percentile) and no public exploit has been identified at time of analysis, consistent with a genuine but non-urgent local privilege issue.
An out-of-bounds read in Apple macOS allows memory disclosure and potential denial-of-service when the system processes a maliciously crafted 3D file, and is addressed by improved bounds checking in macOS Golden Gate 27, macOS Sequoia 15.8, and macOS Tahoe 26.7. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H, 7.1) confirms the path is local and unauthenticated but requires the victim to open or parse attacker-supplied content, so exploitation depends on social-engineering delivery rather than any remote/network-triggerable route. No public exploit code or confirmed active exploitation was identified at time of analysis, EPSS is a low 0.19% (9th percentile), and this is assessed as a moderate, not urgent, priority for fleets that have not yet patched.
An integer overflow in Apple macOS document processing can trigger an out-of-bounds read when a user opens a maliciously crafted file, resulting in potential disclosure of adjacent memory contents and/or a crash of the affected application. Affected versions are macOS releases below Golden Gate 27, below Tahoe 26.7, and below Sequoia 15.8; exploitation requires local handling of the crafted document plus mandatory user interaction (the victim must open the file), and no privileges are required per the CVSS vector (PR:N), but there is no remote or network-service exposure. Apple has released patched versions (Golden Gate 27, Tahoe 26.7, Sequoia 15.8), and no public exploit code or confirmed active exploitation has been identified at time of analysis; EPSS is 0.17% (6th percentile), consistent with a low-likelihood, user-interaction-dependent flaw, and the realistic impact is bounded to memory disclosure or denial of service rather than code execution.
Memory corruption during 3D model parsing on unpatched Apple platforms (iOS/iPadOS before 26.7 and 27, macOS Sequoia before 15.8 / Tahoe before 26.7 / Golden Gate 27, and tvOS, visionOS, watchOS before 27) allows an attacker who can get a victim to open or preview a maliciously crafted 3D model file to corrupt memory, potentially leading to code execution in the context of the parsing process with high confidentiality, integrity, and availability impact. The assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (7.3), so the practical barrier is user interaction - the target must parse the crafted asset locally; there is no remote unauthenticated network path, and no public exploit code has been identified at time of analysis (EPSS 0.20%, 10th percentile). Apple has shipped fixes; this is a genuine but moderate-priority issue rather than a top-tier emergency, since exploitation depends on social engineering plus a locally delivered file.
Local kernel memory corruption in Apple's 26.x operating-system family (iOS and iPadOS, macOS Tahoe, tvOS, visionOS, watchOS) allows an installed, running application to write to kernel memory or trigger unexpected system termination, with the flaw fixed in the 26.6 releases. The bug requires the victim to install and run a malicious or compromised app - it is not reachable over the network and needs no user interaction beyond launching that app (CVSS 7.8, AV:L/PR:L/UI:N) - and Apple's sandbox, notarization and App Review keep the delivery bar high, though a successful kernel-write primitive carries high confidentiality, integrity and availability impact. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and EPSS sits at 0.16% (6th percentile), indicating low near-term exploitation likelihood relative to the severity of the primitive itself.
A path traversal flaw (CWE-22) in Apple macOS is addressed by improved path validation and allows an attacker who controls a network directory server to execute arbitrary code with root privileges on a connecting client. Affected are macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27. Apple has shipped fixes in all three release trains. There is no public exploit code and no CISA KEV listing at time of analysis, and the CVSS 3.1 vector (7.8, AV:L/PR:L) reflects a local vector requiring the attacker to already hold a foothold as a directory service rather than a remote unauthenticated path.
Local sandbox authorization bypass in Apple macOS allows a malicious app already running on the target Mac to access user-sensitive data without proper authorization. Exploitation requires the user to run an untrusted application (UI:R) and affects macOS versions before Sequoia 15.8, Tahoe 26.7, and Golden Gate 27; the impact is limited to confidentiality disclosure with no integrity or availability effect. No public exploit was identified at time of analysis, EPSS is low at 0.19% (9th percentile), and vendor patches are available.
An out-of-bounds write (CWE-787) in Apple's operating system family - iOS/iPadOS, macOS (Sequoia, Tahoe, and Golden Gate), tvOS, visionOS, and watchOS - lets a remote attacker corrupt memory in an affected process, with the confirmed outcome being an application crash and the potential outcome being arbitrary code execution. Exploitation requires no authentication and no user interaction per the CVSS vector (AV:N/PR:N/UI:N), but the independent assessment rates attack complexity as High and the confirmed technical impact as limited to denial of service, because the specific component or content-processing surface that must be reached has not been documented and reliable code execution is unproven. Apple has released fixed builds for every affected platform, and no public exploit code or active exploitation has been identified at time of analysis; EPSS is a modest 0.99% (61st percentile), which is consistent with a patched, non-weaponized memory-safety defect rather than a top-tier emergency.
Sandbox escape in Apple iOS, iPadOS, and macOS allows a locally installed low-privileged malicious app to break out of its sandbox and gain elevated access to system resources, affecting iOS/iPadOS and macOS versions prior to 27 (macOS Golden Gate 27). Apple corrected the underlying permissions weakness (CWE-269, improper privilege management) by adding restrictions in the version 27 releases, so devices updated to iOS 27, iPadOS 27, or macOS Golden Gate 27 are remediated. The flaw is local-only with no remote or network trigger and requires the attacker to first get a malicious app onto the device; EPSS is 0.19% (8th percentile) and no public exploit identified at time of analysis, so risk is concentrated on devices that permit sideloaded, enterprise-provisioned, or otherwise untrusted applications.
Kernel out-of-bounds write in Apple macOS exFAT volume handling lets a local attacker who can get a maliciously crafted exFAT-formatted volume mounted - such as removable USB media or a disk image - trigger unexpected system termination (kernel panic) or disclose kernel memory. Only macOS builds below macOS Golden Gate 27 are affected; Apple fixed the flaw with improved bounds checking in macOS Golden Gate 27. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; EPSS is 0.14% (3rd percentile), and the attack is locally gated, requiring physical, removable-media, or delivery-based access rather than network reach.
Sandbox escape in Apple macOS (all releases prior to Golden Gate 27) allows an app already running inside the macOS App Sandbox to break out of its confinement by abusing improper symlink handling, fixed by Apple in macOS Golden Gate 27. The attacker must first get a malicious or compromised sandboxed app installed and running on the target (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N, CWE-59), so there is no remote or network vector and no user interaction is required beyond launching the app. No public exploit code has been identified and the issue is not in CISA KEV; EPSS is 0.14% (4th percentile), indicating low near-term exploitation likelihood.
Authorization bypass in Apple macOS allows a malicious or compromised application already running on the system to access sensitive user data it should not be able to reach. All macOS releases below Golden Gate 27, Tahoe 26.7, and Sequoia 15.8 are affected; the flaw is rooted in missing authorization checks (CWE-862) that Apple addressed through improved permission validation. Per the independent assessment the practical attack path is local rather than remote - the attacker must first get an app onto the device and executed, with Gatekeeper, notarization, App Store review, and TCC prompts acting as added barriers - and impact is confined to confidentiality (data disclosure) with no integrity or availability effect. No public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS is low (0.19%, 9th percentile), so risk is driven primarily by the widespread install base rather than observed attacks.
Apple macOS contains a process-entitlement verification flaw (CVE-2026-65381) that lets a malicious application break out of the App Sandbox, escalating its reach beyond the container it is supposed to be confined to. Affected systems are macOS versions prior to Golden Gate 27, Sequoia 15.8, and Tahoe 26.7; exploitation requires the attacker to first get their app onto the host and have it launched locally, after which no further privileges or user interaction are needed (assessed vector AV:L/PR:N/UI:N/S:C). The impact is a genuine security-boundary crossing with high confidentiality, integrity, and availability consequences, but EPSS is only 0.19% (9th percentile) and no public exploit code or confirmed in-the-wild exploitation has been identified at time of analysis.
Improper authorization handling in Apple macOS lets a locally running app reach sensitive user data it should not be permitted to access, because the underlying authorization state is not managed correctly. The flaw affects macOS versions prior to Golden Gate 27, Tahoe 26.7, and Sequoia 15.8, and exploits require a malicious or compromised application to already be executing on the target Mac - the external CVSS score of 7.5 (AV:N) is inconsistent with the vendor description and with our assessed vector of CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, which reflects a local, low-privileged precondition. No public exploit code has been identified at time of analysis and EPSS is 0.19% (9th percentile), though Apple has shipped fixes in the versions named above, so patching is the decisive control.
Kernel memory corruption in Apple macOS before Sequoia 15.8, Golden Gate 27, and Tahoe 26.7 can be triggered by a remote attacker, leading to unexpected system termination or kernel memory corruption. Exploitation requires network reachability to an unidentified service with no authentication or user interaction, though the assessed attack complexity is high (AC:H) and the exact trigger surface is unconfirmed. Apple has released patched versions, and no public exploit code has been identified; EPSS is low at 0.29%.
Apple macOS contains a local privilege-escalation flaw in which an application running on the system can escalate to root because entitlement checks were insufficient. Apple addressed the issue with additional entitlement validation, fixing it in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27; earlier releases (pre-15.8, pre-26.7) remain vulnerable. The attack is local (CVSS AV:L) and requires the attacker to already have code running as an ordinary user, so exploitation is typically a second-stage payload delivered by a malicious app or initial social-engineering lope rather than a remote network attack. No public exploit code and no CISA KEV entry were identified at time of analysis, and no EPSS score was supplied by the contributing sources.
Sign In With Apple state-management flaw in iOS, iPadOS, macOS, and visionOS lets a locally installed app hijack the authentication flow and obtain access to the victim's Apple Account. An attacker needs a malicious or compromised app already present on the device (AV:L) and the user must actively complete a Sign In With Apple prompt (UI:R), but no privileges or credentials are required by the app itself (PR:N), yielding high confidentiality and integrity impact on the linked Apple Account. Apple has shipped fixes in iOS/iPadOS 27, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, and visionOS 27; EPSS is low at 0.24% (15th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis.
Local privilege escalation in Apple macOS lets an application running with standard user privileges obtain root, giving an attacker full control of the host once code executes on the machine. The flaw is an improper access-control check (CWE-284) that Apple addressed with improved validation logic, fixed in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. No public exploit code has been identified and the vulnerability is not in CISA KEV; CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', so risk is concentrated in environments where untrusted local code can be executed.
Unexpected system termination (denial of service) can be induced on Apple macOS by a malicious or crafted application running on the host, with the underlying cause classified as an improper authentication weakness (CWE-287) that Apple addressed through improved authentication logic. Affected builds are macOS Sequoia before 15.8, macOS Tahoe before 26.6, and macOS Golden Gate before 27; the independent assessment recalibrates the vendor's network-oriented vector to a local one (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), meaning the attacker must first get code executing on the machine - no remote path, no privilege gain, no confidentiality or integrity loss, and no code execution beyond the crash. Exploitation requires both local access and a running malicious app, so practical risk is moderate rather than urgent: no public exploit code has been identified at time of analysis, EPSS is only 0.20% (10th percentile), and vendor-released patches (15.8, 26.6, 27) are available, though the CVE is tracked in the Apple/ENISA ecosystem (EUVD-2026-78030) and tagged as an authentication-bypass class issue.
Kernel memory corruption in Apple's iOS, iPadOS, and macOS allows a local attacker who can already execute code on the device to cause unexpected system termination or corrupt kernel memory, as described by the vendor's improved memory handling fix. Affected builds are iOS and iPadOS before 26.7 (and before 27), plus macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27; all are remediated by the corresponding vendor updates. Exploitation requires a prior on-device foothold (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8), so this realistically functions as a privilege-escalation or sandbox-escape stage rather than an initial-access vector - no public exploit has been identified at time of analysis, the issue is not confirmed actively exploited (no CISA KEV listing), and EPSS is low at 0.16% (6th percentile). It is a genuine but not top-tier priority: the impact is high if chained, but the barrier of local code execution limits reach.
An out-of-bounds read in Apple macOS versions prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27 can allow a locally executed application to crash a process or disclose its memory contents. The vulnerability requires a local attacker with low privileges (PR:L) and is not remotely exploitable; there is no network exposure. No public exploit code or active exploitation has been identified, and the EPSS score is low at 0.19%, indicating limited immediate risk.
An out-of-bounds read in Apple's operating system kernel lets a local user or a malicious/compromised app running on an affected device disclose kernel memory or crash the system, carrying a vendor CVSS 3.1 base score of 7.1 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H). The flaw affects iOS and iPadOS before 26.7/27, macOS Sequoia before 15.8, macOS Tahoe before 26.7, macOS Golden Gate before 27, and tvOS, visionOS and watchOS before 27; exploitation requires local code execution (AV:L, PR:L), there is no remote or network-triggerable path and no user-interaction requirement. Vendor-released patches addressing the issue are available in iOS 26.7/27, iPadOS 26.7/27, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, tvOS 27, visionOS 27 and watchOS 27; no public exploit code has been identified at time of analysis and EPSS is low at 0.20% (10th percentile), so this reads as a boundary/isolation bypass rather than an initial-access vector.
Local kernel memory corruption in Apple iOS and iPadOS (with parallel fixes in macOS, tvOS, visionOS and watchOS) lets an app already running on the device win a kernel race condition and either force an unexpected system termination or corrupt kernel memory, which can be leveraged toward full kernel read/write. Affected builds are iOS/iPadOS before 26.7 and before 27, macOS before 15.8, 26.7 (Tahoe) and 27 (Golden Gate), plus tvOS, visionOS and watchOS before 27; Apple has shipped fixes in every one of those branches. No public exploit code has been identified at time of analysis and EPSS is low at 0.18% (8th percentile), and because exploitation needs the attacker to already execute code as an app plus a timing-dependent race win, the vendor's own AV:L/PR:L vector (7.8 High) makes opportunistic mass exploitation impractical.
An out-of-bounds write in Apple's 3D model handling code causes memory corruption on unpatched iPhones, iPads, Macs, Apple TVs, Apple Vision Pro and Apple Watches when a maliciously crafted 3D model file is processed by the device. The flaw carries a CVSS 3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and was addressed by Apple with improved bounds checking in iOS/iPadOS 26.7 and 27, macOS Sequoia 15.8, macOS Tahoe 26.7 and macOS Golden Gate 27, plus tvOS 27, visionOS 27 and watchOS 27; no public exploit code has been identified at time of analysis, and EPSS places the likelihood of exploitation in the near term at only 0.17% (7th percentile). Exploitation is not remote-service based: the attacker must first deliver the crafted model to the victim's device and have it parsed, so it is best treated as a genuine but not urgent patching priority rather than an imminent threat.
An out-of-bounds write in Apple's asset-catalog handling lets a maliciously crafted asset catalog trigger memory corruption that terminates the affected process on unpatched Apple operating systems - iOS and iPadOS before 27, macOS before 15.8, 26.7, and 27, and tvOS, visionOS, and watchOS before 27. Exploitation is local rather than network-based (CVSS:3.1/AV:L/AC:L/PR:N/UI:R) and requires the victim to load or open the crafted asset via a downloaded app, bundle, or file, so the realistic outcome is client-side denial of service rather than remote code execution, despite the vendor's 7.8 base score; no public exploit code was identified at time of analysis and EPSS is only 0.20% (10th percentile), indicating low observed exploitation likelihood. Apple has released fixed versions across all affected platforms.
Insufficient path validation in Apple macOS lets a malicious application already running on a Mac escalate to elevated privileges, achieving high confidentiality and integrity impact. The issue is confirmed in macOS releases prior to Golden Gate 27, Sequoia 15.8, and Tahoe 26.7, and Apple has shipped fixes in those three versions (advisories support.apple.com/en-us/149035, 149042, 149043). Exploitation is local-only and constrained: an attacker must first get code running on the target (for example a downloaded or trojanized app) and user interaction is indicated in the CVSS vector, so this is a social-engineering or malware-delivery risk rather than an opportunistic remote attack; there is no public exploit identified at time of analysis and EPSS is 0.19% (9th percentile), indicating low predicted exploitation likelihood.
Sandbox escape in Apple macOS lets a malicious application break out of its App Sandbox and reach resources beyond its granted entitlements, affecting macOS releases prior to Tahoe 26.7 and prior to Golden Gate 27. The flaw is local in nature (CVSS:3.1/AV:L, PR:N, UI:R, S:C) - a remote attacker cannot trigger it directly, but exploitation requires convincing a user to launch a malicious or untrusted application on the target Mac, after which the app's scope of access changes (S:C) with high confidentiality impact. Apple has shipped fixes in macOS Tahoe 26.7 and macOS Golden Gate 27, so a vendor patch is available; no public exploit code has been identified and EPSS is low (0.17%, 6th percentile), with no confirmed active exploitation (no CISA KEV listing).
A locally installed app on Apple iOS/iPadOS (before 27), macOS (before Golden Gate 27, Tahoe 26.7, or Sequoia 15.8), tvOS 27, visionOS 27, and watchOS 27 can bypass insufficient path validation to modify files in protected system locations, corrupting system integrity. Exploitation requires the attacker to get a malicious or trojanized app running on the target device - there is no remote network path despite the vendor's published 9.8 network vector, and our independent assessment rates the issue CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N, with no authentication requirement and no user interaction beyond running the app. Vendor patches are available for all affected platforms, exploitation probability is low (EPSS 0.19%, 9th percentile), and no public exploit code has been identified at time of analysis.
Kernel memory corruption in Apple macOS versions prior to Golden Gate 27 allows a local attacker who can already execute code on the device to trigger an out-of-bounds buffer write, causing unexpected system termination or corruption of kernel memory. Apple addressed the flaw through improved size validation in macOS Golden Gate 27, and a vendor patch is available; no public exploit code has been identified and EPSS remains very low at 0.14% (4th percentile), suggesting limited near-term exploitation activity. Note that the vendor-supplied CVSS of 9.8 (AV:N/PR:N) conflicts with the advisory text, which explicitly describes a local attacker; the authoritative assessed vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, reflecting that the attacker must already be able to execute code on the target system and that exploitation cannot be launched remotely without a prior foothold.
Kernel memory corruption in Apple's operating systems lets an app already running on a device trigger a double free (CWE-415) that can corrupt kernel memory or crash the system unexpectedly. Affected are iOS and iPadOS before 26.7 and before 27, macOS before Sequoia 15.8, before Tahoe 26.7, and before Golden Gate 27, plus tvOS, visionOS, and watchOS before 27; the issue is fixed in those newer releases. Apple's own CVSS of 9.8 (AV:N/PR:N/UI:N) is not supported by the description, which frames the vector as a locally installed and executed app rather than a remote or unauthenticated service, and our independent assessment scores it as a local (AV:L) double-free with high availability and integrity impact but no confidentiality impact. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, and EPSS is only 0.21% (11th percentile), indicating low near-term exploitation likelihood.
Kernel memory corruption in Apple's operating systems (iOS/iPadOS 26.6.1, macOS Sequoia 15.8, macOS Tahoe 26.6.2, tvOS, visionOS and watchOS 27 and earlier) lets an application already running on the device crash the system or corrupt kernel memory, per Apple's advisory the root cause was addressed through improved memory handling. The independent assessment rates this as a local, app-gated issue (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H) rather than the vendor's network-reachable AV:N/PR:N vector of 7.5, meaning exploitation requires an attacker to first get code executing as an app on the target device; no elevated privileges or user interaction beyond launching the app are needed once that foothold exists. There is no public exploit identified at time of analysis, EPSS is low at 0.18% (7th percentile), and no CISA KEV listing applies; the practical outcome in most cases is a device crash or denial of service, with kernel memory corruption that would require additional work to turn into privilege escalation. Vendor-released patches are available across all affected platform lines.
On unpatched Apple platforms, opening a maliciously crafted video file can cause the affected app to terminate unexpectedly or leave process memory corrupted, because the underlying media parsing code fails to handle memory correctly. Affected are iOS/iPadOS before 26.6 or 26.7, macOS Sequoia before 15.8, macOS Tahoe before 26.6 or 26.7, tvOS before 26.6, and watchOS before 26.6; the vector is local (AV:L) with user interaction required (UI:R) and no authentication (PR:N), meaning an attacker must deliver the file and convince the user to open or preview it. There is no public exploit identified at time of analysis and EPSS is low (0.18%, 7th percentile), but the flaw is serious: the description substantiates only app crashes and in-process memory corruption, with no confirmed confidentiality disclosure or code-execution primitive, which is narrower than the vendor's 7.8 high-severity rating implies. Vendor patches are available.
Information disclosure in Apple iOS, iPadOS, macOS, visionOS, and watchOS before version 27 allows a malicious or privacy-abusing app already installed on the device to fingerprint the user by accessing identifiers that should be restricted by the sandbox. The vendor's CVSS 9.1 is drastically inflated and inconsistent with the description; our assessment is AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, with impact limited to privacy tracking rather than data theft, code execution, or system compromise. Apple fixed the issue in iOS 27, iPadOS 27, macOS Golden Gate 27, visionOS 27, and watchOS 27 by adding sandbox restrictions; no public exploit identified at time of analysis and EPSS is low at 0.16% (6th percentile).
Memory corruption during file parsing on Apple iOS/iPadOS (before version 27) and macOS (before Golden Gate 27) can cause the handling application to terminate unexpectedly when a user opens a maliciously crafted file; the flaw was addressed by strengthening input validation. Because the attack vector is local (the file must be delivered to and opened on the device) and user interaction is required, exploitation is not remote or unattended, and no special privileges are needed (PR:N, unauthenticated). The vendor rates this 7.8 High, but the independently assessed vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) reflects availability-only impact, and combined with a very low EPSS of 0.19% (8th percentile) and no public exploit identified at time of analysis, real-world risk is LOW-to-MODERATE rather than critical.
An out-of-bounds write in Apple's media-handling code can corrupt memory and terminate the affected app when a user opens or previews a maliciously crafted video file on an unpatched Apple OS. The flaw affects iOS/iPadOS before 26.7 and before 27, macOS before Sequoia 15.8, before Tahoe 26.7, and before Golden Gate 27, plus tvOS before 27 and visionOS before 27, and Apple resolved it with improved bounds checking in those releases. Exploitation requires local delivery of the crafted file plus user interaction (CVSS AV:L/UI:R/PR:N), no public exploit code has been identified at time of analysis, and EPSS is low at 0.18% (7th percentile), so the practical risk is bounded by the demonstrated outcome of app termination rather than confirmed remote or zero-click compromise.
Improper certificate validation in Apple's cross-platform certificate handling lets an attacker who controls a compromised intermediate certificate authority issue certificates with arbitrary extended key usages that unpatched devices will accept as valid, enabling spoofing or trust-bypass against TLS and other PKI-dependent services. Affected are iOS/iPadOS before 26.7 and before 27, macOS before 15.8, before 26.7 and before 27, plus tvOS before 27, watchOS before 27 and visionOS before 27; the vendor scores this CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) with unauthenticated remote attack, while our independent assessment keeps the same vector but raises attack complexity to High because the attack is only reachable after a trusted intermediate CA has already been compromised. No public exploit code has been identified at time of analysis (EPSS 0.14%, 4th percentile), and vendor patches are available offering the exact fixed versions listed below.
Improper handling of unexpected runtime conditions in Apple's operating systems lets a locally installed malicious app trigger an uncaught exception that terminates the system - a denial-of-service/crash impact with no confidentiality or code-execution effect. Affected platforms are iOS and iPadOS before 26.7 and before 27, macOS Tahoe before 26.7 and macOS Golden Gate before 27, plus tvOS 27, visionOS 27 and watchOS 27; the attacker must first get an app onto the device and execute it, and the payoff is only a transient system termination. There is no public exploit code and no confirmed active exploitation, EPSS is 0.18% (7th percentile), and Apple has shipped fixed versions, so this should be treated as a genuine but low-priority issue requiring routine patch cadence rather than emergency response.
Heap-based buffer overflow in Microsoft Office Word's document-parsing engine enables remote code execution when a victim opens a specially crafted file, yielding full confidentiality, integrity, and availability compromise of the user's session. Affected products span Microsoft 365 Apps for Enterprise, Office 2019, Office LTSC 2021, Office LTSC 2024, Word 2016, and corresponding macOS editions across both x86 and x64 architectures. No public exploit identified at time of analysis, but the AV:N/PR:N/UI:R CVSS pattern is historically associated with rapid phishing-campaign weaponization for Office document vulnerabilities.
Apple's iOS, iPadOS, macOS, tvOS, and watchOS contain a use-after-free vulnerability that could allow a local attacker to corrupt kernel memory or cause unexpected system crashes. An installed application can trigger this memory corruption flaw through user interaction, potentially leading to denial of service or unauthorized kernel-level modifications. No patch is currently available for this vulnerability (CVSS 7.1).
An access control vulnerability in macOS allows applications to connect to network shares without explicit user consent, bypassing the sandbox restrictions designed to prevent unauthorized network access. This affects macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, and macOS Tahoe 26.4, where a malicious or compromised application could silently establish connections to network resources. Apple has addressed this issue through additional sandbox restrictions in the specified patch versions; no public exploit code or active exploitation via KEV has been reported, but the nature of the vulnerability suggests moderate real-world risk due to the ease with which local applications could abuse this capability.
Sandbox escape vulnerability in macOS (Sequoia 15.7.4 and earlier, Sonoma 14.8.4 and earlier, Tahoe 26.3 and earlier) allows locally-installed applications to break out of their sandbox restrictions through a race condition. An attacker with the ability to run an application on an affected system could exploit this to gain unauthorized access outside the application's intended security boundaries. No patch is currently available for this HIGH severity vulnerability (CVSS 8.1).
macOS versions prior to Sequoia 15.7.5, Sonoma 14.8.5, and Tahoe 26.4 contain an out-of-bounds read vulnerability that allows local applications to access and disclose sensitive kernel memory. An attacker with the ability to run code on an affected system can exploit this memory disclosure to obtain privileged information that may aid in further system compromise. No patch is currently available for this HIGH severity vulnerability.
Improper state management in Apple's authentication mechanisms across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS allows attackers positioned on a network to intercept and potentially manipulate encrypted traffic. An attacker with privileged network access can exploit this vulnerability to conduct man-in-the-middle attacks without user interaction, compromising the confidentiality of communications. No patch is currently available for this high-severity flaw.
A buffer overflow vulnerability in Apple macOS Tahoe prior to version 26.4 enables remote attackers to trigger a denial-of-service condition through memory corruption and application crashes without requiring user interaction or authentication. The flaw stems from insufficient bounds checking and currently lacks a security patch. This vulnerability affects all macOS users running vulnerable versions.
Integer overflow vulnerability in Apple macOS (Sequoia 15.7.4 and earlier, Sonoma 14.8.4 and earlier, Tahoe 26.2 and earlier) allows remote attackers to trigger heap corruption by processing a specially crafted string without requiring user interaction or privileges. The vulnerability results in denial of service and potential memory corruption but currently lacks a public patch. No active exploitation has been reported.
A permissions enforcement vulnerability in Apple's operating systems allows applications to bypass access controls and read protected user data without proper authorization. The issue affects iOS and iPadOS versions prior to 26.3, and macOS Tahoe prior to 26.3. An attacker with a malicious app could exploit insufficient permission restrictions to access sensitive user information such as contacts, location data, photos, or other protected resources that should require explicit user consent.
Sandboxed processes on Apple macOS (Sequoia 15.7.5, Sonoma 14.8.5, and Tahoe 26.4) can escape sandbox isolation due to a race condition in state handling, allowing local attackers to bypass security restrictions and potentially execute arbitrary operations with elevated privileges. No patch is currently available for affected systems. The vulnerability requires local access and specific timing conditions but carries high impact across confidentiality, integrity, and availability.
Improper path validation in Apple's operating systems (iOS, iPadOS, macOS, and visionOS) allows applications to bypass directory access restrictions and read sensitive user data without user interaction. An attacker with a malicious app could exploit this parsing weakness to access confidential information across affected Apple devices. No patch is currently available, though Apple has released fixed versions across its product line.
A validation flaw in macOS entitlement verification allows applications to bypass privilege checks and gain elevated system privileges. The vulnerability affects macOS Sequoia 15.7.4 and earlier, macOS Sonoma 14.8.4 and earlier, and macOS Tahoe 26.3 and earlier. Apple has addressed this issue through improved validation of process entitlements in patched versions (15.7.5, 14.8.5, and 26.4 respectively), but no CVSS score, EPSS data, or KEV inclusion status is currently available, limiting immediate risk quantification.
A logic flaw in macOS Tahoe allows applications to bypass security controls and access sensitive user data without proper authorization. The vulnerability affects macOS versions prior to 26.4 and is addressed through improved input validation and access control checks. While CVSS scoring data is unavailable, Apple has released a patch indicating this is a genuine security concern requiring immediate attention.
This vulnerability is a memory handling flaw in Apple's operating systems (iOS, iPadOS, macOS, tvOS, visionOS, and watchOS) that allows a malicious application to trigger unexpected system termination or corrupt kernel memory. The vulnerability affects all versions prior to the version 26.4 releases across Apple's entire ecosystem. An attacker can exploit this by crafting a malicious app that triggers improper memory handling, potentially leading to denial of service or privilege escalation through kernel memory corruption.
Remote attackers can trigger denial-of-service conditions against multiple Apple operating systems (iOS, iPadOS, macOS variants) through network requests that bypass insufficient input validation. The vulnerability affects iOS 26.4 and earlier, iPadOS 26.4 and earlier, macOS Sequoia 15.7.4 and earlier, macOS Sonoma 14.8.4 and earlier, and macOS Tahoe 26.3 and earlier. No patch is currently available for this high-severity vulnerability with a 7.5 CVSS score.
Improper path validation in macOS (Sequoia 15.7.5, Sonoma 14.8.5, and Tahoe 26.4) allows sandboxed applications to escape their sandbox restrictions through directory path traversal. A local attacker with the ability to run malicious apps can exploit this weakness to execute code outside sandbox boundaries with full system privileges. No patch is currently available for this critical vulnerability.
A logic flaw in macOS Tahoe allows local users to elevate their privileges through improved checks that were insufficient in earlier versions. This vulnerability affects macOS versions prior to 26.4 and enables privilege escalation attacks from standard user accounts to higher privilege levels. Apple has patched this issue in macOS Tahoe 26.4, and no active exploitation or public proof-of-concept code has been reported.
Sandbox escape vulnerability in Apple iOS, iPadOS, macOS, and visionOS allows local attackers to break out of application sandboxes through improper path validation, potentially enabling unauthorized access to system resources and data. An attacker with local access could leverage this flaw to execute arbitrary operations outside application boundaries and bypass security restrictions. No patch is currently available for this critical vulnerability affecting multiple Apple platforms.
OpenClaw prior to version 2026.2.22 on macOS allows local attackers with user-level privileges to execute unauthorized binaries by bypassing path validation in the exec-approval allowlist mode through basename-only entries. An attacker can execute same-named local binaries without approval when the security allowlist policy is enabled, circumventing intended path-based restrictions. A patch is not currently available.
Path traversal in Apple and Kubernetes DAG management APIs allows authenticated attackers to access arbitrary files outside the intended directory by injecting URL-encoded forward slashes into file name parameters on GET, DELETE, RENAME, and EXECUTE endpoints. The vulnerability affects systems where a previous patch (CVE-2026-27598) only secured the CREATE endpoint while leaving other API functions unprotected. An attacker with valid credentials can read, modify, or execute unintended DAG files on the affected system.
SiYuan's Bazaar marketplace fails to sanitize package metadata (displayName, description) before rendering in the Electron desktop application, allowing stored XSS that escalates to arbitrary remote code execution. Any SiYuan user (versions ≤3.5.9) who browses the Bazaar will automatically execute attacker-controlled code with full OS-level privileges when a malicious package card renders-no installation or user interaction required. A functional proof-of-concept exists demonstrating command execution via img onerror handlers, and this vulnerability is actively tracked in GitHub's advisory database (GHSA-mvpm-v6q4-m2pf), making it a critical supply-chain risk to the SiYuan user community.
SiYuan's Bazaar (community package marketplace) fails to sanitize HTML in package README files during rendering, allowing stored XSS that escalates to remote code execution due to unsafe Electron configuration. An attacker can submit a malicious package with embedded JavaScript in the README that executes with full Node.js access when any user views the package details in the Bazaar. This affects SiYuan versions 3.5.9 and earlier across Windows, macOS, and Linux, with a CVSS score of 9.6 and multiple real-world exploitation vectors including data theft, reverse shells, and persistent backdoors.
OpenClaw versions prior to 2026.2.22 contain an allowlist bypass vulnerability in the macOS node-host system.run function that permits remote attackers with high privileges to execute arbitrary commands by exploiting improper parsing of command substitution tokens. Attackers can craft malicious shell payloads using command substitution syntax within double-quoted strings to circumvent security allowlists and achieve code execution. A patch is available from the vendor, and the vulnerability has been documented by VulnCheck with public advisory and GitHub security advisory references.
SiYuan's mobile file tree fails to sanitize notebook names in WebSocket rename events, allowing authenticated users to inject arbitrary HTML and JavaScript that executes in other clients' browsers. When combined with Electron's insecure configuration (nodeIntegration enabled, contextIsolation disabled), this stored XSS escalates to remote code execution with full Node.js privileges on affected desktop and mobile clients. The vulnerability affects users with notebook rename permissions across Docker, Node.js, Python, and Apple platforms.
Security vulnerability in RustDesk remote desktop client/server. One of 6+ critical CVEs affecting the open-source remote access platform.
RustDesk Client through version 1.4.5 transmits sensitive preset address book credentials in cleartext during heartbeat synchronization, enabling network eavesdropping attacks across Windows, macOS, Linux, iOS, and Android platforms. An attacker positioned to intercept network traffic can capture authentication credentials by sniffing the unencrypted JSON payload. No patch is currently available for this high-severity vulnerability (CVSS 8.7).
Security vulnerability in RustDesk remote desktop client/server. One of 6+ critical CVEs affecting the open-source remote access platform.
RustDesk Client through version 1.4.5 on Windows, macOS, and Linux uses weak password hashing and improper object prototype handling in its password security and configuration encryption modules, allowing local authenticated attackers to extract embedded sensitive data including passwords and machine identifiers. The vulnerability affects critical cryptographic functions including symmetric_crypt() and decrypt_str_or_original(), enabling attackers with local access and valid credentials to compromise encrypted credentials and system identifiers. No patch is currently available.
RustDesk Server Pro through version 1.7.5 uses weak cryptographic algorithms in configuration string generation and web console export functions, enabling attackers to extract sensitive embedded data from exported configurations. This vulnerability affects Windows, macOS, and Linux deployments and requires no authentication or user interaction to exploit. No patch is currently available.
RustDesk Client through version 1.4.5 uses a broken cryptographic algorithm that allows attackers to retrieve sensitive embedded data during config import, URI scheme handling, or CLI operations across Windows, macOS, Linux, iOS, Android, and web clients. An unauthenticated remote attacker can exploit this vulnerability without user interaction to extract sensitive configuration information. No patch is currently available for this high-severity vulnerability.
Textream prior to version 1.5.1 fails to validate the Origin header during WebSocket handshake, allowing malicious websites to establish unauthorized connections to the local DirectorServer and inject arbitrary commands. An attacker can exploit this from a browser to gain full remote control of teleprompter content without user interaction beyond visiting a compromised page. Public exploit code exists for this vulnerability; updating to version 1.5.1 or later resolves the issue.
Local privilege escalation via out-of-bounds memory read in Docker Desktop's grpcfuse kernel module (versions up to 4.61.0) on Linux, Windows, and macOS allows authenticated local attackers to achieve complete system compromise through manipulation of /proc/docker entries. The vulnerability requires local access and valid user credentials but enables reading and modifying arbitrary kernel memory with high impact on confidentiality, integrity, and availability. Docker Desktop 4.62.0 and later resolve this issue.
OpenClaw AI assistant on macOS versions 2026.2.13 and earlier is vulnerable to command injection through the credential refresh mechanism, which improperly handles user-controlled OAuth tokens when constructing shell commands for Keychain operations. An authenticated attacker with local access could exploit this to execute arbitrary OS commands with the privileges of the application user. The vulnerability has been patched in version 2026.2.14.
Apple's kernel across all platforms (iOS, macOS, watchOS, visionOS, tvOS) contains a memory corruption vulnerability (CVE-2026-20700, CVSS 7.8) that allows attackers with memory write capability to execute arbitrary code at the kernel level. KEV-listed with Apple confirming reports of sophisticated in-the-wild exploitation, this represents an active zero-day targeting the Apple ecosystem at its most fundamental security boundary.
Unprivileged local users on macOS can exploit a package validation bypass to escalate privileges to root through a vulnerable application. This high-severity issue affects macOS systems up to version 26.2 and requires local access with standard user privileges. A patch is not yet available, leaving affected systems exposed to privilege escalation attacks.
Improper symlink handling in macOS Tahoe versions prior to 26.3 allows local authenticated users to escalate privileges to root. An attacker with local access can exploit this vulnerability to gain complete system control. No patch is currently available.
Improper access control in TeamViewer clients (Windows, macOS, Linux) before version 15.74.5 permits authenticated remote users to circumvent confirmation-based access restrictions during active sessions. An attacker with valid remote session credentials can gain unauthorized access without triggering the expected local confirmation prompt, requiring only prior authentication via ID/password, session link, or Easy Access.
Salesforce Uni2TS time series forecasting library (through 1.2.0) has a code injection vulnerability that allows leveraging executable code in non-executable files across all platforms.
Sandbox escape in Google Chrome on macOS lets an attacker who has already compromised the renderer process execute arbitrary code outside the browser sandbox by delivering a crafted extension that abuses incorrect reference resolution in the Extensions subsystem, affecting all Mac builds prior to 155.0.8059.79. Google rates the issue High (Chromium severity: High) and has shipped a vendor fix, and there is no public exploit identified at time of analysis, with the CISA SSVC assessment recording exploitation as none. The impact is total once the chain fires (Scope:Changed, C:H/I:H/A:H), but high attack complexity (AC:H), required user interaction (UI:R) and the hard prerequisite of a prior renderer compromise make this a targeted second-stage escalation rather than a standalone remote exploit.
Incomplete cleanup in the Chromoting (Chrome Remote Desktop) component of Google Chrome on macOS before 155.0.8059.39 lets a remote, unauthenticated attacker bypass system access restrictions using crafted network traffic, per the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N vector. Impact is materially constrained: only macOS hosts on an affected build with Chromoting enabled and reachable are in scope, and the realistic outcome is limited information exposure rather than full compromise, which is consistent with the vendor's 'Low' Chromium severity rating. Risk signals conflict sharply - the supplied CVSS score of 9.1 (C:H/I:N/A:H) and the authoritative assessed vector of C:L/I:N/A:N disagree - and must be reconciled before prioritization; EPSS is negligible at 0.17% (6th percentile), there is no KEV listing, and no public exploit identified at time of analysis. Vendor-released patch: Chrome 155.0.8059.39.
Authorization bypass in the Chromoting (Chrome Remote Desktop) host component of Google Chrome on macOS prior to 155.0.8059.39 lets remote attackers circumvent macOS system access restrictions by sending crafted network traffic to the remoting service; the provided CVSS vector is AV:N/PR:N/UI:N so the flaw is treated as network-reachable and unauthenticated. Exploitation is conditional rather than opportunistic: it requires Chrome Remote Desktop (Chromoting) to be installed, enabled and network-reachable on a macOS host, and Google's Chromium team rated the underlying defect only 'Low' severity, which is why our independent assessment reduces impact to C:L/I:L/A:N with AC:H instead of the vendor's 9.1. No public exploit code or confirmed active exploitation has been identified at time of analysis, and EPSS is low at 0.21% (10th percentile), so this should not be triaged as a 9.1-equivalent emergency even though the vendor score is high.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where incorrect reference resolution in the WebAppInstalls component allows crafted network traffic to cross a process trust boundary. Exploitation is not standalone: the attacker must already have compromised the Chrome renderer process, which makes this a second-stage sandbox-escape primitive in a larger exploit chain rather than a directly reachable remote compromise, and the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects that non-trivial precondition. A vendor-released patch (Chrome 155.0.8059.39) is available, and no public exploit code was identified at the time of analysis.
Sandbox escape in Google Chrome on macOS, affecting releases prior to 155.0.8059.39, allows an attacker who has already compromised the browser's renderer process to execute arbitrary code outside the sandbox when the victim views a crafted HTML page. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H, base 8.3) confirms a network-reachable, scope-changing escape that requires user interaction and carries high confidentiality, integrity and availability impact once triggered, but the AC:H rating and CISA SSVC 'Automatable: no' reflect that it cannot be used standalone - a prior renderer compromise is a hard prerequisite. Per the authoritative assessment this is a chained second-stage exploit limited to macOS; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where a timing-dependent race condition (CWE-367) in the Core component can be won to break out of the renderer's sandbox. Exploitation is conditional rather than a single remote shot: the attacker must already have compromised the renderer process, must socially engineer the victim into opening and interacting with a crafted HTML page (UI:R), and must win a non-deterministic race that the AC:H rating and CISA's SSVC assessment (Exploitation: none, Automatable: no) indicate is unreliable and not readily scriptable. No public exploit code has been identified at time of analysis, and Google has shipped a fixed build, 155.0.8059.39; because the mandatory pre-existing renderer compromise is a high bar, this is best treated as a conditional priority to be handled through normal patching cadence rather than an emergency.
Local privilege escalation in ClamXAV versions 3.3 through 3.11 allows an attacker who already holds a low-privileged local account on a macOS host to execute arbitrary code with system privileges by winning a race condition in the bundled Privileged Helper Tool that combines with insufficient file validation. Exploitation is timing-dependent (AV:L/AC:H/PR:L/UI:N in the assessed vector, with high confidentiality, integrity, and availability impact) and typically requires repeated attempts rather than a single deterministic trigger, making this a credible but not emergency-tier priority; no public exploit code has been identified at time of analysis, and ClamXAV 3.11.1 fully remediates the flaw.
Heap-based buffer overflow in TeamViewer Full Client and Host for Linux and macOS before version 15.82 allows arbitrary code execution at the victim user's privilege level when a crafted .tvs session recording is opened through the 'Play or convert recorded session…' feature. Exploitation is gated by heavy prerequisites: the attacker must land the malicious file on the target host and socially engineer the user into opening it (CVSS 3.1 7.8, AV:L/AC:L/PR:N/UI:R), and the resulting code runs only as the current user with no privilege escalation and no network-reachable path. No public exploit code or confirmed active exploitation is identified at time of analysis, so real-world risk is materially below the raw score.
Out-of-bounds write in Apple's iOS, iPadOS, and macOS file-parsing code lets remote attackers achieve arbitrary code execution when a victim opens a maliciously crafted file, scoring CVSS 8.8 (AV:N/AC:L/PR:N/UI:R, CWE-787). Apple fixed the flaw in iOS 26.7.1, iPadOS 26.7.1, macOS Sequoia 15.8.1, and macOS Tahoe 26.7.1, and states it is aware of a report that the issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 27. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment records an exploitation value of 'none' with the attack assessed as non-automatable.
Local privilege escalation in Extegrity Exam4 on macOS lets any unprivileged local user escalate to full root by abusing command injection in the root-running com.extegrity.LogTool privileged helper, which is reachable over XPC. An attacker with a low-privileged local session (PR:L, AV:L, no user interaction required, UI:N) can send crafted XPC messages that reach [ConsoleLogHelper copyConsoleIntoFileFromStartDate:], where attacker-controlled parameters are passed into a syslog command without sanitization and executed with root privileges via LaunchSynchronous, yielding complete confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, HIGH). Exploitation requires the helper to be installed, registered, and reachable on the host; remote exploitation is not possible, and no public exploit code was identified at time of analysis.
A sandbox escape in Apple macOS allows a locally running sandboxed application to break out of its sandbox on unpatched versions below macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27, gaining full read, write, and execute privileges across the system. The flaw is a protection mechanism failure (CWE-693) in macOS sandbox enforcement logic, and the CVSS score of 8.8 reflects a scope change (S:C) with high confidentiality, integrity, and availability impact. No public exploit code or active exploitation is known at time of analysis, and EPSS is low at 0.17% (6th percentile).
Kernel memory corruption in Apple macOS disk image handling allows an attacker to crash the system or corrupt kernel memory when a user mounts a maliciously crafted disk image; affected versions are all macOS releases before Sequoia 15.8, Tahoe 26.7, and Golden Gate 27. Exploitation requires the victim to actively mount the image (UI:R) with no authentication needed (PR:N), and no public exploit code has been identified at time of analysis. Apple has released fixes, and EPSS is low (0.21%, 12th percentile), making this a genuine but not urgent patch priority.
An out-of-bounds read in the macOS kernel NFS client can terminate the system or corrupt kernel memory when the host connects to a malicious NFS server, and it affects macOS releases before Golden Gate 27, Tahoe 26.7, and Sequoia 15.8. The vendor rates it 7.5 (AV:N/AC:L/PR:N/UI:N), while our assessment adjusts to require user interaction (UI:R) because the victim host must mount or auto-mount an attacker-controlled NFS export - this is a client-side, attacker-server-initiated condition, not a remote hit against a listening service. No public exploit code was identified at time of analysis and EPSS is 0.20% (10th percentile); demonstrated impact is availability only, since code execution is not established. Apple has released vendor fixes.
Processing a maliciously crafted disk image on an unpatched Apple macOS system can trigger an out-of-bounds read that terminates the affected application unexpectedly. The issue affects macOS releases before Golden Gate 27, Sequoia 15.8, and Tahoe 26.7, and requires a local user with no privileges (PR:N) to open or mount the crafted image, meaning user interaction (UI:R) is the trigger rather than remote network access. Apple has shipped fixes in the three affected release trains, and there is no public exploit identified at time of analysis; EPSS is low at 0.17% (6th percentile), reflecting the local, interaction-dependent nature of the issue.
Kernel memory corruption in the macOS Apple Filing Protocol client (afpfs) can be triggered when a user connects to a malicious AFP server, for example by following an afp:// link or using 'Connect to Server'; the underlying out-of-bounds write is fixed in macOS Sequoia 15.7.8, macOS Sonoma 14.8.8 and macOS Tahoe 26.6. Exploitation is conditional rather than broadly wormable: the attacker is unauthenticated (PR:N) but must still induce the victim to initiate the AFP connection (UI:R), and any host running the patched builds is not affected. No public exploit code or confirmed active exploitation has been identified at time of analysis, and EPSS is low at 0.20% (10th percentile), so this is a genuine but socially mediated client-side kernel flaw rather than a mass-exploitation candidate.
An out-of-bounds read in Apple macOS lets a locally running application read kernel memory or trigger unexpected system termination, and is fixed in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. Exploitation is bounded by the CVSS vector (AV:L/AC:L/PR:L/UI:N) - the attacker must already have code executing as a local app on the host and no user interaction is needed - making this a post-access information-disclosure and denial-of-service primitive rather than a remote entry point. EPSS is only 0.17% (6th percentile) and no public exploit has been identified at time of analysis, consistent with a genuine but non-urgent local privilege issue.
An out-of-bounds read in Apple macOS allows memory disclosure and potential denial-of-service when the system processes a maliciously crafted 3D file, and is addressed by improved bounds checking in macOS Golden Gate 27, macOS Sequoia 15.8, and macOS Tahoe 26.7. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H, 7.1) confirms the path is local and unauthenticated but requires the victim to open or parse attacker-supplied content, so exploitation depends on social-engineering delivery rather than any remote/network-triggerable route. No public exploit code or confirmed active exploitation was identified at time of analysis, EPSS is a low 0.19% (9th percentile), and this is assessed as a moderate, not urgent, priority for fleets that have not yet patched.
An integer overflow in Apple macOS document processing can trigger an out-of-bounds read when a user opens a maliciously crafted file, resulting in potential disclosure of adjacent memory contents and/or a crash of the affected application. Affected versions are macOS releases below Golden Gate 27, below Tahoe 26.7, and below Sequoia 15.8; exploitation requires local handling of the crafted document plus mandatory user interaction (the victim must open the file), and no privileges are required per the CVSS vector (PR:N), but there is no remote or network-service exposure. Apple has released patched versions (Golden Gate 27, Tahoe 26.7, Sequoia 15.8), and no public exploit code or confirmed active exploitation has been identified at time of analysis; EPSS is 0.17% (6th percentile), consistent with a low-likelihood, user-interaction-dependent flaw, and the realistic impact is bounded to memory disclosure or denial of service rather than code execution.
Memory corruption during 3D model parsing on unpatched Apple platforms (iOS/iPadOS before 26.7 and 27, macOS Sequoia before 15.8 / Tahoe before 26.7 / Golden Gate 27, and tvOS, visionOS, watchOS before 27) allows an attacker who can get a victim to open or preview a maliciously crafted 3D model file to corrupt memory, potentially leading to code execution in the context of the parsing process with high confidentiality, integrity, and availability impact. The assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (7.3), so the practical barrier is user interaction - the target must parse the crafted asset locally; there is no remote unauthenticated network path, and no public exploit code has been identified at time of analysis (EPSS 0.20%, 10th percentile). Apple has shipped fixes; this is a genuine but moderate-priority issue rather than a top-tier emergency, since exploitation depends on social engineering plus a locally delivered file.
Local kernel memory corruption in Apple's 26.x operating-system family (iOS and iPadOS, macOS Tahoe, tvOS, visionOS, watchOS) allows an installed, running application to write to kernel memory or trigger unexpected system termination, with the flaw fixed in the 26.6 releases. The bug requires the victim to install and run a malicious or compromised app - it is not reachable over the network and needs no user interaction beyond launching that app (CVSS 7.8, AV:L/PR:L/UI:N) - and Apple's sandbox, notarization and App Review keep the delivery bar high, though a successful kernel-write primitive carries high confidentiality, integrity and availability impact. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and EPSS sits at 0.16% (6th percentile), indicating low near-term exploitation likelihood relative to the severity of the primitive itself.
A path traversal flaw (CWE-22) in Apple macOS is addressed by improved path validation and allows an attacker who controls a network directory server to execute arbitrary code with root privileges on a connecting client. Affected are macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27. Apple has shipped fixes in all three release trains. There is no public exploit code and no CISA KEV listing at time of analysis, and the CVSS 3.1 vector (7.8, AV:L/PR:L) reflects a local vector requiring the attacker to already hold a foothold as a directory service rather than a remote unauthenticated path.
Local sandbox authorization bypass in Apple macOS allows a malicious app already running on the target Mac to access user-sensitive data without proper authorization. Exploitation requires the user to run an untrusted application (UI:R) and affects macOS versions before Sequoia 15.8, Tahoe 26.7, and Golden Gate 27; the impact is limited to confidentiality disclosure with no integrity or availability effect. No public exploit was identified at time of analysis, EPSS is low at 0.19% (9th percentile), and vendor patches are available.
An out-of-bounds write (CWE-787) in Apple's operating system family - iOS/iPadOS, macOS (Sequoia, Tahoe, and Golden Gate), tvOS, visionOS, and watchOS - lets a remote attacker corrupt memory in an affected process, with the confirmed outcome being an application crash and the potential outcome being arbitrary code execution. Exploitation requires no authentication and no user interaction per the CVSS vector (AV:N/PR:N/UI:N), but the independent assessment rates attack complexity as High and the confirmed technical impact as limited to denial of service, because the specific component or content-processing surface that must be reached has not been documented and reliable code execution is unproven. Apple has released fixed builds for every affected platform, and no public exploit code or active exploitation has been identified at time of analysis; EPSS is a modest 0.99% (61st percentile), which is consistent with a patched, non-weaponized memory-safety defect rather than a top-tier emergency.
Sandbox escape in Apple iOS, iPadOS, and macOS allows a locally installed low-privileged malicious app to break out of its sandbox and gain elevated access to system resources, affecting iOS/iPadOS and macOS versions prior to 27 (macOS Golden Gate 27). Apple corrected the underlying permissions weakness (CWE-269, improper privilege management) by adding restrictions in the version 27 releases, so devices updated to iOS 27, iPadOS 27, or macOS Golden Gate 27 are remediated. The flaw is local-only with no remote or network trigger and requires the attacker to first get a malicious app onto the device; EPSS is 0.19% (8th percentile) and no public exploit identified at time of analysis, so risk is concentrated on devices that permit sideloaded, enterprise-provisioned, or otherwise untrusted applications.
Kernel out-of-bounds write in Apple macOS exFAT volume handling lets a local attacker who can get a maliciously crafted exFAT-formatted volume mounted - such as removable USB media or a disk image - trigger unexpected system termination (kernel panic) or disclose kernel memory. Only macOS builds below macOS Golden Gate 27 are affected; Apple fixed the flaw with improved bounds checking in macOS Golden Gate 27. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; EPSS is 0.14% (3rd percentile), and the attack is locally gated, requiring physical, removable-media, or delivery-based access rather than network reach.
Sandbox escape in Apple macOS (all releases prior to Golden Gate 27) allows an app already running inside the macOS App Sandbox to break out of its confinement by abusing improper symlink handling, fixed by Apple in macOS Golden Gate 27. The attacker must first get a malicious or compromised sandboxed app installed and running on the target (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N, CWE-59), so there is no remote or network vector and no user interaction is required beyond launching the app. No public exploit code has been identified and the issue is not in CISA KEV; EPSS is 0.14% (4th percentile), indicating low near-term exploitation likelihood.
Authorization bypass in Apple macOS allows a malicious or compromised application already running on the system to access sensitive user data it should not be able to reach. All macOS releases below Golden Gate 27, Tahoe 26.7, and Sequoia 15.8 are affected; the flaw is rooted in missing authorization checks (CWE-862) that Apple addressed through improved permission validation. Per the independent assessment the practical attack path is local rather than remote - the attacker must first get an app onto the device and executed, with Gatekeeper, notarization, App Store review, and TCC prompts acting as added barriers - and impact is confined to confidentiality (data disclosure) with no integrity or availability effect. No public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS is low (0.19%, 9th percentile), so risk is driven primarily by the widespread install base rather than observed attacks.
Apple macOS contains a process-entitlement verification flaw (CVE-2026-65381) that lets a malicious application break out of the App Sandbox, escalating its reach beyond the container it is supposed to be confined to. Affected systems are macOS versions prior to Golden Gate 27, Sequoia 15.8, and Tahoe 26.7; exploitation requires the attacker to first get their app onto the host and have it launched locally, after which no further privileges or user interaction are needed (assessed vector AV:L/PR:N/UI:N/S:C). The impact is a genuine security-boundary crossing with high confidentiality, integrity, and availability consequences, but EPSS is only 0.19% (9th percentile) and no public exploit code or confirmed in-the-wild exploitation has been identified at time of analysis.
Improper authorization handling in Apple macOS lets a locally running app reach sensitive user data it should not be permitted to access, because the underlying authorization state is not managed correctly. The flaw affects macOS versions prior to Golden Gate 27, Tahoe 26.7, and Sequoia 15.8, and exploits require a malicious or compromised application to already be executing on the target Mac - the external CVSS score of 7.5 (AV:N) is inconsistent with the vendor description and with our assessed vector of CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, which reflects a local, low-privileged precondition. No public exploit code has been identified at time of analysis and EPSS is 0.19% (9th percentile), though Apple has shipped fixes in the versions named above, so patching is the decisive control.
Kernel memory corruption in Apple macOS before Sequoia 15.8, Golden Gate 27, and Tahoe 26.7 can be triggered by a remote attacker, leading to unexpected system termination or kernel memory corruption. Exploitation requires network reachability to an unidentified service with no authentication or user interaction, though the assessed attack complexity is high (AC:H) and the exact trigger surface is unconfirmed. Apple has released patched versions, and no public exploit code has been identified; EPSS is low at 0.29%.
Apple macOS contains a local privilege-escalation flaw in which an application running on the system can escalate to root because entitlement checks were insufficient. Apple addressed the issue with additional entitlement validation, fixing it in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27; earlier releases (pre-15.8, pre-26.7) remain vulnerable. The attack is local (CVSS AV:L) and requires the attacker to already have code running as an ordinary user, so exploitation is typically a second-stage payload delivered by a malicious app or initial social-engineering lope rather than a remote network attack. No public exploit code and no CISA KEV entry were identified at time of analysis, and no EPSS score was supplied by the contributing sources.
Sign In With Apple state-management flaw in iOS, iPadOS, macOS, and visionOS lets a locally installed app hijack the authentication flow and obtain access to the victim's Apple Account. An attacker needs a malicious or compromised app already present on the device (AV:L) and the user must actively complete a Sign In With Apple prompt (UI:R), but no privileges or credentials are required by the app itself (PR:N), yielding high confidentiality and integrity impact on the linked Apple Account. Apple has shipped fixes in iOS/iPadOS 27, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, and visionOS 27; EPSS is low at 0.24% (15th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis.
Local privilege escalation in Apple macOS lets an application running with standard user privileges obtain root, giving an attacker full control of the host once code executes on the machine. The flaw is an improper access-control check (CWE-284) that Apple addressed with improved validation logic, fixed in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. No public exploit code has been identified and the vulnerability is not in CISA KEV; CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', so risk is concentrated in environments where untrusted local code can be executed.
Unexpected system termination (denial of service) can be induced on Apple macOS by a malicious or crafted application running on the host, with the underlying cause classified as an improper authentication weakness (CWE-287) that Apple addressed through improved authentication logic. Affected builds are macOS Sequoia before 15.8, macOS Tahoe before 26.6, and macOS Golden Gate before 27; the independent assessment recalibrates the vendor's network-oriented vector to a local one (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), meaning the attacker must first get code executing on the machine - no remote path, no privilege gain, no confidentiality or integrity loss, and no code execution beyond the crash. Exploitation requires both local access and a running malicious app, so practical risk is moderate rather than urgent: no public exploit code has been identified at time of analysis, EPSS is only 0.20% (10th percentile), and vendor-released patches (15.8, 26.6, 27) are available, though the CVE is tracked in the Apple/ENISA ecosystem (EUVD-2026-78030) and tagged as an authentication-bypass class issue.
Kernel memory corruption in Apple's iOS, iPadOS, and macOS allows a local attacker who can already execute code on the device to cause unexpected system termination or corrupt kernel memory, as described by the vendor's improved memory handling fix. Affected builds are iOS and iPadOS before 26.7 (and before 27), plus macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27; all are remediated by the corresponding vendor updates. Exploitation requires a prior on-device foothold (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8), so this realistically functions as a privilege-escalation or sandbox-escape stage rather than an initial-access vector - no public exploit has been identified at time of analysis, the issue is not confirmed actively exploited (no CISA KEV listing), and EPSS is low at 0.16% (6th percentile). It is a genuine but not top-tier priority: the impact is high if chained, but the barrier of local code execution limits reach.
An out-of-bounds read in Apple macOS versions prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27 can allow a locally executed application to crash a process or disclose its memory contents. The vulnerability requires a local attacker with low privileges (PR:L) and is not remotely exploitable; there is no network exposure. No public exploit code or active exploitation has been identified, and the EPSS score is low at 0.19%, indicating limited immediate risk.
An out-of-bounds read in Apple's operating system kernel lets a local user or a malicious/compromised app running on an affected device disclose kernel memory or crash the system, carrying a vendor CVSS 3.1 base score of 7.1 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H). The flaw affects iOS and iPadOS before 26.7/27, macOS Sequoia before 15.8, macOS Tahoe before 26.7, macOS Golden Gate before 27, and tvOS, visionOS and watchOS before 27; exploitation requires local code execution (AV:L, PR:L), there is no remote or network-triggerable path and no user-interaction requirement. Vendor-released patches addressing the issue are available in iOS 26.7/27, iPadOS 26.7/27, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, tvOS 27, visionOS 27 and watchOS 27; no public exploit code has been identified at time of analysis and EPSS is low at 0.20% (10th percentile), so this reads as a boundary/isolation bypass rather than an initial-access vector.
Local kernel memory corruption in Apple iOS and iPadOS (with parallel fixes in macOS, tvOS, visionOS and watchOS) lets an app already running on the device win a kernel race condition and either force an unexpected system termination or corrupt kernel memory, which can be leveraged toward full kernel read/write. Affected builds are iOS/iPadOS before 26.7 and before 27, macOS before 15.8, 26.7 (Tahoe) and 27 (Golden Gate), plus tvOS, visionOS and watchOS before 27; Apple has shipped fixes in every one of those branches. No public exploit code has been identified at time of analysis and EPSS is low at 0.18% (8th percentile), and because exploitation needs the attacker to already execute code as an app plus a timing-dependent race win, the vendor's own AV:L/PR:L vector (7.8 High) makes opportunistic mass exploitation impractical.
An out-of-bounds write in Apple's 3D model handling code causes memory corruption on unpatched iPhones, iPads, Macs, Apple TVs, Apple Vision Pro and Apple Watches when a maliciously crafted 3D model file is processed by the device. The flaw carries a CVSS 3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and was addressed by Apple with improved bounds checking in iOS/iPadOS 26.7 and 27, macOS Sequoia 15.8, macOS Tahoe 26.7 and macOS Golden Gate 27, plus tvOS 27, visionOS 27 and watchOS 27; no public exploit code has been identified at time of analysis, and EPSS places the likelihood of exploitation in the near term at only 0.17% (7th percentile). Exploitation is not remote-service based: the attacker must first deliver the crafted model to the victim's device and have it parsed, so it is best treated as a genuine but not urgent patching priority rather than an imminent threat.
An out-of-bounds write in Apple's asset-catalog handling lets a maliciously crafted asset catalog trigger memory corruption that terminates the affected process on unpatched Apple operating systems - iOS and iPadOS before 27, macOS before 15.8, 26.7, and 27, and tvOS, visionOS, and watchOS before 27. Exploitation is local rather than network-based (CVSS:3.1/AV:L/AC:L/PR:N/UI:R) and requires the victim to load or open the crafted asset via a downloaded app, bundle, or file, so the realistic outcome is client-side denial of service rather than remote code execution, despite the vendor's 7.8 base score; no public exploit code was identified at time of analysis and EPSS is only 0.20% (10th percentile), indicating low observed exploitation likelihood. Apple has released fixed versions across all affected platforms.
Insufficient path validation in Apple macOS lets a malicious application already running on a Mac escalate to elevated privileges, achieving high confidentiality and integrity impact. The issue is confirmed in macOS releases prior to Golden Gate 27, Sequoia 15.8, and Tahoe 26.7, and Apple has shipped fixes in those three versions (advisories support.apple.com/en-us/149035, 149042, 149043). Exploitation is local-only and constrained: an attacker must first get code running on the target (for example a downloaded or trojanized app) and user interaction is indicated in the CVSS vector, so this is a social-engineering or malware-delivery risk rather than an opportunistic remote attack; there is no public exploit identified at time of analysis and EPSS is 0.19% (9th percentile), indicating low predicted exploitation likelihood.
Sandbox escape in Apple macOS lets a malicious application break out of its App Sandbox and reach resources beyond its granted entitlements, affecting macOS releases prior to Tahoe 26.7 and prior to Golden Gate 27. The flaw is local in nature (CVSS:3.1/AV:L, PR:N, UI:R, S:C) - a remote attacker cannot trigger it directly, but exploitation requires convincing a user to launch a malicious or untrusted application on the target Mac, after which the app's scope of access changes (S:C) with high confidentiality impact. Apple has shipped fixes in macOS Tahoe 26.7 and macOS Golden Gate 27, so a vendor patch is available; no public exploit code has been identified and EPSS is low (0.17%, 6th percentile), with no confirmed active exploitation (no CISA KEV listing).
A locally installed app on Apple iOS/iPadOS (before 27), macOS (before Golden Gate 27, Tahoe 26.7, or Sequoia 15.8), tvOS 27, visionOS 27, and watchOS 27 can bypass insufficient path validation to modify files in protected system locations, corrupting system integrity. Exploitation requires the attacker to get a malicious or trojanized app running on the target device - there is no remote network path despite the vendor's published 9.8 network vector, and our independent assessment rates the issue CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N, with no authentication requirement and no user interaction beyond running the app. Vendor patches are available for all affected platforms, exploitation probability is low (EPSS 0.19%, 9th percentile), and no public exploit code has been identified at time of analysis.
Kernel memory corruption in Apple macOS versions prior to Golden Gate 27 allows a local attacker who can already execute code on the device to trigger an out-of-bounds buffer write, causing unexpected system termination or corruption of kernel memory. Apple addressed the flaw through improved size validation in macOS Golden Gate 27, and a vendor patch is available; no public exploit code has been identified and EPSS remains very low at 0.14% (4th percentile), suggesting limited near-term exploitation activity. Note that the vendor-supplied CVSS of 9.8 (AV:N/PR:N) conflicts with the advisory text, which explicitly describes a local attacker; the authoritative assessed vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, reflecting that the attacker must already be able to execute code on the target system and that exploitation cannot be launched remotely without a prior foothold.
Kernel memory corruption in Apple's operating systems lets an app already running on a device trigger a double free (CWE-415) that can corrupt kernel memory or crash the system unexpectedly. Affected are iOS and iPadOS before 26.7 and before 27, macOS before Sequoia 15.8, before Tahoe 26.7, and before Golden Gate 27, plus tvOS, visionOS, and watchOS before 27; the issue is fixed in those newer releases. Apple's own CVSS of 9.8 (AV:N/PR:N/UI:N) is not supported by the description, which frames the vector as a locally installed and executed app rather than a remote or unauthenticated service, and our independent assessment scores it as a local (AV:L) double-free with high availability and integrity impact but no confidentiality impact. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, and EPSS is only 0.21% (11th percentile), indicating low near-term exploitation likelihood.
Kernel memory corruption in Apple's operating systems (iOS/iPadOS 26.6.1, macOS Sequoia 15.8, macOS Tahoe 26.6.2, tvOS, visionOS and watchOS 27 and earlier) lets an application already running on the device crash the system or corrupt kernel memory, per Apple's advisory the root cause was addressed through improved memory handling. The independent assessment rates this as a local, app-gated issue (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H) rather than the vendor's network-reachable AV:N/PR:N vector of 7.5, meaning exploitation requires an attacker to first get code executing as an app on the target device; no elevated privileges or user interaction beyond launching the app are needed once that foothold exists. There is no public exploit identified at time of analysis, EPSS is low at 0.18% (7th percentile), and no CISA KEV listing applies; the practical outcome in most cases is a device crash or denial of service, with kernel memory corruption that would require additional work to turn into privilege escalation. Vendor-released patches are available across all affected platform lines.
On unpatched Apple platforms, opening a maliciously crafted video file can cause the affected app to terminate unexpectedly or leave process memory corrupted, because the underlying media parsing code fails to handle memory correctly. Affected are iOS/iPadOS before 26.6 or 26.7, macOS Sequoia before 15.8, macOS Tahoe before 26.6 or 26.7, tvOS before 26.6, and watchOS before 26.6; the vector is local (AV:L) with user interaction required (UI:R) and no authentication (PR:N), meaning an attacker must deliver the file and convince the user to open or preview it. There is no public exploit identified at time of analysis and EPSS is low (0.18%, 7th percentile), but the flaw is serious: the description substantiates only app crashes and in-process memory corruption, with no confirmed confidentiality disclosure or code-execution primitive, which is narrower than the vendor's 7.8 high-severity rating implies. Vendor patches are available.
Information disclosure in Apple iOS, iPadOS, macOS, visionOS, and watchOS before version 27 allows a malicious or privacy-abusing app already installed on the device to fingerprint the user by accessing identifiers that should be restricted by the sandbox. The vendor's CVSS 9.1 is drastically inflated and inconsistent with the description; our assessment is AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, with impact limited to privacy tracking rather than data theft, code execution, or system compromise. Apple fixed the issue in iOS 27, iPadOS 27, macOS Golden Gate 27, visionOS 27, and watchOS 27 by adding sandbox restrictions; no public exploit identified at time of analysis and EPSS is low at 0.16% (6th percentile).
Memory corruption during file parsing on Apple iOS/iPadOS (before version 27) and macOS (before Golden Gate 27) can cause the handling application to terminate unexpectedly when a user opens a maliciously crafted file; the flaw was addressed by strengthening input validation. Because the attack vector is local (the file must be delivered to and opened on the device) and user interaction is required, exploitation is not remote or unattended, and no special privileges are needed (PR:N, unauthenticated). The vendor rates this 7.8 High, but the independently assessed vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) reflects availability-only impact, and combined with a very low EPSS of 0.19% (8th percentile) and no public exploit identified at time of analysis, real-world risk is LOW-to-MODERATE rather than critical.
An out-of-bounds write in Apple's media-handling code can corrupt memory and terminate the affected app when a user opens or previews a maliciously crafted video file on an unpatched Apple OS. The flaw affects iOS/iPadOS before 26.7 and before 27, macOS before Sequoia 15.8, before Tahoe 26.7, and before Golden Gate 27, plus tvOS before 27 and visionOS before 27, and Apple resolved it with improved bounds checking in those releases. Exploitation requires local delivery of the crafted file plus user interaction (CVSS AV:L/UI:R/PR:N), no public exploit code has been identified at time of analysis, and EPSS is low at 0.18% (7th percentile), so the practical risk is bounded by the demonstrated outcome of app termination rather than confirmed remote or zero-click compromise.
Improper certificate validation in Apple's cross-platform certificate handling lets an attacker who controls a compromised intermediate certificate authority issue certificates with arbitrary extended key usages that unpatched devices will accept as valid, enabling spoofing or trust-bypass against TLS and other PKI-dependent services. Affected are iOS/iPadOS before 26.7 and before 27, macOS before 15.8, before 26.7 and before 27, plus tvOS before 27, watchOS before 27 and visionOS before 27; the vendor scores this CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) with unauthenticated remote attack, while our independent assessment keeps the same vector but raises attack complexity to High because the attack is only reachable after a trusted intermediate CA has already been compromised. No public exploit code has been identified at time of analysis (EPSS 0.14%, 4th percentile), and vendor patches are available offering the exact fixed versions listed below.
Improper handling of unexpected runtime conditions in Apple's operating systems lets a locally installed malicious app trigger an uncaught exception that terminates the system - a denial-of-service/crash impact with no confidentiality or code-execution effect. Affected platforms are iOS and iPadOS before 26.7 and before 27, macOS Tahoe before 26.7 and macOS Golden Gate before 27, plus tvOS 27, visionOS 27 and watchOS 27; the attacker must first get an app onto the device and execute it, and the payoff is only a transient system termination. There is no public exploit code and no confirmed active exploitation, EPSS is 0.18% (7th percentile), and Apple has shipped fixed versions, so this should be treated as a genuine but low-priority issue requiring routine patch cadence rather than emergency response.
Heap-based buffer overflow in Microsoft Office Word's document-parsing engine enables remote code execution when a victim opens a specially crafted file, yielding full confidentiality, integrity, and availability compromise of the user's session. Affected products span Microsoft 365 Apps for Enterprise, Office 2019, Office LTSC 2021, Office LTSC 2024, Word 2016, and corresponding macOS editions across both x86 and x64 architectures. No public exploit identified at time of analysis, but the AV:N/PR:N/UI:R CVSS pattern is historically associated with rapid phishing-campaign weaponization for Office document vulnerabilities.
Apple's iOS, iPadOS, macOS, tvOS, and watchOS contain a use-after-free vulnerability that could allow a local attacker to corrupt kernel memory or cause unexpected system crashes. An installed application can trigger this memory corruption flaw through user interaction, potentially leading to denial of service or unauthorized kernel-level modifications. No patch is currently available for this vulnerability (CVSS 7.1).
An access control vulnerability in macOS allows applications to connect to network shares without explicit user consent, bypassing the sandbox restrictions designed to prevent unauthorized network access. This affects macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, and macOS Tahoe 26.4, where a malicious or compromised application could silently establish connections to network resources. Apple has addressed this issue through additional sandbox restrictions in the specified patch versions; no public exploit code or active exploitation via KEV has been reported, but the nature of the vulnerability suggests moderate real-world risk due to the ease with which local applications could abuse this capability.
Sandbox escape vulnerability in macOS (Sequoia 15.7.4 and earlier, Sonoma 14.8.4 and earlier, Tahoe 26.3 and earlier) allows locally-installed applications to break out of their sandbox restrictions through a race condition. An attacker with the ability to run an application on an affected system could exploit this to gain unauthorized access outside the application's intended security boundaries. No patch is currently available for this HIGH severity vulnerability (CVSS 8.1).
macOS versions prior to Sequoia 15.7.5, Sonoma 14.8.5, and Tahoe 26.4 contain an out-of-bounds read vulnerability that allows local applications to access and disclose sensitive kernel memory. An attacker with the ability to run code on an affected system can exploit this memory disclosure to obtain privileged information that may aid in further system compromise. No patch is currently available for this HIGH severity vulnerability.
Improper state management in Apple's authentication mechanisms across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS allows attackers positioned on a network to intercept and potentially manipulate encrypted traffic. An attacker with privileged network access can exploit this vulnerability to conduct man-in-the-middle attacks without user interaction, compromising the confidentiality of communications. No patch is currently available for this high-severity flaw.
A buffer overflow vulnerability in Apple macOS Tahoe prior to version 26.4 enables remote attackers to trigger a denial-of-service condition through memory corruption and application crashes without requiring user interaction or authentication. The flaw stems from insufficient bounds checking and currently lacks a security patch. This vulnerability affects all macOS users running vulnerable versions.
Integer overflow vulnerability in Apple macOS (Sequoia 15.7.4 and earlier, Sonoma 14.8.4 and earlier, Tahoe 26.2 and earlier) allows remote attackers to trigger heap corruption by processing a specially crafted string without requiring user interaction or privileges. The vulnerability results in denial of service and potential memory corruption but currently lacks a public patch. No active exploitation has been reported.
A permissions enforcement vulnerability in Apple's operating systems allows applications to bypass access controls and read protected user data without proper authorization. The issue affects iOS and iPadOS versions prior to 26.3, and macOS Tahoe prior to 26.3. An attacker with a malicious app could exploit insufficient permission restrictions to access sensitive user information such as contacts, location data, photos, or other protected resources that should require explicit user consent.
Sandboxed processes on Apple macOS (Sequoia 15.7.5, Sonoma 14.8.5, and Tahoe 26.4) can escape sandbox isolation due to a race condition in state handling, allowing local attackers to bypass security restrictions and potentially execute arbitrary operations with elevated privileges. No patch is currently available for affected systems. The vulnerability requires local access and specific timing conditions but carries high impact across confidentiality, integrity, and availability.
Improper path validation in Apple's operating systems (iOS, iPadOS, macOS, and visionOS) allows applications to bypass directory access restrictions and read sensitive user data without user interaction. An attacker with a malicious app could exploit this parsing weakness to access confidential information across affected Apple devices. No patch is currently available, though Apple has released fixed versions across its product line.
A validation flaw in macOS entitlement verification allows applications to bypass privilege checks and gain elevated system privileges. The vulnerability affects macOS Sequoia 15.7.4 and earlier, macOS Sonoma 14.8.4 and earlier, and macOS Tahoe 26.3 and earlier. Apple has addressed this issue through improved validation of process entitlements in patched versions (15.7.5, 14.8.5, and 26.4 respectively), but no CVSS score, EPSS data, or KEV inclusion status is currently available, limiting immediate risk quantification.
A logic flaw in macOS Tahoe allows applications to bypass security controls and access sensitive user data without proper authorization. The vulnerability affects macOS versions prior to 26.4 and is addressed through improved input validation and access control checks. While CVSS scoring data is unavailable, Apple has released a patch indicating this is a genuine security concern requiring immediate attention.
This vulnerability is a memory handling flaw in Apple's operating systems (iOS, iPadOS, macOS, tvOS, visionOS, and watchOS) that allows a malicious application to trigger unexpected system termination or corrupt kernel memory. The vulnerability affects all versions prior to the version 26.4 releases across Apple's entire ecosystem. An attacker can exploit this by crafting a malicious app that triggers improper memory handling, potentially leading to denial of service or privilege escalation through kernel memory corruption.
Remote attackers can trigger denial-of-service conditions against multiple Apple operating systems (iOS, iPadOS, macOS variants) through network requests that bypass insufficient input validation. The vulnerability affects iOS 26.4 and earlier, iPadOS 26.4 and earlier, macOS Sequoia 15.7.4 and earlier, macOS Sonoma 14.8.4 and earlier, and macOS Tahoe 26.3 and earlier. No patch is currently available for this high-severity vulnerability with a 7.5 CVSS score.
Improper path validation in macOS (Sequoia 15.7.5, Sonoma 14.8.5, and Tahoe 26.4) allows sandboxed applications to escape their sandbox restrictions through directory path traversal. A local attacker with the ability to run malicious apps can exploit this weakness to execute code outside sandbox boundaries with full system privileges. No patch is currently available for this critical vulnerability.
A logic flaw in macOS Tahoe allows local users to elevate their privileges through improved checks that were insufficient in earlier versions. This vulnerability affects macOS versions prior to 26.4 and enables privilege escalation attacks from standard user accounts to higher privilege levels. Apple has patched this issue in macOS Tahoe 26.4, and no active exploitation or public proof-of-concept code has been reported.
Sandbox escape vulnerability in Apple iOS, iPadOS, macOS, and visionOS allows local attackers to break out of application sandboxes through improper path validation, potentially enabling unauthorized access to system resources and data. An attacker with local access could leverage this flaw to execute arbitrary operations outside application boundaries and bypass security restrictions. No patch is currently available for this critical vulnerability affecting multiple Apple platforms.
OpenClaw prior to version 2026.2.22 on macOS allows local attackers with user-level privileges to execute unauthorized binaries by bypassing path validation in the exec-approval allowlist mode through basename-only entries. An attacker can execute same-named local binaries without approval when the security allowlist policy is enabled, circumventing intended path-based restrictions. A patch is not currently available.
Path traversal in Apple and Kubernetes DAG management APIs allows authenticated attackers to access arbitrary files outside the intended directory by injecting URL-encoded forward slashes into file name parameters on GET, DELETE, RENAME, and EXECUTE endpoints. The vulnerability affects systems where a previous patch (CVE-2026-27598) only secured the CREATE endpoint while leaving other API functions unprotected. An attacker with valid credentials can read, modify, or execute unintended DAG files on the affected system.
SiYuan's Bazaar marketplace fails to sanitize package metadata (displayName, description) before rendering in the Electron desktop application, allowing stored XSS that escalates to arbitrary remote code execution. Any SiYuan user (versions ≤3.5.9) who browses the Bazaar will automatically execute attacker-controlled code with full OS-level privileges when a malicious package card renders-no installation or user interaction required. A functional proof-of-concept exists demonstrating command execution via img onerror handlers, and this vulnerability is actively tracked in GitHub's advisory database (GHSA-mvpm-v6q4-m2pf), making it a critical supply-chain risk to the SiYuan user community.
SiYuan's Bazaar (community package marketplace) fails to sanitize HTML in package README files during rendering, allowing stored XSS that escalates to remote code execution due to unsafe Electron configuration. An attacker can submit a malicious package with embedded JavaScript in the README that executes with full Node.js access when any user views the package details in the Bazaar. This affects SiYuan versions 3.5.9 and earlier across Windows, macOS, and Linux, with a CVSS score of 9.6 and multiple real-world exploitation vectors including data theft, reverse shells, and persistent backdoors.
OpenClaw versions prior to 2026.2.22 contain an allowlist bypass vulnerability in the macOS node-host system.run function that permits remote attackers with high privileges to execute arbitrary commands by exploiting improper parsing of command substitution tokens. Attackers can craft malicious shell payloads using command substitution syntax within double-quoted strings to circumvent security allowlists and achieve code execution. A patch is available from the vendor, and the vulnerability has been documented by VulnCheck with public advisory and GitHub security advisory references.
SiYuan's mobile file tree fails to sanitize notebook names in WebSocket rename events, allowing authenticated users to inject arbitrary HTML and JavaScript that executes in other clients' browsers. When combined with Electron's insecure configuration (nodeIntegration enabled, contextIsolation disabled), this stored XSS escalates to remote code execution with full Node.js privileges on affected desktop and mobile clients. The vulnerability affects users with notebook rename permissions across Docker, Node.js, Python, and Apple platforms.
Security vulnerability in RustDesk remote desktop client/server. One of 6+ critical CVEs affecting the open-source remote access platform.
RustDesk Client through version 1.4.5 transmits sensitive preset address book credentials in cleartext during heartbeat synchronization, enabling network eavesdropping attacks across Windows, macOS, Linux, iOS, and Android platforms. An attacker positioned to intercept network traffic can capture authentication credentials by sniffing the unencrypted JSON payload. No patch is currently available for this high-severity vulnerability (CVSS 8.7).
Security vulnerability in RustDesk remote desktop client/server. One of 6+ critical CVEs affecting the open-source remote access platform.
RustDesk Client through version 1.4.5 on Windows, macOS, and Linux uses weak password hashing and improper object prototype handling in its password security and configuration encryption modules, allowing local authenticated attackers to extract embedded sensitive data including passwords and machine identifiers. The vulnerability affects critical cryptographic functions including symmetric_crypt() and decrypt_str_or_original(), enabling attackers with local access and valid credentials to compromise encrypted credentials and system identifiers. No patch is currently available.
RustDesk Server Pro through version 1.7.5 uses weak cryptographic algorithms in configuration string generation and web console export functions, enabling attackers to extract sensitive embedded data from exported configurations. This vulnerability affects Windows, macOS, and Linux deployments and requires no authentication or user interaction to exploit. No patch is currently available.
RustDesk Client through version 1.4.5 uses a broken cryptographic algorithm that allows attackers to retrieve sensitive embedded data during config import, URI scheme handling, or CLI operations across Windows, macOS, Linux, iOS, Android, and web clients. An unauthenticated remote attacker can exploit this vulnerability without user interaction to extract sensitive configuration information. No patch is currently available for this high-severity vulnerability.
Textream prior to version 1.5.1 fails to validate the Origin header during WebSocket handshake, allowing malicious websites to establish unauthorized connections to the local DirectorServer and inject arbitrary commands. An attacker can exploit this from a browser to gain full remote control of teleprompter content without user interaction beyond visiting a compromised page. Public exploit code exists for this vulnerability; updating to version 1.5.1 or later resolves the issue.
Local privilege escalation via out-of-bounds memory read in Docker Desktop's grpcfuse kernel module (versions up to 4.61.0) on Linux, Windows, and macOS allows authenticated local attackers to achieve complete system compromise through manipulation of /proc/docker entries. The vulnerability requires local access and valid user credentials but enables reading and modifying arbitrary kernel memory with high impact on confidentiality, integrity, and availability. Docker Desktop 4.62.0 and later resolve this issue.
OpenClaw AI assistant on macOS versions 2026.2.13 and earlier is vulnerable to command injection through the credential refresh mechanism, which improperly handles user-controlled OAuth tokens when constructing shell commands for Keychain operations. An authenticated attacker with local access could exploit this to execute arbitrary OS commands with the privileges of the application user. The vulnerability has been patched in version 2026.2.14.
Apple's kernel across all platforms (iOS, macOS, watchOS, visionOS, tvOS) contains a memory corruption vulnerability (CVE-2026-20700, CVSS 7.8) that allows attackers with memory write capability to execute arbitrary code at the kernel level. KEV-listed with Apple confirming reports of sophisticated in-the-wild exploitation, this represents an active zero-day targeting the Apple ecosystem at its most fundamental security boundary.
Unprivileged local users on macOS can exploit a package validation bypass to escalate privileges to root through a vulnerable application. This high-severity issue affects macOS systems up to version 26.2 and requires local access with standard user privileges. A patch is not yet available, leaving affected systems exposed to privilege escalation attacks.
Improper symlink handling in macOS Tahoe versions prior to 26.3 allows local authenticated users to escalate privileges to root. An attacker with local access can exploit this vulnerability to gain complete system control. No patch is currently available.
Improper access control in TeamViewer clients (Windows, macOS, Linux) before version 15.74.5 permits authenticated remote users to circumvent confirmation-based access restrictions during active sessions. An attacker with valid remote session credentials can gain unauthorized access without triggering the expected local confirmation prompt, requiring only prior authentication via ID/password, session link, or Easy Access.
Salesforce Uni2TS time series forecasting library (through 1.2.0) has a code injection vulnerability that allows leveraging executable code in non-executable files across all platforms.