CVE-2026-39118: Kandji Agent Privilege Escalation (CVSS 8.4)

Technical summary

CVE-2026-39118 stems from insufficient client validation logic in Kandji Agent. The vulnerability (CWE-269: Improper Access Control) permits a local attacker to circumvent authorization controls and invoke restricted agent operations. The attack surface is local-only and requires no user interaction; an attacker with shell access to a managed endpoint can exploit the validation gap to escalate privileges and execute agent functionality normally reserved for higher-privilege contexts.

Business impact

Kandji Agent manages macOS and iOS device security and compliance across enterprises. Privilege escalation on managed endpoints can lead to unauthorized access to sensitive data, configuration tampering, and potential lateral movement within a managed infrastructure. Organizations relying on Kandji for endpoint security and mobile device management face increased risk of insider threats and post-compromise lateral movement if endpoints running vulnerable agent versions are not promptly patched.

Affected systems

Kandji Agent versions prior to 4.7.5(5374) are affected. Organizations using Kandji's endpoint management solution should verify installed agent versions across their macOS fleet. The vulnerability affects agents in their default deployment state; no special configuration is required for the vulnerability to exist.

Exploitability

Exploitability is straightforward for any attacker with local access to an affected endpoint. No authentication, special privileges, or user interaction is needed; the validation bypass is client-side and can be triggered programmatically. However, the attack requires pre-existing local access, limiting exposure to scenarios involving rogue employees, compromised accounts, or physical access. This is not a remote code execution vector.

Remediation

Upgrade Kandji Agent to version 4.7.5(5374) or later on all managed endpoints. Verify the upgrade propagates across your fleet through Kandji's management console. No workarounds exist for the underlying validation flaw; patching is the only mitigation.

Patch guidance

Deploy Kandji Agent 4.7.5(5374) or later to all endpoints via your MDM instance. Test the update in a pilot group to confirm no compatibility issues with your environment before enterprise-wide rollout. Verify successful installation and confirm agent version compliance through Kandji's reporting dashboard.

Detection guidance

Monitor Kandji Agent process logs for unexpected invocations of restricted functionality by unprivileged processes. Audit local access logs for shell sessions that interact directly with the Kandji Agent daemon or configuration files. Use Kandji's compliance reporting to identify endpoints still running versions earlier than 4.7.5(5374). Check endpoint security tools for suspicious calls to agent binaries or attempts to load restricted modules.

Why prioritize this

This is a HIGH-severity local privilege escalation affecting an enterprise-critical security management tool. The CVSS score of 8.4 reflects high impact (confidentiality, integrity, and availability) and easy exploitability for local attackers. While not yet trending in known exploit databases, privilege escalation on endpoint management agents directly undermines security posture across your managed fleet. Organizations should prioritize patching within 30 days, with faster deployment for sensitive environments handling regulated data.

Risk score, explained

The CVSS 3.1 score of 8.4 (HIGH) reflects: local attack vector with no authentication requirement (AV:L, PR:N); low complexity (AC:L); no user interaction (UI:N); and complete compromise of confidentiality, integrity, and availability on the affected system (C:H, I:H, A:H). The unscoped impact (S:U) means the attacker gains full privileges within the endpoint context. This positions the vulnerability in the upper tier of local privilege escalations and warrants rapid remediation.

Frequently asked questions