CVE-2026-34218: craigjbass ClearanceKit improper privilege management in opfilter

CVE-2026-34218 · Severity: medium · CVSS 5.5 · Published 2026-03-31

ClearanceKit, a security tool for macOS that manages file-access permissions, contains a flaw where it fails to apply security policies during system startup. Until a user manually interacts with the application's interface, the software only protects its own internal files, leaving other sensitive data unprotected. This could allow unauthorized programs or users to access, modify, or steal protected files that should have been restricted by corporate or user-defined rules.

Technologies: Craigjbass ClearanceKit. Vendors: Craigjbass.

Quick answers

Is CVE-2026-34218 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-34218 being exploited in the wild.
How severe is CVE-2026-34218?
Medium severity, with a CVSS score of 5.5, published 31 March 2026.
Which products and versions are affected?
craigjbass ClearanceKit < 4.2.14.
Is there a fix for CVE-2026-34218?
A patch was published on 2026-03-31: Fixes committed in version 4.2.14 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34218 attacked?
It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-34218?
Check whether you run Craigjbass ClearanceKit. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

ClearanceKit (opfilter) contains two startup defects that result in a failure to load the full policy set into the FilterInteractor. First, the initialization calls for applying policies (applyPolicyToFilter, applyAllowlistToFilter, and applyJailRulesToFilter) occurred before the Endpoint Security (ES) client was started; because these functions guard on a nil client, they returned early without updating the interactor. Second, the system failed to issue es_clear_cache after startup, allowing the kernel to serve potentially stale authorization decisions. Consequently, only the hardcoded baseline rule was enforced, while MDM-delivered and user-defined rules remained inactive until an XPC-triggered policy mutation occurred. This allows local processes to bypass intended file-access restrictions and jail constraints. The issue is fixed in version 4.2.14 by reordering startup calls and ensuring cache clears.

Affected products

  • craigjbass ClearanceKit < 4.2.14

Timeline

  • 2026-03-26: advisory: GitHub Security Advisory published
  • 2026-03-31: disclosed: CVE published to NVD
  • 2026-03-31: patched: Fixes committed in version 4.2.14

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.