Skip to main content

ClearanceKit CVE-2026-40604

| EUVDEUVD-2026-24213 HIGH
Protection Mechanism Failure (CWE-693)
2026-04-21 security-advisories@github.com
8.2
CVSS 4.0 · Vendor: github
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Achieve root access via separate exploit
  2. Delivery
    Identify opfilter extension process
  3. Exploit
    Send SIGSTOP to suspend extension
  4. Execution
    AUTH events timeout and default to allow
  5. Persist
    Access protected files bypassing ClearanceKit policies
  6. Impact
    Complete objective with disabled controls

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
Exploitation Conditions

Exploitation requires the attacker to have already achieved root (UID 0) privileges on the target macOS system where ClearanceKit opfilter extension is running. The attacker must be able to send signals (SIGSTOP, SIGKILL, or SIGTERM) to the opfilter process, which requires root authority. ClearanceKit must be actively installed and configured to enforce file-access policies - if ClearanceKit is not deployed or is already disabled, there is no security control to bypass. The vulnerability affects default configurations of ClearanceKit prior to version 5.0.6 and does not require any specific ClearanceKit policy configuration or non-standard macOS settings. Limiting factors: macOS System Integrity Protection (SIP) does not prevent root from signaling user-space Endpoint Security extensions. The prerequisite root access means this is effectively a post-exploitation technique rather than an initial compromise vector, which significantly reduces the pool of real-world attack scenarios where this vulnerability would be the critical link in an attack chain.

Impact

This vulnerability presents a paradoxical risk profile requiring careful assessment. The CVSS base score of 8.2 is elevated due to the scope change and complete bypass of ClearanceKit's security controls. However, exploitation requires pre-existing root access (PR:H), which already represents full system compromise on most macOS configurations. The critical question for defenders is: does ClearanceKit provide defense-in-depth against a root-compromised system, or protect against privilege escalation pathways? If ClearanceKit is deployed to enforce mandatory access controls that should survive even root compromise (defense against malicious root processes, separation of administrative duties, or compliance requirements), this is a critical bypass. If ClearanceKit primarily protects against pre-root threats, the practical risk is lower since the attacker already has effective control. The local-only attack vector (AV:L) and high privilege requirement (PR:H) significantly limit exposure compared to network-accessible vulnerabilities. No EPSS, KEV, or POC data is available, suggesting no widespread exploitation. SSVC assessment: exploitation is straightforward for a skilled attacker with root access (low complexity), technical impact is high (complete security control bypass), but automatable exploitation across diverse environments is limited by the prerequisite root access. Priority depends entirely on your threat model for root-level compromise - organizations using ClearanceKit as a control against malicious insiders with administrative access should treat this as high priority; others may defer to normal patching cycles.

Exploit ScenarioDerived

An attacker who has achieved root access on a macOS system protected by ClearanceKit (through separate vulnerability exploitation, stolen credentials, or malicious insider activity) executes 'kill -STOP $(pgrep -f uk.craigbass.clearancekit.opfilter)' to suspend the ClearanceKit Endpoint Security extension. With the extension suspended, all file-access authorization events time out and default to allow. The attacker now accesses sensitive files or modifies protected system components that ClearanceKit policies would normally block, completely bypassing the intended access restrictions while leaving minimal forensic evidence since the bypass occurs silently through legitimate signal mechanisms. The attacker can resume the extension later with SIGCONT to restore normal operation and avoid detection.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 21, 2026

Local privilege escalation in ClearanceKit opfilter system extension allows root-level processes on macOS to completely bypass file-access policy enforcement by suspending or killing the Endpoint Security extension. An attacker with root access can send SIGSTOP to the uk.craigbass.clearancekit.opfilter extension, causing all AUTH events to time out and silently default to allow, effectively disabling all ClearanceKit file-access controls. This represents a critical security control bypass for environments relying on ClearanceKit for file-system access restrictions. Fixed in version 5.0.6. No public exploit identified at time of analysis, though exploitation is straightforward for any attacker who has already achieved root access on the macOS system.

RemediationAI

Upgrade ClearanceKit to version 5.0.6 or later, which implements proper protection against signal-based attacks on the opfilter system extension. The update can be obtained from the vendor's GitHub repository referenced in the security advisory at https://github.com/craigjbass/clearancekit/security/advisories/GHSA-5r9w-9fg6-266q. For environments unable to immediately upgrade, implement compensating controls by restricting which processes can run with root privileges through mandatory access controls external to ClearanceKit (such as TCC restrictions or third-party privilege management solutions), though this has limited effectiveness since the vulnerability itself requires root access. Monitor system logs for unexpected termination or suspension of the opfilter extension process (look for SIGSTOP/SIGKILL/SIGTERM events against processes with bundle ID uk.craigbass.clearancekit.opfilter), which may indicate exploitation attempts, though legitimate administrative actions could also trigger these signals. Note that there is no effective workaround that preserves both ClearanceKit functionality and prevents this bypass - the only complete remediation is upgrading to the patched version.

Affected VersionsENISA

clearancekit < 5.0.6

Affected Packages

euvd clearancekit fix: 5.0.6

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 implements a macOS Endpoint Security system extension (bundle ID uk.craigbass.clearancekit.opfilter) that intercepts file-system access events and enforces per-process access policies. The vulnerability stems from insufficient protection against signal-based process control (CWE-693: Protection Mechanism Failure). macOS Endpoint Security extensions handle authorization events synchronously - when the extension is suspended via SIGSTOP or terminated with SIGKILL/SIGTERM, pending AUTH events time out. The macOS Endpoint Security framework defaults to 'allow' on timeout to prevent system deadlock, creating a fail-open condition. This design means that any process running with root privileges can effectively disable the security extension by suspending its execution, causing all file-access policy checks to silently pass. The CVSS 4.0 vector indicates local attack (AV:L), low complexity (AC:L), high privileges required (PR:H), but critically high impact on subsequent system confidentiality and integrity (SC:H/SI:H), reflecting the scope change from compromising the extension to bypassing system-wide access controls.

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

Vendor (github) PRIMARY 8.2 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:H/SI:H/SA:N

Primary rating from Vendor (github) · only source for this CVE.

CVSS VectorVendor: github

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
None

Lifecycle Timeline

3
Patch released
Apr 24, 2026 - 20:49 nvd
Patch available
Patch available
Apr 21, 2026 - 19:01 EUVD
CVE Published
Apr 21, 2026 - 18:16 nvd
HIGH 8.2

DescriptionCVE.org

ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to 5.0.6, the opfilter Endpoint Security system extension (bundle ID uk.craigbass.clearancekit.opfilter) can be suspended with SIGSTOP or kill -STOP, or killed with SIGKILL/SIGTERM, by any process running as root. While the extension is suspended, all AUTH Endpoint Security events time out and default to allow, silently disabling ClearanceKit's file-access policy enforcement for the duration of the suspension. This vulnerability is fixed in 5.0.6.

Executive ViewAI

Why It Matters

CVE-2026-40604 is a local privilege escalation in ClearanceKit's macOS endpoint security extension that allows root-level attackers to completely bypass file-access policy enforcement by disabling the security extension. Organizations relying on ClearanceKit for file-system access controls face a critical control gap: any attacker with root access can suspend the protection mechanism, neutralizing organizational data governance and compliance policies. This vulnerability requires immediate attention for environments using ClearanceKit as a primary file-access control.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict root access through enhanced privilege access management and multi-factor authentication; (2) Deploy additional macOS security monitoring to detect SIGSTOP signals sent to endpoint security extensions; (3) Consider temporarily reducing reliance on ClearanceKit for critical file-access restrictions until version 5.0.6+ is deployed; (4) Implement host-based intrusion detection to identify root-level process manipulation; (5) Evaluate alternative file-access control mechanisms for high-risk data until patched.

Threat Intelligence Overview

EPSS Score
0.0%
Top 96% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Very High
Technical Impact
Partial

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy