dbcve.org
OpensiftApplication

CVE-2026-27169

HIGH · 8.9 CVSS v3.1 Published 2026-02-21
Fix available
A fix is available. Upgrade to 1.1.3 or later.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable

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 · unedited
OpenSift is an AI study tool that sifts through large datasets using semantic search and generative AI. Versions 1.1.2-alpha and below render untrusted user/model content in chat tool UI surfaces using unsafe HTML interpolation patterns, leading to XSS. Stored content can execute JavaScript when later viewed in authenticated sessions. An attacker who can influence stored study/quiz/flashcard content could trigger script execution in a victim’s browser, potentially performing actions as that user in the local app session. 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 confidence

OpenSift versions 1.1.2-alpha and below contain a stored XSS vulnerability where untrusted user or AI model-generated content in study/quiz/flashcard data is rendered using unsafe HTML interpolation in the chat tool UI. When authenticated users view this stored content, any embedded malicious JavaScript executes within their session, potentially allowing the attacker to perform actions as that user.

MitigationUpgrade to OpenSift version 1.1.3-alpha which contains the fix for the unsafe HTML interpolation. Users should avoid interacting with untrusted content until the update is applied.

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
Affected:< 1.1.3

CVSS 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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OpenSift version
    Check the OpenSift application version through the admin dashboard, package manager, or version endpoint (e.g., /api/version, --version flag, or about page)
    Affected if The installed version is 1.1.2-alpha or below, or any version prior to 1.1.3-alpha
  2. Confirm chat tool UI is accessible
    Log in as an authenticated user and navigate to the chat tool or study interface where quiz/flashcard content is displayed
    Affected if The chat tool UI is active and users can view study/quiz/flashcard content
  3. Verify study/quiz/flashcard data storage exists
    Inspect the database or data store for tables/collections containing study, quiz, or flashcard content that may have been created by users or AI models
    Affected if There are records in study/quiz/flashcard data tables containing user-submitted or AI-generated content
  4. Check content rendering method in UI
    View stored study/quiz/flashcard content through the chat interface and inspect the HTML source or use browser dev tools to see if content is rendered via innerHTML or similar unsafe interpolation
    Affected if The content is rendered directly as HTML without sanitization or escaping (e.g., using v-html in Vue, innerHTML in vanilla JS, or similar unsafe methods)

You are affected if OpenSift version is below 1.1.3-alpha AND the chat tool UI is accessible to authenticated users who can view stored study/quiz/flashcard data containing untrusted content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.1.3 or later
Fixed in 1.1.3
Interim mitigation

Upgrade to OpenSift version 1.1.3-alpha which contains the fix for the unsafe HTML interpolation. Users should avoid interacting with untrusted content until the update is applied.

Recommended fix High confidence

1.1.3-alpha

  1. Identify the current installed version of OpenSift
  2. Locate the project dependency configuration (e.g., package.json, requirements.txt, or similar)
  3. Update the OpenSift dependency to version 1.1.3-alpha or later
  4. Run dependency update/installation command to apply the new version
  5. Verify the upgrade was successful by checking the installed version
  6. Test the chat tool UI with sample content to confirm the XSS fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Opensift Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27169 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27169 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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