CVE-2026-47134 clearancekit vulnerability
ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. The ECDSA private key used to sign the on-disk policy database (`/Library/Application Support/clearancekit/store.db`) is stored in the macOS System Keychain. The key was created via the two-step pattern `SecKeyCreateRandomKey` (in-memory) followed by `SecItemAdd(kSecValueRef:, kSecAttrAccess:)` (persist). Prior to version 5.0.10, for `kSecClassKey` items in the legacy System Keychain, `kSecAttrAccess` passed to `SecItemAdd` is silently ignored — the persisted key inherits no ACL restriction. The same access builder applied to `kSecClassGenericPassword` items correctly binds the ACL, making this bug specific to the EC key. The result is that any process running as root can use the key to produce valid signatures over arbitrary policy content. Version 5.0.10 fixes the issue. No known workarounds are available. Disabling the system extension and manually removing the System Keychain item labelled `clearancekit policy signing key` would prevent the forged-signature path but also disables policy enforcement.
Browse Privilege Escalation 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-47134 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 follow the advisory's key-removal guidance if the old signing key may have been exposed.
- 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 follow the advisory's key-removal guidance if the old signing key may have been exposed.
- 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-47134 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.
CVE-2026-65897 grav vulnerability
Updated July 24, 2026
mediumCVE-2026-65010 datasets vulnerability
Updated July 24, 2026
highWPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 43.2 - Cross-Site Request Forgery to Privilege Escalation via Plugin Settings Update
Updated July 24, 2026
Trusted references
FAQ
What is affected by CVE-2026-47134?
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.