# CVE-2026-47133: ClearanceKit's signed policy tables lack monotonic counter, allowing replay of older legitimately-signed snapshots

> Attackers can bypass file access controls by replaying old signed policy snapshots, requiring local write access to the database.

- **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-9hx3-5wp9-2qqg

## What is CVE-2026-47133?

CVE-2026-47133 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. 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.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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


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

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

## Is CVE-2026-47133 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47133 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-47133 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-47133/ (Markdown: https://insights.sbomify.com/CVE-2026-47133/index.md)
```

## Sources

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

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