CVE-2026-47133

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.

CVSS

No CVSS.

References

Link	Resource
https://github.com/craigjbass/clearancekit/security/advisories/GHSA-9hx3-5wp9-2qqg

Configurations

No configuration.

History

24 Oct 2026, 20:10

Type	Values Removed	Values Added
Summary		(es) ClearanceKit intercepta eventos de acceso al sistema de archivos en macOS y aplica políticas de acceso por proceso. Antes de la versión 5.0.10, cada tabla en el almacén de políticas SQLite en disco (’/Library/Application Support/clearancekit/store.db’) se verifica usando una firma ECDSA almacenada en la tabla ’data_signatures’. La carga útil firmada contiene solo el contenido canónico de la fila, sin contador de versión ni vinculación de frescura. Un atacante que puede escribir ’store.db’ y la fila ’data_signatures’ correspondiente - factible durante la ventana de actualización de opfilter cuando el filtro de seguridad de punto final está desconectado, o mediante escenarios de arranque sin conexión / copia de seguridad descifrada - puede sustituir una instantánea capturada previamente y firmada legítimamente. opfilter acepta la instantánea más antigua como totalmente válida en el siguiente arranque porque las firmas existentes aún verifican. La versión 5.0.10 corrige el problema.

Information

Published : 2026-07-20 22:17

Updated : 2026-10-24 20:10

NVD link : CVE-2026-47133

Mitre link : CVE-2026-47133

CVE.ORG link : CVE-2026-47133

JSON object : View

Products Affected

No product.

CWE

CWE-294

Authentication Bypass by Capture-replay

{"id": "CVE-2026-47133", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-47133", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-21T14:08:57.775610Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 6.9, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "HIGH", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "craigjbass", "product": "clearancekit", "versions": [{"status": "affected", "version": "< 5.0.10"}]}]}], "published": "2026-07-20T22:17:14.997", "references": [{"url": "https://github.com/craigjbass/clearancekit/security/advisories/GHSA-9hx3-5wp9-2qqg", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-294"}]}], "descriptions": [{"lang": "en", "value": "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 \u2014 feasible during the opfilter-update window when the Endpoint Security filter is offline, or via offline-boot / decrypted-backup scenarios \u2014 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."}, {"lang": "es", "value": "ClearanceKit intercepta eventos de acceso al sistema de archivos en macOS y aplica pol\u00edticas de acceso por proceso. Antes de la versi\u00f3n 5.0.10, cada tabla en el almac\u00e9n de pol\u00edticas SQLite en disco (\u2019/Library/Application Support/clearancekit/store.db\u2019) se verifica usando una firma ECDSA almacenada en la tabla \u2019data_signatures\u2019. La carga \u00fatil firmada contiene solo el contenido can\u00f3nico de la fila, sin contador de versi\u00f3n ni vinculaci\u00f3n de frescura. Un atacante que puede escribir \u2019store.db\u2019 y la fila \u2019data_signatures\u2019 correspondiente - factible durante la ventana de actualizaci\u00f3n de opfilter cuando el filtro de seguridad de punto final est\u00e1 desconectado, o mediante escenarios de arranque sin conexi\u00f3n / copia de seguridad descifrada - puede sustituir una instant\u00e1nea capturada previamente y firmada leg\u00edtimamente. opfilter acepta la instant\u00e1nea m\u00e1s antigua como totalmente v\u00e1lida en el siguiente arranque porque las firmas existentes a\u00fan verifican. La versi\u00f3n 5.0.10 corrige el problema."}], "lastModified": "2026-10-24T20:10:00.137", "sourceIdentifier": "security-advisories@github.com"}