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

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

Which versions of Kandji Agent are affected by CVE-2026-39118?

Kandji Agent versions prior to 4.7.5(5374) contain a local privilege escalation vulnerability enabling device users to escalate permissions and compromise endpoint security, including data…

How to fix or mitigate CVE-2026-39118?

24 hours: Inventory all deployed Kandji Agent versions and identify systems running versions prior to 4.7.5(5374); implement enhanced monitoring for local privilege escalation attempts on managed endpoints. 7 days: Validate Kandji Agent 4.7.5(5374) in pilot environment and finalize staged deployment schedule. 30 days: Complete deployment of Kandji Agent 4.7.5(5374) or later across all managed endpoints.

Kandji Agent CVE-2026-39118

EUVD-2026-36761 HIGH

Improper Privilege Management (CWE-269)

2026-06-15 mitre

GHSA-3wx9-p98r-g7qr

Privilege Escalation N A

8.4

CVSS 3.1 · Vendor: mitre

Severity by source

Vendor (mitre) PRIMARY

8.4 HIGH

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

vuln.today AI

7.8 HIGH

Local privilege escalation requires an existing logged-in/unprivileged process on the managed Mac, so PR:L (not PR:N); low complexity yields full C/I/A impact in the agent's root context.

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

4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 16, 2026 - 19:23 vuln.today

CVSS changed

Jun 16, 2026 - 19:22 NVD

8.4 (HIGH)

CVE Published

Jun 15, 2026 - 00:00 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

An issue in Iru, Inc Kandji Agent before v.4.7.5(5374) allows a local attacker to escalate privileges via a client validation gap to invoke restricted agent functionality.

AnalysisAI

Local privilege escalation in Iru, Inc Kandji Agent versions prior to 4.7.5(5374) allows a local attacker to invoke restricted agent functionality by exploiting a client-side validation gap. The flaw maps to CWE-269 (Improper Privilege Management) and carries a CVSS 8.4 rating due to high impact on confidentiality, integrity, and availability, though no public exploit identified at time of analysis and EPSS is low at 0.14%.

Technical ContextAI

Kandji Agent is the macOS endpoint client component of the Kandji device-management platform, running with elevated privileges to enforce policies, install software, and manage configurations on managed Apple devices. The root cause is CWE-269 (Improper Privilege Management): the agent relies on client-side validation to gate access to privileged internal functions, meaning a local actor on the endpoint can bypass these checks and invoke restricted agent operations that should be reserved for the trusted management plane. CPE data is unhelpful here (listed as 'n/a:n/a'), but the vendor URL identifies the affected component unambiguously as the Kandji macOS agent prior to build 4.7.5(5374).

RemediationAI

Vendor-released patch: Kandji Agent 4.7.5(5374) - upgrade all managed endpoints to this build or later as documented at https://www.iru.com/updates/2026/03/agent-4-7-5-5374, with cross-reference at https://nvd.nist.gov/vuln/detail/CVE-2026-39118. Because Kandji centrally pushes agent updates, administrators should confirm the rollout has reached 100% of the managed fleet and audit endpoints that may have missed the update window (offline laptops, suspended devices). As a compensating control until patching completes, restrict interactive local access to managed Macs (limit secondary user accounts, enforce screen-lock and FileVault, and tighten remote-shell access such as SSH and ARD) so that an attacker cannot run code locally to trigger the flaw; the trade-off is reduced helpdesk flexibility, not a true mitigation of the vulnerability itself.