craigjbass clearancekit up to 4.1 Opfilter Endpoint authorization

Summaryinfo

A vulnerability was found in craigjbass clearancekit up to 4.1. It has been rated as problematic. This issue affects some unknown processing of the component Opfilter Endpoint. This manipulation causes authorization. This vulnerability is handled as CVE-2026-33631. It is possible to launch the attack on the local host. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in craigjbass clearancekit up to 4.1 and classified as problematic. Affected by this vulnerability is an unknown function of the component Opfilter Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. In versions on the 4.1 branch and earlier, the opfilter Endpoint Security system extension enforced file access policy exclusively by intercepting ES_EVENT_TYPE_AUTH_OPEN events. Seven additional file operation event types were not intercepted, allowing any locally running process to bypass the configured FAA policy without triggering a denial. Commit a3d1733 adds subscriptions for all seven event types and routes them through the existing FAA policy evaluator. AUTH_RENAME and AUTH_UNLINK additionally preserve XProtect change detection: events on the XProtect path are allowed and trigger the existing onXProtectChanged callback rather than being evaluated against user policy. All versions on the 4.2 branch contain the fix. No known workarounds are available.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-33631 since 03/23/2026. The exploitation appears to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 4.2 eliminates this vulnerability. Applying the patch a3d1733d2691a0d40209c48b01bf9291bf645207 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• craigjbass

Name

• clearancekit

Version

• 4.0
• 4.1

License

• open-source

Website

• Product: https://github.com/craigjbass/clearancekit/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion