{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-47133 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-47133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47133 is a medium-severity vulnerability in craigjbass clearancekit, published on 20 Jul 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-47133 and fix it if it is affected.\n\nWhat it is: CVE-2026-47133 is a medium-severity vulnerability in craigjbass clearancekit, published on 20 Jul 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-47133 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-47133/ (Markdown: https://insights.sbomify.com/CVE-2026-47133/index.md)","id":"CVE-2026-47133","markdown":"https://insights.sbomify.com/CVE-2026-47133/index.md","name":"CVE-2026-47133","record":{"aliases":["GHSA-9hx3-5wp9-2qqg"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"macOS security tool","requires_auth":"high_privilege","summary":"Attackers can bypass file access controls by replaying old signed policy snapshots, requiring local write access to the database.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to version 5.0.10, each table in the on-disk SQLite policy store (`/Library/Application Support/clearancekit/store.db`) is verified using an ECDSA signature stored in the `data_signatures` table. The signed payload contains only the canonical row content, with no version counter or freshness binding. An attacker who can write `store.db` and the matching `data_signatures` row — feasible during the opfilter-update window when the Endpoint Security filter is offline, or via offline-boot / decrypted-backup scenarios — can substitute a previously-captured legitimately-signed snapshot. opfilter accepts the older snapshot as fully valid on next boot because the existing signatures still verify. Version 5.0.10 patches the issue.","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's signed policy tables lack monotonic counter, allowing replay of older legitimately-signed snapshots","id":"CVE-2026-47133","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":"Security feature bypass in clearancekit","id":"CVE-2026-47134"},"packages":[],"prev":{"headline":"phpMyFAQ: SQL LIKE Wildcard Injection in Chat User Search Allows Authenticated User Enumeration","id":"CVE-2026-47132"},"products":["clearancekit"],"published":"2026-07-20","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":"partial"},"state":"PUBLISHED","updated":"2026-07-21","vendors":["craigjbass"]},"summary":"Attackers can bypass file access controls by replaying old signed policy snapshots, requiring local write access to the database.","url":"https://insights.sbomify.com/CVE-2026-47133/"}