{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40604 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40604 is a high-severity vulnerability in craigjbass clearancekit, published on 21 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40604 and fix it if it is affected.\n\nWhat it is: CVE-2026-40604 is a high-severity vulnerability in craigjbass clearancekit, published on 21 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-40604 in the wild and no public exploit code.\n\nAffected product: craigjbass clearancekit. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-40604/ (Markdown: https://insights.sbomify.com/CVE-2026-40604/index.md)","id":"CVE-2026-40604","markdown":"https://insights.sbomify.com/CVE-2026-40604/index.md","name":"CVE-2026-40604","record":{"aliases":["GHSA-5r9w-9fg6-266q"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"macOS security extension","requires_auth":"high_privilege","summary":"A root process can suspend the ClearanceKit macOS extension, causing file-access policies to fail open and allowing unauthorized file access.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"clearancekit","vendor":"craigjbass"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to 5.0.6, the opfilter Endpoint Security system extension (bundle ID uk.craigbass.clearancekit.opfilter) can be suspended with SIGSTOP or kill -STOP, or killed with SIGKILL/SIGTERM, by any process running as root. While the extension is suspended, all AUTH Endpoint Security events time out and default to allow, silently disabling ClearanceKit's file-access policy enforcement for the duration of the suspension. This vulnerability is fixed in 5.0.6.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in clearancekit","id":"CVE-2026-40604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Tautulli Vulnerable to Authenticated Path Traversal in Cache Deletion API","id":"CVE-2026-40605"},"packages":[],"prev":{"headline":"Chartbrew: Incorrect Access Control in /api/project/dashboard/:brewName via same-team override","id":"CVE-2026-40603"},"products":["clearancekit"],"published":"2026-04-21","related":[{"cvss_score":8.7,"headline":"ClearanceKit: opfilter policy bypass via non-open file operations","id":"CVE-2026-33631","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.4,"headline":"ClearanceKit: Ad-hoc signed binaries can spoof Apple process identities in the global allowlist","id":"CVE-2026-40599","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":8.4,"headline":"ClearanceKit: opfilter policy bypass via exchangedata and clone operations","id":"CVE-2026-33632","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":6.3,"headline":"ClearanceKit: Managed and user-defined policy rules not enforced between opfilter start and first policy modification","id":"CVE-2026-34218","kev_date_added":null,"published":"2026-03-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-21","vendors":["craigjbass"]},"summary":"A root process can suspend the ClearanceKit macOS extension, causing file-access policies to fail open and allowing unauthorized file access.","url":"https://insights.sbomify.com/CVE-2026-40604/"}