# CVE-2026-47134: Security feature bypass in clearancekit

> Local root processes can forge signed policies in ClearanceKit due to missing keychain ACLs, bypassing file-system access controls.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-w254-hxm5-3hgh

## What is CVE-2026-47134?

CVE-2026-47134 is a medium-severity vulnerability in craigjbass clearancekit, published on 20 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2026-47134?


## How do I fix CVE-2026-47134?

No fix has been published for CVE-2026-47134 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47134 being exploited?

There is no known exploitation of CVE-2026-47134 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47134 and fix it if it is affected.

What it is: CVE-2026-47134 is a medium-severity vulnerability in craigjbass clearancekit, published on 20 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47134 in the wild and no public exploit code.

Affected product: craigjbass clearancekit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47134/ (Markdown: https://insights.sbomify.com/CVE-2026-47134/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47134
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47134
- OSV: https://osv.dev/vulnerability/CVE-2026-47134

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47134/
Summaries are generated and may contain mistakes; the official description above is the record.