{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24071 exists.","fix":"No fix has been published for CVE-2026-24071 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24071 is a high-severity vulnerability in Native Access, published on 2 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24071 and fix it if it is affected.\n\nWhat it is: CVE-2026-24071 is a high-severity vulnerability in Native Access, published on 2 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24071 exists.\n\nAffected product: Native Access. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24071/ (Markdown: https://insights.sbomify.com/CVE-2026-24071/index.md)","id":"CVE-2026-24071","markdown":"https://insights.sbomify.com/CVE-2026-24071/index.md","name":"CVE-2026-24071","record":{"aliases":["GHSA-xp6c-hp7c-5vjx"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Native Access application","requires_auth":"low_privilege","summary":"A race condition in Native Access allows local attackers to escalate privileges by exploiting PID reuse in XPC client validation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SEC-VLab","cpe":[{"product":"native_access","vendor":"native-instruments"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"XPC Client Validation via PID leading to Local Privilege Escalation in Native Instruments Native Access","id":"CVE-2026-24071","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Apache HTTP Server: mod_rewrite elevation of privileges via ap_expr","id":"CVE-2026-24072"},"packages":[],"prev":{"headline":"Local Privilege Escalation via DYLIB Injection in Native Instruments Native Access","id":"CVE-2026-24070"},"products":["Native Access"],"published":"2026-02-02","related":[{"cvss_score":8.8,"headline":"Local Privilege Escalation via DYLIB Injection in Native Instruments Native Access","id":"CVE-2026-24070","kev_date_added":null,"published":"2026-02-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-03","vendors":["Native Instruments"]},"summary":"A race condition in Native Access allows local attackers to escalate privileges by exploiting PID reuse in XPC client validation.","url":"https://insights.sbomify.com/CVE-2026-24071/"}