{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33631 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-33631 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33631 is a high-severity vulnerability in craigjbass clearancekit, published on 26 Mar 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-33631 and fix it if it is affected.\n\nWhat it is: CVE-2026-33631 is a high-severity vulnerability in craigjbass clearancekit, published on 26 Mar 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-33631 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-33631/ (Markdown: https://insights.sbomify.com/CVE-2026-33631/index.md)","id":"CVE-2026-33631","markdown":"https://insights.sbomify.com/CVE-2026-33631/index.md","name":"CVE-2026-33631","record":{"aliases":["GHSA-25f8-8cj2-m887"],"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":"low_privilege","summary":"Local attackers can bypass file access policies in ClearanceKit by using file operations not intercepted by the security extension.","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.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. In versions on the 4.1 branch and earlier, the opfilter Endpoint Security system extension enforced file access policy exclusively by intercepting ES_EVENT_TYPE_AUTH_OPEN events. Seven additional file operation event types were not intercepted, allowing any locally running process to bypass the configured FAA policy without triggering a denial. Commit a3d1733 adds subscriptions for all seven event types and routes them through the existing FAA policy evaluator. AUTH_RENAME and AUTH_UNLINK additionally preserve XProtect change detection: events on the XProtect path are allowed and trigger the existing onXProtectChanged callback rather than being evaluated against user policy. All versions on the 4.2 branch contain the fix. No known workarounds are available.","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":"ClearanceKit: opfilter policy bypass via non-open file operations","id":"CVE-2026-33631","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ClearanceKit: opfilter policy bypass via exchangedata and clone operations","id":"CVE-2026-33632"},"packages":[],"prev":{"headline":"Use after free in c-ares","id":"CVE-2026-33630"},"products":["clearancekit"],"published":"2026-03-26","related":[{"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":8.2,"headline":"Security feature bypass in clearancekit","id":"CVE-2026-40604","kev_date_added":null,"published":"2026-04-21"},{"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":"total"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["craigjbass"]},"summary":"Local attackers can bypass file access policies in ClearanceKit by using file operations not intercepted by the security extension.","url":"https://insights.sbomify.com/CVE-2026-33631/"}