Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS 6.3 score reflects a local attack vector (AV:L) with low complexity (AC:L) and no privileges or user interaction required (PR:N, UI:N). The 4.0 vector indicates high scope impact on system integrity (SI:H) and confidentiality (SC:H), but no direct availability impact. The attack is trivial to execute from any local process during the startup window-a persistent threat window rather than a one-shot exploit. However, real-world risk is constrained by temporal factors: the vulnerability only manifests during system boot or service restart, and exploitation requires the attacker to act before the user opens the ClearanceKit GUI. No KEV status is provided, suggesting no confirmed active exploitation in the wild at time of analysis. No public exploit code (POC) is referenced. The high-integrity, system-level nature of the bypass combined with ease of exploitation (local, unauthenticated) elevates this above typical local-only CVEs; systems that depend on ClearanceKit for security policy enforcement face a meaningful integrity risk until patched, though the window is narrow and the prerequisite is local code execution already on the system. |
| Exploit ScenarioDerived | A local attacker with code execution on a macOS system (e.g., via a compromised application or user-level privilege escalation) can exploit the startup window to read, write, or delete files that should be blocked by ClearanceKit's user-defined or MDM-managed policies. For example, an attacker could copy sensitive files from a restricted directory or modify system files during the narrow window after boot but before the user opens the ClearanceKit GUI. The attacker requires only local code execution and no special privileges; the vulnerability is deterministic and does not depend on timing beyond the startup phase, making it a reliable vector for systems reliant on ClearanceKit for file integrity assurance. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 31, 2026
ClearanceKit on macOS fails to enforce managed and user-defined file-access policies during startup, allowing local processes to bypass intended access controls until GUI interaction triggers policy reloading. The vulnerability affects ClearanceKit versions prior to 4.2.14, where two startup defects create a window in which only a hardcoded baseline rule is enforced, leaving the system vulnerable to privilege escalation and unauthorized file access. This issue is not confirmed actively exploited, but the trivial attack vector (local, no authentication) and high integrity/system impact make it a meaningful risk for systems relying on ClearanceKit for file-access enforcement.
RemediationAI
Vendor-released patch: ClearanceKit 4.2.14. Update to version 4.2.14 or later, which fixes the two startup defects and ensures managed and user-defined policies are enforced immediately at boot time without requiring GUI interaction. The fixes are tracked in commits 56d617b778c571e3c29b803636d9807940992daa and ddfdacb2633681bbd9c2f41dbd536ea039386628 in the upstream repository at https://github.com/craigjbass/clearancekit. For systems unable to update immediately, minimize the startup window by logging in and opening the ClearanceKit GUI immediately after boot to trigger policy loading; however, this is a workaround and not a substitute for patching. MDM administrators should prioritize updating ClearanceKit across managed devices to restore intended file-access policy enforcement from boot time.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
ClearanceKit is a macOS kernel extension or system service that implements per-process file-system access policies through an opfilter enforcement mechanism. The vulnerability stems from initialization logic in two distinct startup code paths that fail to load and activate managed (MDM-delivered) policies and user-defined rules at boot time. Instead, only a single compile-time baseline rule is enforced until a user manually interacts with the policy GUI, which triggers a policy mutation event over XPC (inter-process communication). This is rooted in CWE-269 (Improper Control of Resource Identifiers), indicating the system fails to correctly enforce its own intended access control mechanisms. The affected product is identified by CPE cpe:2.3:a:craigjbass:clearancekit:*:*:*:*:*:*:*:* across all versions prior to 4.2.14.
Know when Clearancekit gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to version 4.2.14, two related startup defects created a window during which only the single compile-time baseline rule was enforced by opfilter. All managed (MDM-delivered) and user-defined file-access rules were not applied until the user interacted with policies through the GUI, triggering a policy mutation over XPC. This issue has been patched in version 4.2.14.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Clearancekit
View allClearanceKit 4.1 and earlier for macOS allows local authenticated users to completely bypass configured file access poli
ClearanceKit 5.0.4 and earlier allows local attackers with low-privilege accounts to bypass file-system access controls
Local authenticated attackers can bypass file access policies in ClearanceKit (macOS system extension) versions prior to
Local privilege escalation in ClearanceKit opfilter system extension allows root-level processes on macOS to completely
Policy signing key bypass in ClearanceKit prior to 5.0.10 permits any root process on macOS to forge valid signatures ov
ClearanceKit's on-disk SQLite policy store on macOS is vulnerable to a replay attack that allows a high-privileged local
ClearanceKit for macOS prior to version 5.0.4-beta-1f46165 fails to validate destination paths in dual-path file operati
EUVD-2026-17484
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB