Quick answers
- Is CVE-2026-47134 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47134 being exploited in the wild.
- How severe is CVE-2026-47134?
- 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-47134?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47134 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-47134?
- 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 versions prior to 5.0.10 suffer from an incorrect permission assignment (CWE-732) regarding its ECDSA private key stored in the macOS System Keychain. The vulnerability stems from using a two-step creation pattern (SecKeyCreateRandomKey followed by SecItemAdd) where the Access Control List (ACL) attribute (kSecAttrAccess) is silently ignored by the legacy System Keychain for EC keys. Consequently, the key inherits no ACL restrictions, allowing any process with root privileges to access the key and sign arbitrary policy databases. An attacker with local root access can exploit this to inject whitelist rules or disable security features. The issue is resolved in version 5.0.10 by using a single-step creation and persistence call that correctly binds the ACL.
Affected products
- craigjbass ClearanceKit < 5.0.10
Timeline
- 2026-05-17: advisory: GitHub advisory published
- 2026-07-20: disclosed: NVD publication date