{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34218 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34218 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34218 is a medium-severity missing authorization vulnerability in craigjbass clearancekit, published on 31 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-34218 and fix it if it is affected.\n\nWhat it is: CVE-2026-34218 is a medium-severity missing authorization vulnerability in craigjbass clearancekit, published on 31 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-34218 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-34218/ (Markdown: https://insights.sbomify.com/CVE-2026-34218/index.md)","id":"CVE-2026-34218","markdown":"https://insights.sbomify.com/CVE-2026-34218/index.md","name":"CVE-2026-34218","record":{"aliases":["GHSA-fpmv-5wgw-qhhr"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"macOS security tool","requires_auth":"none","summary":"Attackers can bypass file-access policies on macOS before the first policy modification, allowing unauthorized file access until GUI interaction occurs.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"clearancekit","vendor":"craigjbass"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to version 4.2.14, two related startup defects created a window during which only the single compile-time baseline rule was enforced by opfilter. All managed (MDM-delivered) and user-defined file-access rules were not applied until the user interacted with policies through the GUI, triggering a policy mutation over XPC. This issue has been patched in version 4.2.14.","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: Managed and user-defined policy rules not enforced between opfilter start and first policy modification","id":"CVE-2026-34218","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"libp2p-gossipsub: Gossipsub PRUNE Backoff Heartbeat Instant Overflow","id":"CVE-2026-34219"},"packages":[],"prev":{"headline":"SandboxJS has a Sandbox Escape via Prop Object Leak in New Handler","id":"CVE-2026-34217"},"products":["clearancekit"],"published":"2026-03-31","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":8.2,"headline":"Security feature bypass in clearancekit","id":"CVE-2026-40604","kev_date_added":null,"published":"2026-04-21"}],"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-02","vendors":["craigjbass"]},"summary":"Attackers can bypass file-access policies on macOS before the first policy modification, allowing unauthorized file access until GUI interaction occurs.","url":"https://insights.sbomify.com/CVE-2026-34218/"}