CVE-2026-39118
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA local privilege escalation vulnerability exists in Kandji Agent before v4.7.5(5374) due to a client-side validation gap that allows local attackers to invoke restricted agent functionality that should be limited to privileged users or processes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Kandji Agent is installedCheck for the Kandji Agent process or installation on the system. On macOS, this may involve checking /Applications, system processes, or LaunchDaemons related to Kandji.Affected if Kandji Agent is found running on the system
-
Determine the installed Kandji Agent versionRetrieve the version number of the installed Kandji Agent. This is typically available via the agent's info pane, system report, or by querying the agent directly if a command-line interface exists.Affected if The version cannot be determined or is below 4.7.5(5374)
-
Compare version against the affected rangeCompare the installed version to the affected range: any version before 4.7.5(5374) is vulnerable.Affected if The installed version is earlier than 4.7.5(5374)
-
Confirm the agent is running with elevated privilegesVerify that the Kandji Agent is running as a privileged user or as a system-level service, as the vulnerability allows unprivileged local users to invoke restricted functionality.Affected if The agent runs with elevated privileges and the version is before 4.7.5(5374)
The environment is affected if Kandji Agent is installed with a version earlier than 4.7.5(5374), allowing local unprivileged users to potentially invoke restricted privileged agent functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Kandji Agent to version 4.7.5(5374) or later to remediate the client validation gap. As this is a local attack requiring existing local access, prioritize patching of managed endpoints.
Kandji Agent v.4.7.5(5374) or later
- 1. Identify the currently installed Kandji Agent version on affected systems
- 2. If the installed version is before v.4.7.5(5374), download the latest Kandji Agent version from the official Iru/Kandji vendor portal
- 3. Test the upgrade in a non-production environment to verify compatibility
- 4. Deploy the upgrade to production systems following standard change management procedures
- 5. Verify the upgrade was successful by confirming the installed version is v.4.7.5(5374) or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39118 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data