CVE-2026-47133 clearancekit vulnerability
ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to version 5.0.10, each table in the on-disk SQLite policy store (`/Library/Application Support/clearancekit/store.db`) is verified using an ECDSA signature stored in the `data_signatures` table. The signed payload contains only the canonical row content, with no version counter or freshness binding. An attacker who can write `store.db` and the matching `data_signatures` row — feasible during the opfilter-update window when the Endpoint Security filter is offline, or via offline-boot / decrypted-backup scenarios — can substitute a previously-captured legitimately-signed snapshot. opfilter accepts the older snapshot as fully valid on next boot because the existing signatures still verify. Version 5.0.10 patches the issue.
Browse Authentication Bypass security risksQuick answer
craigjbass clearancekit should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- < 5.0.10
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-47133 affects clearancekit and involves cryptographic validation failure. An attacker with the required local access may reuse or forge trusted policy data and weaken enforcement. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Upgrade ClearanceKit to 5.0.10 or later and rebuild the policy database from a trusted current source.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses clearancekit.
- Compare the installed version with the recorded affected range: < 5.0.10.
- Upgrade ClearanceKit to 5.0.10 or later and rebuild the policy database from a trusted current source.
- Until patched, reduce public exposure, disable the affected workflow where practical, and allow access only from trusted users and systems.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to clearancekit; remove access that is not required.
- Review application, system, proxy, and audit logs for requests and behavior linked to the affected feature and CVE.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-47133 in place.
- Use a safe regression test to confirm the affected cryptographic validation failure path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-47133?
craigjbass clearancekit versions listed as affected should be reviewed: < 5.0.10.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.