It was found that the XPC service offered by the privileged helper of Native Access uses the PID of the connecting client to verify its code signature. This is considered insecure and can be exploited by PID reuse attacks. The connection handler function uses _xpc_connection_get_pid(arg2) as argument for the hasValidSignature function. This value can not be trusted since it is vulnerable to PID reuse attacks.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
The vendor was unreachable and did not respond to multiple contact attempts. No patch is available. Customers should contact the vendor and request a patch.
Workaround
No workaround given by the vendor.
References
History
Mon, 02 Feb 2026 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | It was found that the XPC service offered by the privileged helper of Native Access uses the PID of the connecting client to verify its code signature. This is considered insecure and can be exploited by PID reuse attacks. The connection handler function uses _xpc_connection_get_pid(arg2) as argument for the hasValidSignature function. This value can not be trusted since it is vulnerable to PID reuse attacks. | |
| Title | XPC Client Validation via PID leading to Local Privilege Escalation in Native Instruments Native Access | |
| Weaknesses | CWE-367 | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: SEC-VLab
Published:
Updated: 2026-02-02T13:23:51.846Z
Reserved: 2026-01-21T11:29:19.854Z
Link: CVE-2026-24071
No data.
Status : Received
Published: 2026-02-02T14:16:35.753
Modified: 2026-02-02T14:16:35.753
Link: CVE-2026-24071
No data.
OpenCVE Enrichment
No data.
Weaknesses