CVE-2026-47133: ClearanceKit policy replay vulnerability in SQLite store

CVE-2026-47133 · Severity: info · CVSS 6.9 · Published 2026-07-20

ClearanceKit is a security tool for macOS that manages file access permissions for different applications. A vulnerability in how it stores its security rules allows an attacker with administrative access to replace current security settings with older, less restrictive versions. This could allow an attacker to bypass newer security protections or re-enable features that were previously disabled by the administrator.

Technologies: Craigjbass ClearanceKit. Vendors: Craigjbass.

Quick answers

Is CVE-2026-47133 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47133 being exploited in the wild.
How severe is CVE-2026-47133?
Informational severity, with a CVSS score of 6.9, published 20 July 2026.
Which products and versions are affected?
Craigjbass ClearanceKit < 5.0.10.
Is there a fix for CVE-2026-47133?
A patch was published on 2026-07-20: Version 5.0.10 released to address the issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47133 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-47133?
Check whether you run Craigjbass ClearanceKit at an affected version. 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 (prior to version 5.0.10) uses an SQLite database to store per-process access policies, with integrity verified via ECDSA signatures in a 'data_signatures' table. However, the signed payload lacks a monotonic counter or timestamp (freshness binding). An attacker with local root privileges can exploit windows where the Endpoint Security filter is offline (such as during updates or via offline boot) to replace the current 'store.db' with a previously captured, legitimately-signed version. The system accepts the older snapshot as valid because the signatures remain cryptographically correct. This allows for the persistence of outdated or less-restrictive security policies. The issue is resolved in version 5.0.10 by introducing an 'epoch ratchet' stored in the System Keychain.

Affected products

  • craigjbass ClearanceKit < 5.0.10

Timeline

  • 2026-05-17: advisory: Vendor advisory published on GitHub
  • 2026-07-20: disclosed: CVE published to NVD
  • 2026-07-20: patched: Version 5.0.10 released to address the issue

References

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