Protected-file writes via unchecked destination paths
Published Apr 10, 2026 · Updated Apr 10, 2026
Incorrect authorization in ClearanceKit before 5.0.4-beta-1f46165 allows local users to write files into protected directories. Its Endpoint Security event handler evaluated only the source path for rename, link, copyfile, exchangedata, and clone operations, leaving each destination unchecked. Low-privileged local access and a configured FAA rule or App Jail policy are required; exploitation permits placing, linking, or replacing protected files.
Summary
What happened
Incorrect authorization in ClearanceKit before 5.0.4-beta-1f46165 allows local users to write files into protected directories. Its Endpoint Security event handler evaluated only the source path for rename, link, copyfile, exchangedata, and clone operations, leaving each destination unchecked. Low-privileged local access and a configured FAA rule or App Jail policy are required; exploitation permits placing, linking, or replacing protected files.
The record
- CVE
- CVE-2026-40191
- Published
- Apr 10, 2026
- Updated
- Apr 10, 2026
- Vendor
- Craig J. Bass
- Product
- ClearanceKit
- Classifications
- CWE-863, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 10, 2026CVE publishedPublication date reported by the CVE source.
- Apr 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.0.4-beta-1f46165
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitHub advisory rename reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo