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

CVE-2026-24071 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:H/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-24071?

Native Access users are exposed to a privilege escalation vulnerability that allows attackers to bypass security controls through PID reuse attacks, potentially gaining unauthorized access to…

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

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

How to fix or mitigate CVE-2026-24071?

Within 24 hours: Inventory all systems running Native Access and assess business criticality. Within 7 days: Implement network segmentation to restrict XPC service access and disable Native Access on non-essential systems; establish monitoring for suspicious process behavior. Within 30 days: Monitor vendor for patch availability and develop a rapid deployment plan; consider alternative solutions if patch timeline extends beyond 60 days.

Native Access CVE-2026-24071

HIGH

Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)

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

Information Disclosure Native Access

7.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

AV:L/AC:H/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

High

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 22:01 vuln.today

PoC Detected

Feb 11, 2026 - 20:39 vuln.today

Public exploit code

CVE Published

Feb 02, 2026 - 14:16 nvd

HIGH 7.8

DescriptionCVE.org

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.

AnalysisAI

Native Access's privileged XPC helper uses PID-based code signature verification, which is vulnerable to PID reuse attacks allowing local attackers with low privileges to bypass security checks and gain elevated access. Public exploit code exists for this vulnerability, and no patch is currently available. An attacker can leverage this flaw to achieve arbitrary code execution with the privileges of the helper process.

Technical ContextAI

Affects Native Access. 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.