What is the CVSS score of CVE-2026-24070?

CVE-2026-24070 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Native Access are affected by CVE-2026-24070?

Native Access installations contain a privileged helper component vulnerable to unauthorized XPC-based command execution, potentially allowing attackers to execute arbitrary file operations with…

Is there a public PoC exploit available for CVE-2026-24070?

Yes, a public proof-of-concept exploit is available for CVE-2026-24070. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-24070?

Within 24 hours: Inventory all systems with Native Access installed and isolate high-risk machines from production networks if possible; notify affected users to avoid using the application pending remediation. Within 7 days: Contact Native Instruments for patch availability timeline and evaluate whether Native Access can be replaced with alternative solutions; implement network monitoring for suspicious XPC activity. Within 30 days: Deploy vendor patch immediately upon release or execute compensating controls; conduct forensic analysis of systems for evidence of exploitation.

Native Access CVE-2026-24070

HIGH

Untrusted Search Path (CWE-426)

2026-02-02 551230f0-3615-47bd-b7cc-93e92e730bbf

Privilege Escalation Apple Native Access

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Re-analysis Queued

Apr 29, 2026 - 09:22 vuln.today

cvss_changed

Analysis Generated

Mar 12, 2026 - 22:01 vuln.today

PoC Detected

Feb 11, 2026 - 20:40 vuln.today

Public exploit code

CVE Published

Feb 02, 2026 - 14:16 nvd

HIGH 8.8

DescriptionCVE.org

During the installation of the Native Access application, a privileged helper com.native-instruments.NativeAccess.Helper2, which is used by Native Access to trigger functions via XPC communication like copy-file, remove or set-permissions, is deployed as well. The communication with the XPC service of the privileged helper is only allowed if the client process is signed with the corresponding certificate and fulfills the following code signing requirement: "anchor trusted and certificate leaf[subject.CN] = \"Developer ID Application: Native Instruments GmbH (83K5EG6Z9V)\""

The Native Access application was found to be signed with the com.apple.security.cs.allow-dyld-environment-variables and com.apple.security.cs.disable-library-validation entitlements leading to DYLIB injection and therefore command execution in the context of this application. A low privileged user can exploit the DYLIB injection to trigger functions of the privileged helper XPC service resulting in privilege escalation by first deleting the /etc/sudoers file and then copying a malicious version of that file to /etc/sudoers.

AnalysisAI

Native Access on macOS allows local authenticated attackers to inject malicious libraries into the privileged XPC helper process due to overly permissive code signing entitlements, enabling arbitrary code execution with system-level privileges. The vulnerability stems from the application being signed with dyld environment variable and library validation bypass entitlements while communicating with a trusted helper that validates only the signing certificate. Public exploit code exists, and no patch is currently available.

Technical ContextAI

Classified as CWE-426 (Untrusted Search Path). Affects Native Access. During the installation of the Native Access application, a privileged helper com.native-instruments.NativeAccess.Helper2, which is used by Native Access to trigger functions via XPC communication like copy-file, remove or set-permissions, is deployed as well. The communication with the XPC service of the privileged helper is only allowed if the client process is signed with the corresponding certificate and fulfills the following code signing requirement: "anchor trusted and certificate leaf[