CVE-2026-40599: ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies

Q: How do I fix CVE-2026-40599?

clearancekit: upgrade to 5.0.5. Exact commands for each OS are on this page.

Q: Is CVE-2026-40599 being exploited?

CVE-2026-40599 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-40599 affect?

CVE-2026-40599 affects clearancekit. Severity is high (CVSS 7.1). ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to 5.0.5, ClearanceKit incorrectly treats a process with an empty Team ID and a non-empty Signing ID as an Apple platform binary. Thi

Q: How urgent is CVE-2026-40599?

Priority 31/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2026-40599 is a high-severity flaw (CVSS 7.1) affecting clearancekit. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to 5.0.5, ClearanceKit incorrectly treats a process with an empty Team ID and a non-empty Signing ID as an Apple platform binary. This bug allows a malicious software to impersonate an apple process in the global allowlist, and access all protected files. This vulnerability is fixed in 5.0.5.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 97%)
CISA exploited list	No
Weakness	CWE-863
Published	2026-04-21
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: craigjbass

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-21 18:16 UTCPublished CVE record published
2026-10-26 21:10 UTCUpdated Record last modified

craigjbass clearancekit UPGRADE

Affected: < 5.0.5

Fixed in: 5.0.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy clearancekit || rpm -q clearancekit || clearancekit --version

2. UPGRADE to 5.0.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade clearancekit

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade clearancekit

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-40599?

clearancekit: upgrade to 5.0.5. Exact commands for each OS are on this page.

Is CVE-2026-40599 being exploited?

CVE-2026-40599 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-40599 affect?

CVE-2026-40599 affects clearancekit. Severity is high (CVSS 7.1). ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to 5.0.5, ClearanceKit incorrectly treats a process with an empty Team ID and a non-empty Signing ID as an Apple platform binary. Thi

How urgent is CVE-2026-40599?

Priority 31/100. High severity; Public exploit reference

Software pages

macOS vulnerabilities

Related CVEs

CVE-2026-40604 MEDIUM 4.4 UPGRADE ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies

References

← Back to latest CVEs