Local state corruption via unsynchronized JSON writes
Published Feb 21, 2026 · Updated Feb 21, 2026
Race condition in OpenSift local JSON persistence before 1.1.3-alpha allows local users to corrupt or lose saved application state. JSON store writes for sessions, study data, quizzes, flashcards, wellness settings, and authentication lack atomic replacement and sufficient locking, so concurrent operations can overwrite updates or leave corrupted state. Exploitation requires low-privileged local access and concurrent operations; the bounded consequence is lost or corrupted locally persisted state.
Summary
What happened
Race condition in OpenSift local JSON persistence before 1.1.3-alpha allows local users to corrupt or lose saved application state. JSON store writes for sessions, study data, quizzes, flashcards, wellness settings, and authentication lack atomic replacement and sufficient locking, so concurrent operations can overwrite updates or leave corrupted state. Exploitation requires low-privileged local access and concurrent operations; the bounded consequence is lost or corrupted locally persisted state.
The record
- CVE
- CVE-2026-27189
- Published
- Feb 21, 2026
- Updated
- Feb 21, 2026
- Vendor
- OpenSift
- Product
- OpenSift
- Classifications
- CWE-362, CWE-367
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 21, 2026CVE publishedPublication date reported by the CVE source.
- Feb 21, 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=< 1.1.3-alpha
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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