CVE-2026-47133 craigjbass CVE debrief

Who should care

macOS system administrators and security teams using ClearanceKit should assess exposure and apply the patch to version 5.0.10 or later. This vulnerability requires local access to the system and the ability to write to specific files, making it a concern for those managing macOS systems with ClearanceKit installed.

Why it matters

CVE-2026-47133 is a medium-severity vulnerability in ClearanceKit that allows an attacker with local access to bypass security mechanisms by substituting a previously captured, legitimately signed snapshot of the on-disk SQLite policy store. This could lead to unauthorized changes to system policies. The vulnerability is addressed in ClearanceKit version 5.0.10. macOS system administrators and security teams should verify and apply the patch, review system logs, and implement additional monitoring for Endpoint Security filter events.

• An attacker with local access can bypass security mechanisms
• Potential for unauthorized changes to system policies
• Requires verification of ClearanceKit version and patch application
• Monitoring of Endpoint Security filter events may be necessary

Technical summary

ClearanceKit, a security component on macOS, stores its on-disk SQLite policy store in `/Library/Application Support/clearancekit/store.db`. Prior to version 5.0.10, the ECDSA signature verification process for this store only checks the canonical row content, lacking a version counter or freshness binding. This allows an attacker with write access to `store.db` and the corresponding `data_signatures` row to substitute a previously captured, legitimately signed snapshot. The attacker can exploit this during the opfilter-update window when the Endpoint Security filter is offline or through offline-boot/decrypted-backup scenarios. On the next boot, opfilter will accept the older snapshot as valid since the existing signatures still verify.

Defensive priority

macOS systems using ClearanceKit prior to version 5.0.10 should verify and apply the patch

Recommended defensive actions

• Verify ClearanceKit version and apply patch to version 5.0.10 or later
• Review system logs for potential exploitation attempts
• Implement additional monitoring for Endpoint Security filter events
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in ClearanceKit, including the lack of version counter or freshness binding in the signed payload, allowing an attacker to substitute a previously-captured legitimately-signed snapshot.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.