Apple
Monthly
Rsbuild versions before 2.0.9 contain a command injection flaw in the developer-server browser-launcher on macOS. The openBrowser() helper in packages/core/src/server/open.ts passes a URL through encodeURI() and then interpolates it into a string handed to child_process.exec(), and because encodeURI() leaves characters such as $, (, ), and ; untouched, a crafted URL is evaluated by /bin/sh and can execute arbitrary operating-system commands with the privileges of the developer running the dev server. The issue was fixed in the 2.0.9 release (upstream PR 7789), so a vendor-released patch is available; no CISA KEV listing or public exploit code was present in the supplied intelligence, and the attack requires local conditions on the developer machine.
MCPVault, a lightweight Model Context Protocol server that exposes Obsidian vault files to AI agents, fails to block access to restricted directories such as .git, .obsidian, and node_modules in versions prior to 0.11.4. PathFilter compiles its deny-list patterns case-sensitively and matches raw path segments, so on case-insensitive macOS and Windows filesystems variants like .Git/config or .GIT/config (and on Windows, trailing-dot/space forms such as .git./config) pass both isAllowed() and isAllowedForListing() while the operating system still opens the real restricted directory. An attacker who can influence a path selected by an AI agent can then read, write, move, search, or list sensitive repository and Obsidian metadata; no public exploit code or CISA KEV entry was identified at time of analysis.
Sandbox escape in Docker Sandboxes on macOS (0.28.0 through 0.41.x) lets a workload running inside a sandbox break out of its shared workspace and read or modify arbitrary files on the host as the VMM user, with host code execution possible where the reachable files are executable or otherwise privileged. The virtio-fs host server follows symlinks when reopening an unlinked file from a stored path, so a guest that replaces a parent directory of a workspace file with a symlink can redirect host-side file operations outside the workspace bind mount. Exploitation requires the attacker to already control a guest workload (for example an untrusted agent or repository), is macOS-specific, and depends on winning a directory-swap timing race; SSVC records Exploitation: none, and no public exploit code was identified at time of analysis. The raw 9.4 CVSS 4.0 score should be read alongside these preconditions rather than at face value - this is a genuine sandbox escape leading to host compromise, but it is not remotely reachable and is bounded by the privileges of the VMM user rather than root.
Apple iOS 18.7.10 and iPadOS 18.7.10 ship a fix for an input-validation flaw (CWE-20) that lets a remote attacker crash or otherwise deny service on unpatched devices, with Apple rating the impact as a full availability loss (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/A:H). Every iPhone or iPad still running a version below 18.7.10 is potentially affected. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so this is currently a patch-promptly issue rather than an emergency.
Local applications on macOS versions prior to 27 can escalate to root privileges because the operating system fails to properly validate entitlements before granting privileged operations (CWE-280). An attacker who can get a user to launch — or who can otherwise run — a crafted app on the target Mac gains full root-level control of the system, with high impact to confidentiality, integrity, and availability. The flaw is fixed in macOS Golden Gate 27 per Apple's advisory; no CISA KEV listing, no public exploit code, and no EPSS score were provided at time of analysis, so this is currently a patching-hygiene issue rather than a confirmed active threat.
A logic flaw in Apple macOS Sequoia, Tahoe, and Golden Gate allows an application running on the target Mac to force unexpected system termination, producing a denial-of-service condition that can crash the host and force a reboot. The flaw is fixed in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27 per Apple's advisories, and no public exploit code has been identified at time of analysis. EPSS is very low (0.17%, 6th percentile) and the issue is not listed in CISA KEV, so near-term mass exploitation is unlikely.
Kernel-level use-after-free in Apple's built-in NFS client allows memory corruption when a device connects to an attacker-operated NFS server, affecting iOS/iPadOS, macOS, tvOS, visionOS and watchOS. Exploitation requires the victim to mount or connect to a malicious NFS share (UI:R) but no credentials or privileges on the target device, making this a remote, unauthenticated-against-the-client attack that terminates in kernel memory corruption with high confidentiality, integrity and availability impact. No public exploit code and no CISA KEV listing were identified at time of analysis; EPSS is low at 0.18% (8th percentile), and CISA SSVC rates exploitation as none and automatable as no, though technical impact is total. Apple has released fixes 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.
Out-of-bounds write in Apple's file-parsing code affects iOS/iPadOS 27 and earlier, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, tvOS 27, visionOS 27, and watchOS 27, allowing a maliciously crafted file to corrupt memory when processed. Apple addressed the flaw with improved bounds checking across all listed platforms, and CVSS 3.1 scores it 7.8 (AV:L/AC:L/PR:L/UI:N) with high confidentiality, integrity, and availability impact, even though the advisory text itself describes only unexpected app termination. No publicly available exploit code and no CISA KEV listing were identified at time of analysis, and EPSS is 0.18% (7th percentile), indicating low near-term exploitation likelihood.
Local privilege escalation in Apple macOS Sequoia (before 15.7.8) and macOS Tahoe (before 26.6) lets a malicious application already running as a normal user obtain root privileges. Apple addressed the flaw by adding restriction checks in its permission-handling code, disclosing it only as 'a permissions issue'; fixed versions are macOS Sequoia 15.7.8 and macOS Tahoe 26.6. There is no CISA KEV listing and no public exploit code identified at time of analysis, and CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', so this is a patching-during-normal-maintenance item rather than an emergency remote threat.
Out-of-bounds memory access in the macOS SMB client kernel component allows a malicious or compromised SMB server to corrupt kernel memory when a victim connects to it, resulting in unexpected system termination or potentially kernel-level code execution. All macOS releases prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27 are affected. Apple has released fixed versions (support.apple.com advisories 149035, 149042, 149043); no public exploit code has been identified and EPSS is low at 0.17% (6th percentile), though the flaw is unauthenticated from the network perspective and requires only that the victim initiate an SMB connection.
Improper state management in Apple's operating systems (iOS/iPadOS, tvOS, visionOS, watchOS) allows a locally installed app to read a persistent account identifier that should have remained isolated, resulting in information disclosure. Affected platforms are all versions prior to the 27 release train on each OS. Vendor patches are available (iOS 27, iPadOS 27, tvOS 27, visionOS 27, watchOS 27), no public exploit code has been identified at time of analysis, and EPSS is very low (0.15%, 5th percentile). The supplied CVSS vector (AV:N/PR:N) does not match the description's local-app precondition, so treat the 7.5 score with caution.
Sandbox escape in Apple macOS lets a malicious or compromised application already running inside the macOS App Sandbox break out of that confinement and operate with privileges beyond what its sandbox profile permits (CVSS 3.1 base 8.4, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N). Affected systems are macOS releases prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27; exploitation requires the attacker to already have local code execution as a sandboxed app (for example, one the user installed and launched), and provides no remote initial access, functioning as a boundary-crossing primitive once code is running on the host. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; EPSS is 0.19% (9th percentile), so real-world activity appears limited, though the sandbox-boundary impact keeps this a serious local isolation flaw rather than a theoretical one.
An out-of-bounds write (CWE-787) in the Apple frameworks that parse 3D model files lets a maliciously crafted model corrupt memory when it is opened on an affected device, potentially giving the attacker code execution in the context of the processing application. The flaw affects iOS/iPadOS before 26.7 and 27, macOS Sequoia before 15.8, macOS Tahoe before 26.7, macOS Golden Gate 27, tvOS before 27, visionOS before 27 and watchOS before 27, and Apple has shipped fixes for all of them. Exploitation likelihood is low: EPSS is 0.17% (7th percentile), CISA SSVC records exploitation as 'none' and the vulnerability is not in KEV — no public exploit code has been identified, and the local attack vector with required user interaction makes mass exploitation unlikely.
Race condition in Apple's kernel state management lets a malicious sandboxed app escape its sandbox and execute arbitrary code with kernel privileges on iOS, iPadOS, macOS, tvOS, visionOS and watchOS. Exploitation requires a timing window to be won (CVSS AC:H) but no user interaction beyond launching the app, and success yields full control of the affected device. Apple shipped fixes in iOS/iPadOS 26.7 and 27, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, tvOS 27, visionOS 27 and watchOS 27; no public exploit code or CISA KEV listing was present in the provided data, and no EPSS
Improper state management in Apple iOS, iPadOS, and watchOS allows an installed app to track a user across other apps and websites without the user's permission, effectively defeating the platform's cross-app tracking consent controls. The flaw affects iOS/iPadOS releases before 26.7 and before 27, plus watchOS before 27, and is remediated by the iOS 26.7/iPadOS 26.7, iOS 27/iPadOS 27, and watchOS 27 updates. Exploitation requires a hostile app on the device rather than remote network access; EPSS is 0.15% (5th percentile), there is no CISA KEV listing or public exploit identified, and SSVC rates exploitation as 'none' with partial technical impact.
Improper handling of persistent identifiers in Apple's mobile and desktop operating systems allows an app installed on the device to recognize the same user across app reinstalls, defeating the identifier-reset behavior that users and administrators rely on for privacy. Apple states the issue is fixed in iOS 27 and iPadOS 27, macOS Golden Gate 27, and visionOS 27, and the affected CPE set covers all earlier releases of iOS/iPadOS, macOS, and visionOS. No public exploit code or CISA KEV entry has been reported at time of analysis, and EPSS is only 0.16% (6th percentile), so this is a privacy-integrity hardening fix rather than an emergency remote-code-execution patch.
Kernel memory corruption in Apple macOS can be triggered when a user mounts a maliciously crafted disk image, causing unexpected system termination or corruption of kernel memory. Apple addressed the CWE-120 buffer overflow with improved bounds checking in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. No public exploit code and no active exploitation have been identified, and the EPSS score is low (0.21%, 12th percentile), so practical exposure is dominated by local file-delivery scenarios rather than remote mass exploitation.
Sandboxed applications on Apple macOS can break out of their App Sandbox because of a logic error in the sandbox's validation checks, and Apple has fixed the issue in macOS 27 "Golden Gate". Any Mac running a macOS release earlier than 27 is affected, and successful exploitation gives a malicious app access to files, services, and resources it should never have been able to reach, matching the integrity-only impact (C:N/I:H) in the published vector. No public exploit code and no CISA KEV entry were identified at the time of analysis, and the EPSS score of 0.15% (5th percentile) suggests the flaw is not currently being exploited at scale.
Kernel-level out-of-bounds write (CWE-787) in the macOS SMB client stack allows a malicious SMB server to corrupt kernel memory when a target Mac connects to it, potentially yielding kernel code execution or a system crash. All macOS branches are affected: Sequoia before 15.8, Tahoe before 26.7, and macOS Golden Gate versions before 27. Apple has released patches for all three branches; there is no public exploit code identified, no CISA KEV listing, and EPSS is low (0.17%, 6th percentile), so exploitation is currently assessed as targeted/manual rather than widespread.
Local privilege escalation in Apple macOS lets a low-privileged local process obtain root via improper path validation (CWE-22), affecting macOS versions prior to Sequoia 15.8, Tahoe 26.7 and Golden Gate 27. Apple addressed the flaw with improved path validation, and the CVSS 7.8 vector (AV:L/AC:L/PR:L/UI:N, total CIA impact) reflects a reliable but non-automatable local escalation requiring an existing code-execution foothold. There is no CISA KEV listing and no public exploit identified at time of analysis; exploitation status is 'none' per CISA SSVC and the issue is not considered automatable.
A local sandbox-escape flaw in Apple macOS (CWE-284, improper access control via faulty state management) allows a malicious application to break out of its App Sandbox and operate outside the restricted environment it was granted. Affected versions are macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27, with Apple shipping fixes in all three (support.apple.com advisories 149035, 149042, 149043). CVSS 3.1 rates it 8.2 (AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N), but EPSS is only 0.19% (9th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis — so this is a high-severity, low-current-activity issue whose priority is driven by the App Sandbox being a core macOS security boundary rather than by observed exploitation.
Apple iOS and iPadOS before version 27 leak cross-application information through the handling of user preferences, allowing a locally installed app to enumerate which other apps are present on the device. Apple addressed the privacy flaw in iOS 27 and iPadOS 27; EPSS is only 0.17% (7th percentile), there is no CISA KEV listing, and no public exploit code identified at time of analysis. The practical impact is user profiling and device fingerprinting rather than code execution or data theft.
A race condition in Apple macOS (fixed in macOS Tahoe 26.6) allows a locally executed malicious application to escalate privileges and gain root on the host. The flaw is reachable by a low-privileged local process without user interaction beyond running the app, and it has a 7.8 CVSS base score reflecting total loss of confidentiality, integrity and availability for the vulnerable component. There is no CISA KEV listing, no vendor confirmation of in-the-wild exploitation, and no public exploit code identified at time of analysis; CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', indicating a targeted rather than wormable threat.
An out-of-bounds read in Apple's kernel (CWE-125) lets an app already running on the device read past the end of a kernel buffer, potentially leaking kernel memory or crashing the system. Affected platforms span iOS/iPadOS before 26.6.1, macOS Sequoia before 15.8, macOS Tahoe before 26.6.2, and tvOS, visionOS and watchOS before 27, with a CVSS 3.1 base of 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H). There is no CISA KEV listing and no public exploit identified at time of analysis; EPSS is 0.20% (10th percentile), so this is a local, app-mediated kernel hardening issue rather than a remotely exploitable emergency.
Resource exhaustion in Apple macOS allows a remote, unauthenticated attacker to deny service to legitimate users by feeding input that the operating system fails to bound correctly. Apple fixed the flaw with improved input validation in macOS Tahoe 26.7, macOS Sequoia 15.8, and macOS Golden Gate 27. It is rated 7.5 with an availability-only impact (CWE-400), and while no public exploit code or observed exploitation has been identified, the attack is network-reachable and fully automatable per CISA's SSVC assessment.
Race condition in Apple's kernel allows a local user on iOS 27, iPadOS 27, macOS Golden Gate 27, tvOS 27, visionOS 27 and watchOS 27 to cause unexpected system termination or read kernel memory. Apple fixed the flaw with additional validation, publishing advisories 149034-149038; there is no public exploit code and no confirmed active exploitation (EPSS 0.16%, SSVC exploitation: none).
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.
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.
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.
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.
Integer overflow in the macOS kernel NFS client can be triggered when an unpatched Mac connects to or mounts a share from a malicious or spoofed NFS server, leading to kernel memory corruption or unexpected system termination. Affected systems are macOS releases below Sequoia 15.8, Tahoe 26.7, and Golden Gate 27 (CPE cpe:2.3:a:apple:macos). The flaw is availability-only (CVSS 3.1 base 7.5; our assessment AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H), requires no credentials on the target but does require the victim to initiate an NFS client session, and is best exploited by an attacker positioned to serve or impersonate an NFS endpoint the victim reaches; no public exploit code has been identified at time of analysis, EPSS is low at 0.17% (6th percentile), and the issue is not in CISA KEV. Apple has released fixes, so patching removes the exposure entirely.
An out-of-bounds write in Apple macOS lets a malicious or compromised app running as a normal, unprivileged user corrupt memory and escalate to root privileges on the affected system. The flaw is fixed in macOS Golden Gate 27, macOS Tahoe 26.7, and macOS Sequoia 15.8; all earlier releases of those branches remain exposed (CWE-787, CVSS 7.8, AV:L/PR:L/UI:N). No public exploit code has been identified at time of analysis, and CISA's SSVC assessment rates exploitation as 'none' and non-automatable, so practical risk is currently confined to local post-compromise privilege escalation rather than mass remote attacks.
Local privilege escalation in Apple macOS allows a malicious or compromised application already running on the system to obtain root privileges. The flaw is a permissions-handling defect (CWE-280) that Apple addressed by adding additional restrictions, with fixes shipping in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. Exploitation requires local code execution as a normal user (AV:L, PR:L) and, per CISA SSVC, is not automatable with no known exploitation activity; no public exploit code or EPSS signal was provided at time of analysis.
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.
A use-after-free in Apple macOS kernel memory management allows a locally installed and executed app to escalate to kernel privileges and run arbitrary code with full system control. Affected releases are macOS before Sequoia 15.8, before Tahoe 26.7, and before Golden Gate 27; Apple shipped fixes in all three branches. The flaw is a local privilege escalation (CVSS 7.8, AV:L/PR:L) rather than a remote code execution bug, and there is no public exploit code or CISA KEV listing identified at time of analysis, so real-world exploitation currently depends on an attacker first getting a malicious app onto the target Mac.
Memory corruption in Apple's image-handling code across iOS 27, iPadOS 27, macOS Golden Gate 27 and visionOS 27 allows an attacker to achieve arbitrary code execution when a user processes a maliciously crafted image. Apple removed the vulnerable code entirely in the 27-generation releases, which are the only versions containing the fix; all earlier supported builds remain affected. The flaw is rated 7.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H), meaning exploitation needs local positioning plus some user interaction, and there is no public exploit code or CISA KEV entry identified at time of analysis.
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.
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.
Memory corruption in Apple macOS WebDAV client handling allows code execution when a user connects to an attacker-controlled WebDAV server, affecting macOS versions prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27. The flaw is an out-of-bounds write (CWE-787) reachable over the network but gated by user interaction, rated 8.8 by Apple/NVD with an unauthenticated network attack vector. Apple has released fixes in three OS updates, and exploitation is not confirmed — no public exploit code and no CISA KEV listing — while EPSS sits at 0.18% (8th percentile), indicating low predicted mass-exploitation activity; this reads as a credible but targeted risk rather than a wormable event.
Apple macOS contains a local privilege-escalation flaw in which an application running under an ordinary user account can abuse insufficient access-control checks to obtain root privileges. Devices are affected if they run macOS versions below Sequoia 15.8, Tahoe 26.7 or Golden Gate 27, and Apple has shipped fixes for all three release lines. CVSS 3.1 scores this 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and CISA's SSVC rates technical impact as total, but there is no CISA KEV listing, no reported exploitation and no public exploit code identified at time of analysis, so this is best treated as a high-value post-compromise escalation primitive rather than an imminent remote threat.
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.
Opening a maliciously crafted file on an unpatched Apple device can crash the component that parses it, because a buffer overflow in Apple's size-validation logic was only corrected in the latest OS releases. Affected platforms are iOS/iPadOS before 26.7 (and before 27), macOS Sequoia before 15.8, macOS Tahoe before 26.7, macOS Golden Gate before 27, tvOS before 27, and visionOS before 27; exploitation is local and requires the victim to actively open the attacker-supplied file, with no remote or network trigger available. The demonstrated outcome per Apple's advisory is unexpected process termination (denial of service) rather than code execution or data disclosure, and no public exploit code or confirmed active exploitation was identified at time of analysis, with EPSS at 0.22% (13th percentile).
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.
Path traversal in Apple iOS and iPadOS lets an attacker who physically holds a trust-paired iPhone or iPad read and write files outside the intended directory, a high-confidentiality and high-integrity impact on the device's file store. Everything running earlier than iOS/iPadOS 26.7 or iOS/iPadOS 27 is affected, and the vendor-released fixes are iOS 26.7, iPadOS 26.7, iOS 27 and iPadOS 27 (Apple advisories 149034 and 149041). Exploitation hinges on prior physical possession and an already-accepted 'Trust This Computer' relationship, so the published 7.5 score (CVSS:3.1/AV:N/PR:N) is inflated relative to the required prerequisites - the same vector's PR:N confirms no additional authentication is needed once the pairing exists - and exploitation risk is further limited by a low EPSS of 0.15 percent (5th percentile) with no public exploit identified at time of analysis.
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.
A use-after-free flaw in Apple's kernel affects iOS and iPadOS before 26.7, macOS Sequoia before 15.8, and macOS Golden Gate before 27, allowing a locally running app to corrupt kernel memory or cause unexpected system termination. The issue is a local, low-privilege memory-safety defect (CWE-416) rated CVSS 7.8, and Apple has shipped fixes in iOS 26.7, iPadOS 26.7, macOS Golden Gate 27 and macOS Sequoia 15.8. There is no indication of active exploitation (no CISA KEV listing) and no public exploit code identified, with EPSS at 0.19% (9th percentile) suggesting low near-term exploitation likelihood at scale.
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.
A remote input-validation weakness in Apple macOS allows crafted data to terminate an application unexpectedly or, more seriously, achieve arbitrary code execution on the host. Apple has fixed the flaw in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27, and only those or later builds are protected. Exploitation requires the victim to interact with the malicious content (CVSS UI:R, PR:N), there is no public exploit code identified at time of analysis, and neither CISA KEV nor the SSVC decision framework indicates observed exploitation, so this is best treated as a patch-now hygiene issue rather than an emergency.
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.
Unexpected system termination is possible on unpatched Apple macOS hosts because of an out-of-bounds read that a remote attacker can trigger without authentication or user interaction. Apple addressed the flaw with improved bounds checking in macOS Tahoe 26.7, macOS Sequoia 15.8, and macOS Golden Gate 27, but the affected system component is not named in the public advisories. No public exploit code has been identified and CISA's SSVC assessment records exploitation as 'none' while flagging the issue as automatable with partial technical impact; the CVSS 7.5 score is driven entirely by availability loss, with no confidentiality or integrity impact.
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.
Parsing a maliciously crafted file on an unpatched Mac can crash the affected application or leak contents of process memory, caused by an out-of-bounds read (CWE-125) in Apple's file-handling code. Apple has fixed the flaw in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27, with advisories published at support.apple.com. There is no public exploit code identified at time of analysis and no CISA KEV listing, and the EPSS probability is low at 0.19% (9th percentile), so this rates as a patch-on-schedule issue rather than an emergency.
An out-of-bounds write in Apple's WebKit engine — reachable by processing maliciously crafted web content — can corrupt memory and potentially lead to arbitrary code execution on affected Apple platforms. The flaw stems from an integer-overflow class defect (CWE-190) where a size calculation overflows and the subsequent bounds check fails, allowing an OOB write. It is fixed in Safari 26.6.1, iOS/iPadOS 26.6.1, macOS Tahoe 26.6.2, tvOS 27, visionOS 27 and watchOS 27; exploitation requires the victim to load attacker-controlled web content (UI:R), and no public exploit or active exploitation has been identified at time of analysis, with EPSS at just 0.17% (6th percentile).
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.
Missing entitlement checks in Apple's iOS and iPadOS, tvOS, watchOS, and visionOS (all versions before the 27 release train) allow a locally installed app to read device attributes it is not authorized to access and combine them into a persistent fingerprint of the user. Only devices running an affected platform with an attacker-supplied app already installed are exposed; the independent assessment re-scores the issue as local-access with confidentiality-only impact (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), which is materially lower than the supplied CVSS 3.1 vector (AV:N, 7.5) that treats the flaw as remotely reachable. There is no indication of active exploitation, KEV status is not set, and no public exploit code has been identified at time of analysis; EPSS is 0.19% (9th percentile), consistent with a low near-term exploit probability. Apple has released fixes in iOS 27, iPadOS 27, tvOS 27, visionOS 27, and watchOS 27.
Memory corruption in Apple Safari and the shared WebKit engine used across iOS, iPadOS, macOS Tahoe, tvOS, visionOS and watchOS can be triggered when a victim views maliciously crafted web content, rooted in an integer overflow (CWE-190) that was corrected through improved input validation. The CVSS 3.1 vector (8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates an unauthenticated network-delivered attack that requires user interaction but yields high confidentiality, integrity and availability impact, consistent with out-of-bounds memory effects rather than a confirmed code-execution chain. No public exploit code has been identified at time of analysis and CISA KEV does not list this CVE, while the EPSS score of 0.17% (6th percentile) signals a real but low-priority, non-urgent risk that is best addressed through routine patching. Patches are available from the vendor in Safari 26.6.1, iOS 26.6.1 and iPadOS 26.6.1, macOS Tahoe 26.6.2, tvOS 27, visionOS 27 and watchOS 27.
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.
User fingerprinting on Apple iOS and iPadOS devices running versions earlier than 26.6 allows an installed application to identify and track the device owner through sensitive data that Apple has now relocated as part of version 26.6. Per the authoritative assessment, this is an on-device, local-execution privacy flaw (CWE-359) with no additional privileges or user interaction required beyond the app running, and its impact is limited to tracking/fingerprinting rather than data theft, code execution, or system compromise; the supplied AV:N/high-confidentiality vector is not borne out by analysis. Exploitation requires getting a malicious or privacy-abusing app onto the device via the App Store, sideloading, MDM/enterprise provisioning, or TestFlight, and devices already updated to iOS/iPadOS 26.6 are not affected. There is no public exploit identified at time of analysis, no CISA KEV listing, and EPSS is low at 0.14% (4th percentile).
A local privilege-escalation flaw in Apple's operating system family lets a malicious app already running on the device obtain root privileges by exploiting a missing authorization check. Apple addressed the issue with 'additional restrictions' in iOS 26.7 and iPadOS 26.7, iOS 27 and iPadOS 27, macOS Golden Gate 27, and visionOS 27, and the CVSS 3.1 score is 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is not confirmed: the issue is not in CISA KEV, no public exploit code is identified, and CISA's SSVC assessment lists exploitation as 'none' and automatable as 'no', though technical impact is rated 'total' once root is achieved.
Memory corruption in Apple's 3D model parsing pipeline allows a local attacker with low privileges to trigger a classic buffer overflow (CWE-120) on iOS/iPadOS, macOS, tvOS, visionOS and watchOS when a victim opens a maliciously crafted 3D model file. Apple addressed the flaw with improved memory handling in iOS 26.7/27, iPadOS 26.7/27, macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7, tvOS 27, visionOS 27 and watchOS 27. Exploitation requires local access and user interaction, no public exploit code has been identified at time of analysis, and the EPSS score is very low at 0.17% (7th percentile), so this is a credible patching priority for Apple fleets rather than a mass-exploitation emergency.
Privilege escalation to root in Parallels Desktop for Mac via argument injection into a tar command executed by the root-owned dispatcher service. Any local user - no admin rights required - can connect to the world-writable `/var/run/prl_disp_service.socket`, authenticate via `PrlSrv_LoginLocal` without signature verification, and then pass a crafted appliance path through `PrlSrv_InstallAppliance` that embeds a quote character to escape the Qt `QProcess::splitCommand` argument boundary, injecting `--use-compress-program=<binary>` into macOS tar and running arbitrary code as root. No public exploit has been identified at time of analysis, but the exploitation path requires no special conditions beyond a local user account.
Out-of-bounds read and write in the Linux kernel's forcedeth NVIDIA ethernet driver triggers on every S3 suspend/resume cycle due to an off-by-one loop terminator in nv_suspend() and nv_resume(). The loop runs one iteration past the end of the saved_config_space[] array, overwriting adjacent kernel memory (np->name_rx[]) and issuing a stray MMIO write one dword beyond the ioremap'd hardware window; with CONFIG_UBSAN_TRAP=y the kernel aborts during the suspend path. The bug has existed since Linux 2.6.27 but was only surfaced by UBSAN on Apple Macmini3,1 (MCP79) hardware during S3 cycling. No public exploit has been identified at time of analysis.
Remote unauthenticated denial-of-service in AirSane scanner server (versions prior to 0.4.12) allows an attacker to crash the daemon by sending an HTTP POST request with an arbitrarily large Content-Length value, triggering memory exhaustion and a std::bad_alloc exception. The root cause is in httpserver.cpp, where the Content-Length header value is passed directly to std::string::resize() with no upper-bound validation. A secondary variant using non-numeric Content-Length values produces undefined behavior via NaN-to-integer conversion. No public exploit or active exploitation has been identified at time of analysis.
Stack-based buffer overflow in Tesseract OCR 5.5.3 and earlier corrupts the stack during legacy engine initialization, enabling denial of service and potential control-flow hijacking when a crafted `.traineddata` file is processed. The flaw originates in `Classify::ReadNormProtos` (normmatch.cpp), where unbounded `std::istream::operator>>(char*)` extraction into a fixed 61-byte stack buffer allows a 99-character NORMPROTO token to overwrite up to 39 bytes beyond the buffer boundary during `TessBaseAPI::Init`. No fixed release is available at time of analysis; an upstream fix commit exists but has not been tagged as a release, and no public exploit has been identified at time of analysis.
Buffer overflow in the Apple Notification Center Service (ANCS) event handler of the Pavlok Behavioral Conditioning Wearable allows unauthenticated adjacent-network attackers to achieve full compromise of the wearable device and potentially the paired Apple host. The vulnerability resides in firmware versions up to build 20260707 and is exploitable by any attacker within Bluetooth Low Energy range without credentials. A proof-of-concept has been published (CVSS 4.0 E:P); the vendor did not respond to coordinated disclosure, and no patch has been released.
Remote code execution in Google Chrome on iOS before 153.0.8010.36 stems from a use-after-free in the Sharing component (CWE-416), letting a remote attacker who lures a victim to crafted network content execute arbitrary code outside the browser sandbox. Google has shipped a patched Chrome build; no public exploit is identified at time of analysis, and Google/Chromium rated the underlying bug 'Medium' severity even though the assigned CVSS base score is 9.6.
Local privilege escalation in Waves Central for macOS (versions up to 16.6.2) allows any authenticated local user to gain root code execution by abusing a flawed XPC client authorization scheme in the product's privileged helper service. The helper validates connecting XPC clients by performing a certificate-chain equality comparison against itself rather than enforcing a pinned code requirement (application identifier and Apple Team ID), meaning any process carrying the Waves signing certificate can impersonate a legitimate client and instruct the helper to run arbitrary scripts as root. No public exploit has been identified at time of analysis; a vendor-released fix is available in version 17.0.
Privilege escalation and local code execution affect the OpenTelemetry.Resources.Host NuGet package (opentelemetry-dotnet-contrib) on macOS prior to version 1.16.0-beta.2. The host.id resource attribute detector invokes sh and ioreg using bare names resolved through the PATH environment variable rather than absolute paths, allowing a local attacker with fewer privileges than the host application to substitute malicious binaries and execute arbitrary code in the application's security context. No public exploit has been identified at time of analysis; Linux and Windows hosts are explicitly unaffected.
Sandbox-escape remote code execution affects Google Chrome on iOS prior to 152.0.7977.82, where improper input validation (CWE-20) in the browser's Transactions Platform component lets a remote attacker potentially run arbitrary code outside the renderer sandbox when a victim loads a crafted HTML page. Google shipped a fix in the stable channel and Chromium rated the underlying issue Medium severity, though the supplied CVSS vector scores it 9.6. There is no public exploit identified and CISA's SSVC framework records exploitation status as none.
Arbitrary code execution in OpenAI Codex CLI (Windows, macOS, Linux) and Codex Desktop (Windows, macOS) allows an attacker who can deliver a crafted repository archive to run code with the victim user's full privileges when Codex automatically collects Git repository metadata. The root cause is that Codex's Git metadata collection path did not suppress the repository-local core.fsmonitor configuration, enabling a malicious .git/config to direct Git to invoke an attacker-supplied filesystem-monitor helper outside Codex's command sandbox and without any user-approval prompt. OpenAI has issued a source-level fix via PR #22652 adding -c core.fsmonitor=false to the relevant Git invocations; no public exploit code has been identified at time of analysis.
Arbitrary code execution in OpenAI Codex Desktop (Windows and macOS, including the Microsoft Store package) occurs when a user opens a workspace containing an attacker-prepared Git repository whose local .git/config is intact. Because Codex automatically inspects Git metadata and working-tree status on open, a malicious attr.tree setting combined with a clean/process filter causes Git to launch an attacker-controlled program outside Codex's command sandbox, with the signed-in user's privileges and no trust prompt, approval, or model interaction. No public exploit is identified at time of analysis and EPSS is low (0.14%), but the outcome is full local compromise of the user's files and credentials.
OpenAI Codex CLI and Codex Desktop's PowerShell command-safety parser failed to recognize PowerShell's stop-parsing token (--%), misclassifying file-writing Git commands embedded after that token as safe and executing them without user approval. An attacker who tricks a developer into opening a crafted repository can cause Codex to silently write an attacker-controlled configuration; when Codex subsequently loads that configuration, it launches an attacker-designated MCP server and executes arbitrary code under the user's account. No public exploit has been identified at time of analysis (EPSS 0.16%, 6th percentile), and the default filesystem sandbox on macOS and Linux can limit the damage radius by preventing writes outside permitted directories.
Arbitrary code execution in OpenAI Codex Desktop for Windows and macOS allows an attacker's Git hooks to run outside the application's command sandbox when a user opens a specially prepared repository. Codex's automated Git operations honored the repository-local `core.hooksPath` setting in `.git/config` without sanitizing or overriding it, enabling a malicious hook script to execute with the user's full OS privileges - reading, modifying, or deleting files and accessing other resources. No active exploitation has been identified (EPSS 0.13%, not in CISA KEV); a code-level fix exists in GitHub PR #22843 but a versioned patch release is not independently confirmed at time of analysis.
OS command injection in the Digitální a informační agentura (DIA) eObčanka-Identifikace macOS client (the Czech national electronic-ID 'eOP' identification app) lets a remote attacker execute arbitrary shell commands by luring a victim to open a crafted czeeopauth:// URL. Versions prior to 3.6.0 pass incoming URL-scheme parameters into a compiled AppleScript wrapper via string concatenation without sanitization, so attacker-controlled input breaks out of the intended command. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV, but the CVSS 9.3 rating reflects unauthenticated network-reachable code execution requiring only that the user follow a malicious link.
Out-of-bounds read in Exiv2's CrwMap::decodeBasic() function affects versions prior to 0.28.9, impacting applications that use the library to parse Canon CRW image metadata. Classified as low severity by the Exiv2 maintainers, this flaw has only been reproduced using a dedicated fuzz target - the standard exiv2 command-line tool cannot trigger it under normal operation. No public exploit exists and no active exploitation has been identified, making real-world impact minimal despite the memory safety class of defect.
Out-of-bounds write in Exiv2's RemoteIo::Impl::populateBlocks() affects all versions prior to 0.28.9, exploitable only when Exiv2 is invoked with a remote URL as input rather than a local file path. Memory corruption from the write could theoretically enable code execution in the Exiv2 process context if a user or automated pipeline fetches a specially crafted image from an attacker-controlled server. Fixed in the 0.28.9 release; no public exploit or KEV listing identified at time of analysis.
Path traversal in Pake before 3.13.1 allows a malicious or compromised web page loaded inside any Pake-generated desktop app to write attacker-fetched content to arbitrary user-writable filesystem locations, including persistence directories. The `download_file` Tauri command accepted a JavaScript-supplied filename and joined it directly to the Downloads directory without stripping path separators or sanitizing sequences such as `../`, enabling writes to locations such as `~/Library/LaunchAgents/` on macOS, `~/.config/autostart/` on Linux, or the Windows Startup folder. Because the HTTP fetch is performed by the Rust backend rather than the sandboxed browser renderer, browser-level download restrictions do not apply. No public exploit is identified at time of analysis, though the attack primitive is straightforward given JFrog's public disclosure.
Authentication bypass in the Omnivore API (packages/api) before commit abf53d6 lets a remote unauthenticated attacker impersonate any Apple-linked account through a JWT algorithm-confusion flaw in Apple sign-in. Because decodeAppleToken trusted the attacker-controlled 'alg' header and jsonwebtoken v8 does not enforce key/algorithm compatibility, an attacker can switch the token to HS256 and sign it with Apple's public RSA key used as the HMAC secret. Reported by VulnCheck; no public exploit identified at time of analysis, though the technique is a well-documented class of attack.
Remote code execution in Time4Popcorn - a Popcorn Time media-streaming fork - affects the Windows client (<= 6.2.1.18), macOS client (<= 6.2.1.17), and Android client (<= 3.5.0.173) through the application's auto-update mechanism (updater.exe on Windows, the PT.updd component on macOS). Because the updater fetches and executes update payloads without verifying their integrity (CWE-494), an attacker able to influence the update channel can deliver and run arbitrary code on the victim host. No CISA KEV listing, no public exploit is identified at time of analysis, and EPSS is low at 0.26% (18th percentile).
Path traversal in IzPack's UnpackerBase.unpack() enables arbitrary file writes under victim privileges when a user executes a trojanized installer JAR. The unpacking pipeline calls IoHelper.translatePath(), which performs only file-separator substitution with no canonical-path check, no startsWith(installDir) containment guard, and no normalization of '../' sequences, allowing attacker-controlled PackFile entries to escape the install directory entirely. Because IzPack JARs are standard unsigned ZIPs with no integrity protection, any legitimate IzPack installer can be silently repackaged with malicious entries; a publicly available proof-of-concept confirms the escape. The CVE is not listed in CISA KEV, but the trivial repacking method and social-engineering distribution vector make this a credible supply-chain threat to organizations consuming IzPack-packaged software from untrusted sources.
Rsbuild versions before 2.0.9 contain a command injection flaw in the developer-server browser-launcher on macOS. The openBrowser() helper in packages/core/src/server/open.ts passes a URL through encodeURI() and then interpolates it into a string handed to child_process.exec(), and because encodeURI() leaves characters such as $, (, ), and ; untouched, a crafted URL is evaluated by /bin/sh and can execute arbitrary operating-system commands with the privileges of the developer running the dev server. The issue was fixed in the 2.0.9 release (upstream PR 7789), so a vendor-released patch is available; no CISA KEV listing or public exploit code was present in the supplied intelligence, and the attack requires local conditions on the developer machine.
MCPVault, a lightweight Model Context Protocol server that exposes Obsidian vault files to AI agents, fails to block access to restricted directories such as .git, .obsidian, and node_modules in versions prior to 0.11.4. PathFilter compiles its deny-list patterns case-sensitively and matches raw path segments, so on case-insensitive macOS and Windows filesystems variants like .Git/config or .GIT/config (and on Windows, trailing-dot/space forms such as .git./config) pass both isAllowed() and isAllowedForListing() while the operating system still opens the real restricted directory. An attacker who can influence a path selected by an AI agent can then read, write, move, search, or list sensitive repository and Obsidian metadata; no public exploit code or CISA KEV entry was identified at time of analysis.
Sandbox escape in Docker Sandboxes on macOS (0.28.0 through 0.41.x) lets a workload running inside a sandbox break out of its shared workspace and read or modify arbitrary files on the host as the VMM user, with host code execution possible where the reachable files are executable or otherwise privileged. The virtio-fs host server follows symlinks when reopening an unlinked file from a stored path, so a guest that replaces a parent directory of a workspace file with a symlink can redirect host-side file operations outside the workspace bind mount. Exploitation requires the attacker to already control a guest workload (for example an untrusted agent or repository), is macOS-specific, and depends on winning a directory-swap timing race; SSVC records Exploitation: none, and no public exploit code was identified at time of analysis. The raw 9.4 CVSS 4.0 score should be read alongside these preconditions rather than at face value - this is a genuine sandbox escape leading to host compromise, but it is not remotely reachable and is bounded by the privileges of the VMM user rather than root.
Apple iOS 18.7.10 and iPadOS 18.7.10 ship a fix for an input-validation flaw (CWE-20) that lets a remote attacker crash or otherwise deny service on unpatched devices, with Apple rating the impact as a full availability loss (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/A:H). Every iPhone or iPad still running a version below 18.7.10 is potentially affected. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so this is currently a patch-promptly issue rather than an emergency.
Local applications on macOS versions prior to 27 can escalate to root privileges because the operating system fails to properly validate entitlements before granting privileged operations (CWE-280). An attacker who can get a user to launch — or who can otherwise run — a crafted app on the target Mac gains full root-level control of the system, with high impact to confidentiality, integrity, and availability. The flaw is fixed in macOS Golden Gate 27 per Apple's advisory; no CISA KEV listing, no public exploit code, and no EPSS score were provided at time of analysis, so this is currently a patching-hygiene issue rather than a confirmed active threat.
A logic flaw in Apple macOS Sequoia, Tahoe, and Golden Gate allows an application running on the target Mac to force unexpected system termination, producing a denial-of-service condition that can crash the host and force a reboot. The flaw is fixed in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27 per Apple's advisories, and no public exploit code has been identified at time of analysis. EPSS is very low (0.17%, 6th percentile) and the issue is not listed in CISA KEV, so near-term mass exploitation is unlikely.
Kernel-level use-after-free in Apple's built-in NFS client allows memory corruption when a device connects to an attacker-operated NFS server, affecting iOS/iPadOS, macOS, tvOS, visionOS and watchOS. Exploitation requires the victim to mount or connect to a malicious NFS share (UI:R) but no credentials or privileges on the target device, making this a remote, unauthenticated-against-the-client attack that terminates in kernel memory corruption with high confidentiality, integrity and availability impact. No public exploit code and no CISA KEV listing were identified at time of analysis; EPSS is low at 0.18% (8th percentile), and CISA SSVC rates exploitation as none and automatable as no, though technical impact is total. Apple has released fixes 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.
Out-of-bounds write in Apple's file-parsing code affects iOS/iPadOS 27 and earlier, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, tvOS 27, visionOS 27, and watchOS 27, allowing a maliciously crafted file to corrupt memory when processed. Apple addressed the flaw with improved bounds checking across all listed platforms, and CVSS 3.1 scores it 7.8 (AV:L/AC:L/PR:L/UI:N) with high confidentiality, integrity, and availability impact, even though the advisory text itself describes only unexpected app termination. No publicly available exploit code and no CISA KEV listing were identified at time of analysis, and EPSS is 0.18% (7th percentile), indicating low near-term exploitation likelihood.
Local privilege escalation in Apple macOS Sequoia (before 15.7.8) and macOS Tahoe (before 26.6) lets a malicious application already running as a normal user obtain root privileges. Apple addressed the flaw by adding restriction checks in its permission-handling code, disclosing it only as 'a permissions issue'; fixed versions are macOS Sequoia 15.7.8 and macOS Tahoe 26.6. There is no CISA KEV listing and no public exploit code identified at time of analysis, and CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', so this is a patching-during-normal-maintenance item rather than an emergency remote threat.
Out-of-bounds memory access in the macOS SMB client kernel component allows a malicious or compromised SMB server to corrupt kernel memory when a victim connects to it, resulting in unexpected system termination or potentially kernel-level code execution. All macOS releases prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27 are affected. Apple has released fixed versions (support.apple.com advisories 149035, 149042, 149043); no public exploit code has been identified and EPSS is low at 0.17% (6th percentile), though the flaw is unauthenticated from the network perspective and requires only that the victim initiate an SMB connection.
Improper state management in Apple's operating systems (iOS/iPadOS, tvOS, visionOS, watchOS) allows a locally installed app to read a persistent account identifier that should have remained isolated, resulting in information disclosure. Affected platforms are all versions prior to the 27 release train on each OS. Vendor patches are available (iOS 27, iPadOS 27, tvOS 27, visionOS 27, watchOS 27), no public exploit code has been identified at time of analysis, and EPSS is very low (0.15%, 5th percentile). The supplied CVSS vector (AV:N/PR:N) does not match the description's local-app precondition, so treat the 7.5 score with caution.
Sandbox escape in Apple macOS lets a malicious or compromised application already running inside the macOS App Sandbox break out of that confinement and operate with privileges beyond what its sandbox profile permits (CVSS 3.1 base 8.4, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N). Affected systems are macOS releases prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27; exploitation requires the attacker to already have local code execution as a sandboxed app (for example, one the user installed and launched), and provides no remote initial access, functioning as a boundary-crossing primitive once code is running on the host. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; EPSS is 0.19% (9th percentile), so real-world activity appears limited, though the sandbox-boundary impact keeps this a serious local isolation flaw rather than a theoretical one.
An out-of-bounds write (CWE-787) in the Apple frameworks that parse 3D model files lets a maliciously crafted model corrupt memory when it is opened on an affected device, potentially giving the attacker code execution in the context of the processing application. The flaw affects iOS/iPadOS before 26.7 and 27, macOS Sequoia before 15.8, macOS Tahoe before 26.7, macOS Golden Gate 27, tvOS before 27, visionOS before 27 and watchOS before 27, and Apple has shipped fixes for all of them. Exploitation likelihood is low: EPSS is 0.17% (7th percentile), CISA SSVC records exploitation as 'none' and the vulnerability is not in KEV — no public exploit code has been identified, and the local attack vector with required user interaction makes mass exploitation unlikely.
Race condition in Apple's kernel state management lets a malicious sandboxed app escape its sandbox and execute arbitrary code with kernel privileges on iOS, iPadOS, macOS, tvOS, visionOS and watchOS. Exploitation requires a timing window to be won (CVSS AC:H) but no user interaction beyond launching the app, and success yields full control of the affected device. Apple shipped fixes in iOS/iPadOS 26.7 and 27, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, tvOS 27, visionOS 27 and watchOS 27; no public exploit code or CISA KEV listing was present in the provided data, and no EPSS
Improper state management in Apple iOS, iPadOS, and watchOS allows an installed app to track a user across other apps and websites without the user's permission, effectively defeating the platform's cross-app tracking consent controls. The flaw affects iOS/iPadOS releases before 26.7 and before 27, plus watchOS before 27, and is remediated by the iOS 26.7/iPadOS 26.7, iOS 27/iPadOS 27, and watchOS 27 updates. Exploitation requires a hostile app on the device rather than remote network access; EPSS is 0.15% (5th percentile), there is no CISA KEV listing or public exploit identified, and SSVC rates exploitation as 'none' with partial technical impact.
Improper handling of persistent identifiers in Apple's mobile and desktop operating systems allows an app installed on the device to recognize the same user across app reinstalls, defeating the identifier-reset behavior that users and administrators rely on for privacy. Apple states the issue is fixed in iOS 27 and iPadOS 27, macOS Golden Gate 27, and visionOS 27, and the affected CPE set covers all earlier releases of iOS/iPadOS, macOS, and visionOS. No public exploit code or CISA KEV entry has been reported at time of analysis, and EPSS is only 0.16% (6th percentile), so this is a privacy-integrity hardening fix rather than an emergency remote-code-execution patch.
Kernel memory corruption in Apple macOS can be triggered when a user mounts a maliciously crafted disk image, causing unexpected system termination or corruption of kernel memory. Apple addressed the CWE-120 buffer overflow with improved bounds checking in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. No public exploit code and no active exploitation have been identified, and the EPSS score is low (0.21%, 12th percentile), so practical exposure is dominated by local file-delivery scenarios rather than remote mass exploitation.
Sandboxed applications on Apple macOS can break out of their App Sandbox because of a logic error in the sandbox's validation checks, and Apple has fixed the issue in macOS 27 "Golden Gate". Any Mac running a macOS release earlier than 27 is affected, and successful exploitation gives a malicious app access to files, services, and resources it should never have been able to reach, matching the integrity-only impact (C:N/I:H) in the published vector. No public exploit code and no CISA KEV entry were identified at the time of analysis, and the EPSS score of 0.15% (5th percentile) suggests the flaw is not currently being exploited at scale.
Kernel-level out-of-bounds write (CWE-787) in the macOS SMB client stack allows a malicious SMB server to corrupt kernel memory when a target Mac connects to it, potentially yielding kernel code execution or a system crash. All macOS branches are affected: Sequoia before 15.8, Tahoe before 26.7, and macOS Golden Gate versions before 27. Apple has released patches for all three branches; there is no public exploit code identified, no CISA KEV listing, and EPSS is low (0.17%, 6th percentile), so exploitation is currently assessed as targeted/manual rather than widespread.
Local privilege escalation in Apple macOS lets a low-privileged local process obtain root via improper path validation (CWE-22), affecting macOS versions prior to Sequoia 15.8, Tahoe 26.7 and Golden Gate 27. Apple addressed the flaw with improved path validation, and the CVSS 7.8 vector (AV:L/AC:L/PR:L/UI:N, total CIA impact) reflects a reliable but non-automatable local escalation requiring an existing code-execution foothold. There is no CISA KEV listing and no public exploit identified at time of analysis; exploitation status is 'none' per CISA SSVC and the issue is not considered automatable.
A local sandbox-escape flaw in Apple macOS (CWE-284, improper access control via faulty state management) allows a malicious application to break out of its App Sandbox and operate outside the restricted environment it was granted. Affected versions are macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27, with Apple shipping fixes in all three (support.apple.com advisories 149035, 149042, 149043). CVSS 3.1 rates it 8.2 (AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N), but EPSS is only 0.19% (9th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis — so this is a high-severity, low-current-activity issue whose priority is driven by the App Sandbox being a core macOS security boundary rather than by observed exploitation.
Apple iOS and iPadOS before version 27 leak cross-application information through the handling of user preferences, allowing a locally installed app to enumerate which other apps are present on the device. Apple addressed the privacy flaw in iOS 27 and iPadOS 27; EPSS is only 0.17% (7th percentile), there is no CISA KEV listing, and no public exploit code identified at time of analysis. The practical impact is user profiling and device fingerprinting rather than code execution or data theft.
A race condition in Apple macOS (fixed in macOS Tahoe 26.6) allows a locally executed malicious application to escalate privileges and gain root on the host. The flaw is reachable by a low-privileged local process without user interaction beyond running the app, and it has a 7.8 CVSS base score reflecting total loss of confidentiality, integrity and availability for the vulnerable component. There is no CISA KEV listing, no vendor confirmation of in-the-wild exploitation, and no public exploit code identified at time of analysis; CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', indicating a targeted rather than wormable threat.
An out-of-bounds read in Apple's kernel (CWE-125) lets an app already running on the device read past the end of a kernel buffer, potentially leaking kernel memory or crashing the system. Affected platforms span iOS/iPadOS before 26.6.1, macOS Sequoia before 15.8, macOS Tahoe before 26.6.2, and tvOS, visionOS and watchOS before 27, with a CVSS 3.1 base of 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H). There is no CISA KEV listing and no public exploit identified at time of analysis; EPSS is 0.20% (10th percentile), so this is a local, app-mediated kernel hardening issue rather than a remotely exploitable emergency.
Resource exhaustion in Apple macOS allows a remote, unauthenticated attacker to deny service to legitimate users by feeding input that the operating system fails to bound correctly. Apple fixed the flaw with improved input validation in macOS Tahoe 26.7, macOS Sequoia 15.8, and macOS Golden Gate 27. It is rated 7.5 with an availability-only impact (CWE-400), and while no public exploit code or observed exploitation has been identified, the attack is network-reachable and fully automatable per CISA's SSVC assessment.
Race condition in Apple's kernel allows a local user on iOS 27, iPadOS 27, macOS Golden Gate 27, tvOS 27, visionOS 27 and watchOS 27 to cause unexpected system termination or read kernel memory. Apple fixed the flaw with additional validation, publishing advisories 149034-149038; there is no public exploit code and no confirmed active exploitation (EPSS 0.16%, SSVC exploitation: none).
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.
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.
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.
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.
Integer overflow in the macOS kernel NFS client can be triggered when an unpatched Mac connects to or mounts a share from a malicious or spoofed NFS server, leading to kernel memory corruption or unexpected system termination. Affected systems are macOS releases below Sequoia 15.8, Tahoe 26.7, and Golden Gate 27 (CPE cpe:2.3:a:apple:macos). The flaw is availability-only (CVSS 3.1 base 7.5; our assessment AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H), requires no credentials on the target but does require the victim to initiate an NFS client session, and is best exploited by an attacker positioned to serve or impersonate an NFS endpoint the victim reaches; no public exploit code has been identified at time of analysis, EPSS is low at 0.17% (6th percentile), and the issue is not in CISA KEV. Apple has released fixes, so patching removes the exposure entirely.
An out-of-bounds write in Apple macOS lets a malicious or compromised app running as a normal, unprivileged user corrupt memory and escalate to root privileges on the affected system. The flaw is fixed in macOS Golden Gate 27, macOS Tahoe 26.7, and macOS Sequoia 15.8; all earlier releases of those branches remain exposed (CWE-787, CVSS 7.8, AV:L/PR:L/UI:N). No public exploit code has been identified at time of analysis, and CISA's SSVC assessment rates exploitation as 'none' and non-automatable, so practical risk is currently confined to local post-compromise privilege escalation rather than mass remote attacks.
Local privilege escalation in Apple macOS allows a malicious or compromised application already running on the system to obtain root privileges. The flaw is a permissions-handling defect (CWE-280) that Apple addressed by adding additional restrictions, with fixes shipping in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. Exploitation requires local code execution as a normal user (AV:L, PR:L) and, per CISA SSVC, is not automatable with no known exploitation activity; no public exploit code or EPSS signal was provided at time of analysis.
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.
A use-after-free in Apple macOS kernel memory management allows a locally installed and executed app to escalate to kernel privileges and run arbitrary code with full system control. Affected releases are macOS before Sequoia 15.8, before Tahoe 26.7, and before Golden Gate 27; Apple shipped fixes in all three branches. The flaw is a local privilege escalation (CVSS 7.8, AV:L/PR:L) rather than a remote code execution bug, and there is no public exploit code or CISA KEV listing identified at time of analysis, so real-world exploitation currently depends on an attacker first getting a malicious app onto the target Mac.
Memory corruption in Apple's image-handling code across iOS 27, iPadOS 27, macOS Golden Gate 27 and visionOS 27 allows an attacker to achieve arbitrary code execution when a user processes a maliciously crafted image. Apple removed the vulnerable code entirely in the 27-generation releases, which are the only versions containing the fix; all earlier supported builds remain affected. The flaw is rated 7.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H), meaning exploitation needs local positioning plus some user interaction, and there is no public exploit code or CISA KEV entry identified at time of analysis.
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.
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.
Memory corruption in Apple macOS WebDAV client handling allows code execution when a user connects to an attacker-controlled WebDAV server, affecting macOS versions prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27. The flaw is an out-of-bounds write (CWE-787) reachable over the network but gated by user interaction, rated 8.8 by Apple/NVD with an unauthenticated network attack vector. Apple has released fixes in three OS updates, and exploitation is not confirmed — no public exploit code and no CISA KEV listing — while EPSS sits at 0.18% (8th percentile), indicating low predicted mass-exploitation activity; this reads as a credible but targeted risk rather than a wormable event.
Apple macOS contains a local privilege-escalation flaw in which an application running under an ordinary user account can abuse insufficient access-control checks to obtain root privileges. Devices are affected if they run macOS versions below Sequoia 15.8, Tahoe 26.7 or Golden Gate 27, and Apple has shipped fixes for all three release lines. CVSS 3.1 scores this 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and CISA's SSVC rates technical impact as total, but there is no CISA KEV listing, no reported exploitation and no public exploit code identified at time of analysis, so this is best treated as a high-value post-compromise escalation primitive rather than an imminent remote threat.
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.
Opening a maliciously crafted file on an unpatched Apple device can crash the component that parses it, because a buffer overflow in Apple's size-validation logic was only corrected in the latest OS releases. Affected platforms are iOS/iPadOS before 26.7 (and before 27), macOS Sequoia before 15.8, macOS Tahoe before 26.7, macOS Golden Gate before 27, tvOS before 27, and visionOS before 27; exploitation is local and requires the victim to actively open the attacker-supplied file, with no remote or network trigger available. The demonstrated outcome per Apple's advisory is unexpected process termination (denial of service) rather than code execution or data disclosure, and no public exploit code or confirmed active exploitation was identified at time of analysis, with EPSS at 0.22% (13th percentile).
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.
Path traversal in Apple iOS and iPadOS lets an attacker who physically holds a trust-paired iPhone or iPad read and write files outside the intended directory, a high-confidentiality and high-integrity impact on the device's file store. Everything running earlier than iOS/iPadOS 26.7 or iOS/iPadOS 27 is affected, and the vendor-released fixes are iOS 26.7, iPadOS 26.7, iOS 27 and iPadOS 27 (Apple advisories 149034 and 149041). Exploitation hinges on prior physical possession and an already-accepted 'Trust This Computer' relationship, so the published 7.5 score (CVSS:3.1/AV:N/PR:N) is inflated relative to the required prerequisites - the same vector's PR:N confirms no additional authentication is needed once the pairing exists - and exploitation risk is further limited by a low EPSS of 0.15 percent (5th percentile) with no public exploit identified at time of analysis.
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.
A use-after-free flaw in Apple's kernel affects iOS and iPadOS before 26.7, macOS Sequoia before 15.8, and macOS Golden Gate before 27, allowing a locally running app to corrupt kernel memory or cause unexpected system termination. The issue is a local, low-privilege memory-safety defect (CWE-416) rated CVSS 7.8, and Apple has shipped fixes in iOS 26.7, iPadOS 26.7, macOS Golden Gate 27 and macOS Sequoia 15.8. There is no indication of active exploitation (no CISA KEV listing) and no public exploit code identified, with EPSS at 0.19% (9th percentile) suggesting low near-term exploitation likelihood at scale.
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.
A remote input-validation weakness in Apple macOS allows crafted data to terminate an application unexpectedly or, more seriously, achieve arbitrary code execution on the host. Apple has fixed the flaw in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27, and only those or later builds are protected. Exploitation requires the victim to interact with the malicious content (CVSS UI:R, PR:N), there is no public exploit code identified at time of analysis, and neither CISA KEV nor the SSVC decision framework indicates observed exploitation, so this is best treated as a patch-now hygiene issue rather than an emergency.
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.
Unexpected system termination is possible on unpatched Apple macOS hosts because of an out-of-bounds read that a remote attacker can trigger without authentication or user interaction. Apple addressed the flaw with improved bounds checking in macOS Tahoe 26.7, macOS Sequoia 15.8, and macOS Golden Gate 27, but the affected system component is not named in the public advisories. No public exploit code has been identified and CISA's SSVC assessment records exploitation as 'none' while flagging the issue as automatable with partial technical impact; the CVSS 7.5 score is driven entirely by availability loss, with no confidentiality or integrity impact.
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.
Parsing a maliciously crafted file on an unpatched Mac can crash the affected application or leak contents of process memory, caused by an out-of-bounds read (CWE-125) in Apple's file-handling code. Apple has fixed the flaw in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27, with advisories published at support.apple.com. There is no public exploit code identified at time of analysis and no CISA KEV listing, and the EPSS probability is low at 0.19% (9th percentile), so this rates as a patch-on-schedule issue rather than an emergency.
An out-of-bounds write in Apple's WebKit engine — reachable by processing maliciously crafted web content — can corrupt memory and potentially lead to arbitrary code execution on affected Apple platforms. The flaw stems from an integer-overflow class defect (CWE-190) where a size calculation overflows and the subsequent bounds check fails, allowing an OOB write. It is fixed in Safari 26.6.1, iOS/iPadOS 26.6.1, macOS Tahoe 26.6.2, tvOS 27, visionOS 27 and watchOS 27; exploitation requires the victim to load attacker-controlled web content (UI:R), and no public exploit or active exploitation has been identified at time of analysis, with EPSS at just 0.17% (6th percentile).
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.
Missing entitlement checks in Apple's iOS and iPadOS, tvOS, watchOS, and visionOS (all versions before the 27 release train) allow a locally installed app to read device attributes it is not authorized to access and combine them into a persistent fingerprint of the user. Only devices running an affected platform with an attacker-supplied app already installed are exposed; the independent assessment re-scores the issue as local-access with confidentiality-only impact (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), which is materially lower than the supplied CVSS 3.1 vector (AV:N, 7.5) that treats the flaw as remotely reachable. There is no indication of active exploitation, KEV status is not set, and no public exploit code has been identified at time of analysis; EPSS is 0.19% (9th percentile), consistent with a low near-term exploit probability. Apple has released fixes in iOS 27, iPadOS 27, tvOS 27, visionOS 27, and watchOS 27.
Memory corruption in Apple Safari and the shared WebKit engine used across iOS, iPadOS, macOS Tahoe, tvOS, visionOS and watchOS can be triggered when a victim views maliciously crafted web content, rooted in an integer overflow (CWE-190) that was corrected through improved input validation. The CVSS 3.1 vector (8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates an unauthenticated network-delivered attack that requires user interaction but yields high confidentiality, integrity and availability impact, consistent with out-of-bounds memory effects rather than a confirmed code-execution chain. No public exploit code has been identified at time of analysis and CISA KEV does not list this CVE, while the EPSS score of 0.17% (6th percentile) signals a real but low-priority, non-urgent risk that is best addressed through routine patching. Patches are available from the vendor in Safari 26.6.1, iOS 26.6.1 and iPadOS 26.6.1, macOS Tahoe 26.6.2, tvOS 27, visionOS 27 and watchOS 27.
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.
User fingerprinting on Apple iOS and iPadOS devices running versions earlier than 26.6 allows an installed application to identify and track the device owner through sensitive data that Apple has now relocated as part of version 26.6. Per the authoritative assessment, this is an on-device, local-execution privacy flaw (CWE-359) with no additional privileges or user interaction required beyond the app running, and its impact is limited to tracking/fingerprinting rather than data theft, code execution, or system compromise; the supplied AV:N/high-confidentiality vector is not borne out by analysis. Exploitation requires getting a malicious or privacy-abusing app onto the device via the App Store, sideloading, MDM/enterprise provisioning, or TestFlight, and devices already updated to iOS/iPadOS 26.6 are not affected. There is no public exploit identified at time of analysis, no CISA KEV listing, and EPSS is low at 0.14% (4th percentile).
A local privilege-escalation flaw in Apple's operating system family lets a malicious app already running on the device obtain root privileges by exploiting a missing authorization check. Apple addressed the issue with 'additional restrictions' in iOS 26.7 and iPadOS 26.7, iOS 27 and iPadOS 27, macOS Golden Gate 27, and visionOS 27, and the CVSS 3.1 score is 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is not confirmed: the issue is not in CISA KEV, no public exploit code is identified, and CISA's SSVC assessment lists exploitation as 'none' and automatable as 'no', though technical impact is rated 'total' once root is achieved.
Memory corruption in Apple's 3D model parsing pipeline allows a local attacker with low privileges to trigger a classic buffer overflow (CWE-120) on iOS/iPadOS, macOS, tvOS, visionOS and watchOS when a victim opens a maliciously crafted 3D model file. Apple addressed the flaw with improved memory handling in iOS 26.7/27, iPadOS 26.7/27, macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7, tvOS 27, visionOS 27 and watchOS 27. Exploitation requires local access and user interaction, no public exploit code has been identified at time of analysis, and the EPSS score is very low at 0.17% (7th percentile), so this is a credible patching priority for Apple fleets rather than a mass-exploitation emergency.
Privilege escalation to root in Parallels Desktop for Mac via argument injection into a tar command executed by the root-owned dispatcher service. Any local user - no admin rights required - can connect to the world-writable `/var/run/prl_disp_service.socket`, authenticate via `PrlSrv_LoginLocal` without signature verification, and then pass a crafted appliance path through `PrlSrv_InstallAppliance` that embeds a quote character to escape the Qt `QProcess::splitCommand` argument boundary, injecting `--use-compress-program=<binary>` into macOS tar and running arbitrary code as root. No public exploit has been identified at time of analysis, but the exploitation path requires no special conditions beyond a local user account.
Out-of-bounds read and write in the Linux kernel's forcedeth NVIDIA ethernet driver triggers on every S3 suspend/resume cycle due to an off-by-one loop terminator in nv_suspend() and nv_resume(). The loop runs one iteration past the end of the saved_config_space[] array, overwriting adjacent kernel memory (np->name_rx[]) and issuing a stray MMIO write one dword beyond the ioremap'd hardware window; with CONFIG_UBSAN_TRAP=y the kernel aborts during the suspend path. The bug has existed since Linux 2.6.27 but was only surfaced by UBSAN on Apple Macmini3,1 (MCP79) hardware during S3 cycling. No public exploit has been identified at time of analysis.
Remote unauthenticated denial-of-service in AirSane scanner server (versions prior to 0.4.12) allows an attacker to crash the daemon by sending an HTTP POST request with an arbitrarily large Content-Length value, triggering memory exhaustion and a std::bad_alloc exception. The root cause is in httpserver.cpp, where the Content-Length header value is passed directly to std::string::resize() with no upper-bound validation. A secondary variant using non-numeric Content-Length values produces undefined behavior via NaN-to-integer conversion. No public exploit or active exploitation has been identified at time of analysis.
Stack-based buffer overflow in Tesseract OCR 5.5.3 and earlier corrupts the stack during legacy engine initialization, enabling denial of service and potential control-flow hijacking when a crafted `.traineddata` file is processed. The flaw originates in `Classify::ReadNormProtos` (normmatch.cpp), where unbounded `std::istream::operator>>(char*)` extraction into a fixed 61-byte stack buffer allows a 99-character NORMPROTO token to overwrite up to 39 bytes beyond the buffer boundary during `TessBaseAPI::Init`. No fixed release is available at time of analysis; an upstream fix commit exists but has not been tagged as a release, and no public exploit has been identified at time of analysis.
Buffer overflow in the Apple Notification Center Service (ANCS) event handler of the Pavlok Behavioral Conditioning Wearable allows unauthenticated adjacent-network attackers to achieve full compromise of the wearable device and potentially the paired Apple host. The vulnerability resides in firmware versions up to build 20260707 and is exploitable by any attacker within Bluetooth Low Energy range without credentials. A proof-of-concept has been published (CVSS 4.0 E:P); the vendor did not respond to coordinated disclosure, and no patch has been released.
Remote code execution in Google Chrome on iOS before 153.0.8010.36 stems from a use-after-free in the Sharing component (CWE-416), letting a remote attacker who lures a victim to crafted network content execute arbitrary code outside the browser sandbox. Google has shipped a patched Chrome build; no public exploit is identified at time of analysis, and Google/Chromium rated the underlying bug 'Medium' severity even though the assigned CVSS base score is 9.6.
Local privilege escalation in Waves Central for macOS (versions up to 16.6.2) allows any authenticated local user to gain root code execution by abusing a flawed XPC client authorization scheme in the product's privileged helper service. The helper validates connecting XPC clients by performing a certificate-chain equality comparison against itself rather than enforcing a pinned code requirement (application identifier and Apple Team ID), meaning any process carrying the Waves signing certificate can impersonate a legitimate client and instruct the helper to run arbitrary scripts as root. No public exploit has been identified at time of analysis; a vendor-released fix is available in version 17.0.
Privilege escalation and local code execution affect the OpenTelemetry.Resources.Host NuGet package (opentelemetry-dotnet-contrib) on macOS prior to version 1.16.0-beta.2. The host.id resource attribute detector invokes sh and ioreg using bare names resolved through the PATH environment variable rather than absolute paths, allowing a local attacker with fewer privileges than the host application to substitute malicious binaries and execute arbitrary code in the application's security context. No public exploit has been identified at time of analysis; Linux and Windows hosts are explicitly unaffected.
Sandbox-escape remote code execution affects Google Chrome on iOS prior to 152.0.7977.82, where improper input validation (CWE-20) in the browser's Transactions Platform component lets a remote attacker potentially run arbitrary code outside the renderer sandbox when a victim loads a crafted HTML page. Google shipped a fix in the stable channel and Chromium rated the underlying issue Medium severity, though the supplied CVSS vector scores it 9.6. There is no public exploit identified and CISA's SSVC framework records exploitation status as none.
Arbitrary code execution in OpenAI Codex CLI (Windows, macOS, Linux) and Codex Desktop (Windows, macOS) allows an attacker who can deliver a crafted repository archive to run code with the victim user's full privileges when Codex automatically collects Git repository metadata. The root cause is that Codex's Git metadata collection path did not suppress the repository-local core.fsmonitor configuration, enabling a malicious .git/config to direct Git to invoke an attacker-supplied filesystem-monitor helper outside Codex's command sandbox and without any user-approval prompt. OpenAI has issued a source-level fix via PR #22652 adding -c core.fsmonitor=false to the relevant Git invocations; no public exploit code has been identified at time of analysis.
Arbitrary code execution in OpenAI Codex Desktop (Windows and macOS, including the Microsoft Store package) occurs when a user opens a workspace containing an attacker-prepared Git repository whose local .git/config is intact. Because Codex automatically inspects Git metadata and working-tree status on open, a malicious attr.tree setting combined with a clean/process filter causes Git to launch an attacker-controlled program outside Codex's command sandbox, with the signed-in user's privileges and no trust prompt, approval, or model interaction. No public exploit is identified at time of analysis and EPSS is low (0.14%), but the outcome is full local compromise of the user's files and credentials.
OpenAI Codex CLI and Codex Desktop's PowerShell command-safety parser failed to recognize PowerShell's stop-parsing token (--%), misclassifying file-writing Git commands embedded after that token as safe and executing them without user approval. An attacker who tricks a developer into opening a crafted repository can cause Codex to silently write an attacker-controlled configuration; when Codex subsequently loads that configuration, it launches an attacker-designated MCP server and executes arbitrary code under the user's account. No public exploit has been identified at time of analysis (EPSS 0.16%, 6th percentile), and the default filesystem sandbox on macOS and Linux can limit the damage radius by preventing writes outside permitted directories.
Arbitrary code execution in OpenAI Codex Desktop for Windows and macOS allows an attacker's Git hooks to run outside the application's command sandbox when a user opens a specially prepared repository. Codex's automated Git operations honored the repository-local `core.hooksPath` setting in `.git/config` without sanitizing or overriding it, enabling a malicious hook script to execute with the user's full OS privileges - reading, modifying, or deleting files and accessing other resources. No active exploitation has been identified (EPSS 0.13%, not in CISA KEV); a code-level fix exists in GitHub PR #22843 but a versioned patch release is not independently confirmed at time of analysis.
OS command injection in the Digitální a informační agentura (DIA) eObčanka-Identifikace macOS client (the Czech national electronic-ID 'eOP' identification app) lets a remote attacker execute arbitrary shell commands by luring a victim to open a crafted czeeopauth:// URL. Versions prior to 3.6.0 pass incoming URL-scheme parameters into a compiled AppleScript wrapper via string concatenation without sanitization, so attacker-controlled input breaks out of the intended command. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV, but the CVSS 9.3 rating reflects unauthenticated network-reachable code execution requiring only that the user follow a malicious link.
Out-of-bounds read in Exiv2's CrwMap::decodeBasic() function affects versions prior to 0.28.9, impacting applications that use the library to parse Canon CRW image metadata. Classified as low severity by the Exiv2 maintainers, this flaw has only been reproduced using a dedicated fuzz target - the standard exiv2 command-line tool cannot trigger it under normal operation. No public exploit exists and no active exploitation has been identified, making real-world impact minimal despite the memory safety class of defect.
Out-of-bounds write in Exiv2's RemoteIo::Impl::populateBlocks() affects all versions prior to 0.28.9, exploitable only when Exiv2 is invoked with a remote URL as input rather than a local file path. Memory corruption from the write could theoretically enable code execution in the Exiv2 process context if a user or automated pipeline fetches a specially crafted image from an attacker-controlled server. Fixed in the 0.28.9 release; no public exploit or KEV listing identified at time of analysis.
Path traversal in Pake before 3.13.1 allows a malicious or compromised web page loaded inside any Pake-generated desktop app to write attacker-fetched content to arbitrary user-writable filesystem locations, including persistence directories. The `download_file` Tauri command accepted a JavaScript-supplied filename and joined it directly to the Downloads directory without stripping path separators or sanitizing sequences such as `../`, enabling writes to locations such as `~/Library/LaunchAgents/` on macOS, `~/.config/autostart/` on Linux, or the Windows Startup folder. Because the HTTP fetch is performed by the Rust backend rather than the sandboxed browser renderer, browser-level download restrictions do not apply. No public exploit is identified at time of analysis, though the attack primitive is straightforward given JFrog's public disclosure.
Authentication bypass in the Omnivore API (packages/api) before commit abf53d6 lets a remote unauthenticated attacker impersonate any Apple-linked account through a JWT algorithm-confusion flaw in Apple sign-in. Because decodeAppleToken trusted the attacker-controlled 'alg' header and jsonwebtoken v8 does not enforce key/algorithm compatibility, an attacker can switch the token to HS256 and sign it with Apple's public RSA key used as the HMAC secret. Reported by VulnCheck; no public exploit identified at time of analysis, though the technique is a well-documented class of attack.
Remote code execution in Time4Popcorn - a Popcorn Time media-streaming fork - affects the Windows client (<= 6.2.1.18), macOS client (<= 6.2.1.17), and Android client (<= 3.5.0.173) through the application's auto-update mechanism (updater.exe on Windows, the PT.updd component on macOS). Because the updater fetches and executes update payloads without verifying their integrity (CWE-494), an attacker able to influence the update channel can deliver and run arbitrary code on the victim host. No CISA KEV listing, no public exploit is identified at time of analysis, and EPSS is low at 0.26% (18th percentile).
Path traversal in IzPack's UnpackerBase.unpack() enables arbitrary file writes under victim privileges when a user executes a trojanized installer JAR. The unpacking pipeline calls IoHelper.translatePath(), which performs only file-separator substitution with no canonical-path check, no startsWith(installDir) containment guard, and no normalization of '../' sequences, allowing attacker-controlled PackFile entries to escape the install directory entirely. Because IzPack JARs are standard unsigned ZIPs with no integrity protection, any legitimate IzPack installer can be silently repackaged with malicious entries; a publicly available proof-of-concept confirms the escape. The CVE is not listed in CISA KEV, but the trivial repacking method and social-engineering distribution vector make this a credible supply-chain threat to organizations consuming IzPack-packaged software from untrusted sources.