OpensiftApplication
CVE-2026-27189
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenSift is an AI study tool that sifts through large datasets using semantic search and generative AI. Versions 1.1.2-alpha and below, use non-atomic and insufficiently synchronized local JSON persistence flows, potentially causing concurrent operations to lose updates or corrupt local state across sessions/study/quiz/flashcard/wellness/auth stores. This issue has been fixed in version 1.1.3-alpha.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenSift versions 1.1.2-alpha and below have a race condition in local JSON persistence where concurrent operations to write data (across sessions, study, quiz, flashcard, wellness, and auth stores) lack proper synchronization. Non-atomic file writes can result in lost updates or data corruption when multiple processes or threads access the same JSON files simultaneously.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OpensiftApplication
< 1.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check OpenSift versionRun 'opensift --version' or check the package.json/version file in the OpenSift installation directoryAffected if Version is 1.1.2-alpha or lower (any version below 1.1.3)
-
Identify active JSON persistence storesExamine the OpenSift configuration or application data directory for JSON files related to sessions, study, quiz, flashcard, wellness, and auth storesAffected if Any of these stores are using local JSON file persistence (as opposed to database or remote storage)
-
Verify concurrent access patternsMonitor the application or review logs for multi-process or multi-threaded access to the same JSON store files simultaneouslyAffected if Multiple processes or threads write to the same JSON store files at overlapping times
-
Inspect JSON file integrityExamine the JSON data files in the OpenSift data directory for signs of partial writes, truncation, or inconsistent data patternsAffected if JSON files contain corrupted data, missing updates, or unexpected truncation compared to expected state
You are affected if OpenSift version is below 1.1.3 and any of the JSON-based stores (sessions, study, quiz, flashcard, wellness, or auth) are accessed concurrently by multiple processes or threads.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.1.3
Upgrade to version 1.1.3-alpha which contains the fix for proper atomic writes and synchronization, or implement file locking mechanisms around all JSON persistence operations to ensure serialize access.
1.1.3-alpha
- Upgrade OpenSift to version 1.1.3-alpha or later to resolve the race condition in local JSON persistence flows
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Opensift
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27189 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27189 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data