{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-40191 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40191 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40191 is a medium-severity vulnerability in craigjbass clearancekit, published on 10 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-40191 and fix it if it is affected.\n\nWhat it is: CVE-2026-40191 is a medium-severity vulnerability in craigjbass clearancekit, published on 10 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-40191 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-40191/ (Markdown: https://insights.sbomify.com/CVE-2026-40191/index.md)","id":"CVE-2026-40191","markdown":"https://insights.sbomify.com/CVE-2026-40191/index.md","name":"CVE-2026-40191","record":{"aliases":["GHSA-92f3-38m7-579h"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"macOS security software","requires_auth":"low_privilege","summary":"Local attackers can bypass file-access protections in ClearanceKit by using dual-path operations that ignore destination path checks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to 5.0.4-beta-1f46165,  ClearanceKit's Endpoint Security event handler only checked the source path of dual-path file operations against File Access Authorization (FAA) rules and App Jail policies. The destination path was ignored entirely. This allowed any local process to bypass file-access protection by using rename, link, copyfile, exchangedata, or clone operations to place or replace files inside protected directories. This vulnerability is fixed in 5.0.4-beta-1f46165.","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 has a policy bypass via dual-path Endpoint Security events checking only source path","id":"CVE-2026-40191","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":"Pillow is vulnerable to a FITS GZIP decompression bomb","id":"CVE-2026-40192"},"packages":[],"prev":{"headline":"LangSmith Client SDKs has Prototype Pollution in langsmith-sdk via Incomplete `__proto__` Guard in Internal lodash `set()`","id":"CVE-2026-40190"},"products":["clearancekit"],"published":"2026-04-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-04-15","vendors":["craigjbass"]},"summary":"Local attackers can bypass file-access protections in ClearanceKit by using dual-path operations that ignore destination path checks.","url":"https://insights.sbomify.com/CVE-2026-40191/"}