CVE-2026-39107
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 · uneditedA Cross Site Scripting vulnerability exists in the Kimi AI v1.0 web interface's 'Preview' feature. The application fails to properly sanitize or encode HTML/JavaScript payloads generated by the AI model. When a user switches to the 'Preview' tab to view AI-generated code, the malicious payload is rendered directly into the DOM, leading to arbitrary JavaScript execution in the victim's browser session.
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 confidenceA stored Cross Site Scripting vulnerability exists in Kimi AI v1.0's web interface 'Preview' feature. The application renders AI-generated content directly into the DOM without sanitizing or encoding HTML/JavaScript payloads, allowing arbitrary script execution when users view the Preview tab.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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.
-
Identify the installed Kimi AI versionCheck the web interface version by looking at the application settings, about page, or checking the response headers for version information. Look for 'v1.0' or check the login/application URL for version indicators.Affected if The installed version is Kimi AI v1.0 specifically.
-
Locate the Preview featureIn the Kimi AI web interface, navigate to the feature where AI-generated content can be viewed. Look for a 'Preview' tab or toggle that switches from raw/code view to rendered view.Affected if The Preview tab exists and is accessible in the web interface.
-
Test for reflected content renderingGenerate content using the AI, then switch to the Preview tab. Inspect the DOM using browser developer tools (F12) to see if the content is rendered as raw HTML or if it's being processed by a sanitization library.Affected if Content appears directly in the DOM without visible encoding or sanitization markers.
-
Check for sanitization in the application codeUse browser developer tools to examine the JavaScript handling the Preview feature. Look for references to sanitization libraries like DOMPurify, or inspect network requests to see if content is processed server-side before rendering.Affected if No sanitization library (DOMPurify, sanitize-html, etc.) is loaded or referenced in the Preview feature code.
A user is affected if they are running Kimi AI v1.0 web interface, have access to the Preview feature, and the AI-generated content is rendered without any visible sanitization or encoding being applied.
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.
From vendor dataImplement context-appropriate output encoding and content sanitization (e.g., using a library like DOMPurify) on all AI-generated content before rendering in the Preview feature, ensuring HTML entities are properly escaped.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39107 — 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-39107 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