CVE-2026-39426: MaxKB: Stored XSS via Unsanitized iframe_render Parsing
MaxKB is an open-source AI assistant for enterprise. Versions 2.7.1 and below contain a Stored Cross-Site Scripting (XSS) vulnerability where the frontend's MdRenderer.vue component parses custom <iframerender> tags from LLM responses or Application Prologue configurations, bypassing standard Markdown sanitization and XSS filtering. The unsanitized HTML content is passed to the IframeRender.vue component, which renders it directly into an <iframe> via the srcdoc attribute configured with sandbox="allow-scripts allow-same-origin". This can be a dangerous combination, allowing injected scripts to escape the iframe and execute JavaScript in the parent window using window.parent. Since the Prologue is rendered for any user visiting an application's chat interface, this results in a high-impact Stored XSS that can lead to session hijacking, unauthorized actions, and sensitive data exposure. This issue has been fixed in version 2.8.0.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39426?
CVE-2026-39426 has been classified as a high-severity vulnerability due to the risk of stored XSS attacks.
How do I fix CVE-2026-39426?
To fix CVE-2026-39426, upgrade to MaxKB version 2.8.0 or later.
What types of attacks can CVE-2026-39426 allow?
CVE-2026-39426 can allow attackers to execute arbitrary JavaScript code in the context of authenticated users.
Which versions of MaxKB are affected by CVE-2026-39426?
CVE-2026-39426 affects MaxKB versions 2.7.1 and below.
What component of MaxKB is vulnerable in CVE-2026-39426?
The vulnerability in CVE-2026-39426 resides in the MdRenderer.vue component that improperly parses <iframe_render> tags.