What is CVE-2026-55650?

CVE-2026-55650 is a medium-severity cross-site scripting (XSS) vulnerability in @outerbase/studio (npm), affecting versions <= 0.10.2. No fixed version is listed yet. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2026-55650?

CVE-2026-55650 has a CVSS score of 4.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @outerbase/studio are affected by CVE-2026-55650?

@outerbase/studio (npm) versions <= 0.10.2 is affected.

Is there a fix for CVE-2026-55650?

No fixed version is listed for CVE-2026-55650 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2026-55650 exploitable, and should I be worried?

Whether CVE-2026-55650 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-55650 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-55650?

No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.

CVE-2026-55650 in @outerbase/studio

Q: How severe is CVE-2026-55650?

CVE-2026-55650 has a CVSS score of 4.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @outerbase/studio are affected by CVE-2026-55650?

@outerbase/studio (npm) versions <= 0.10.2 is affected.

Q: Is there a fix for CVE-2026-55650?

No fixed version is listed for CVE-2026-55650 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2026-55650 exploitable, and should I be worried?

Whether CVE-2026-55650 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-55650 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-55650?

No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.

Summary

Outerbase Studio: Stored XSS in Text Widget Leads to Authentication Token Exposure

Full technical description

A Stored Cross-Site Scripting (XSS) issue previously existed in the Text Widget in Board of Outerbase Studio where unsanitized HTML could be rendered using dangerouslySetInnerHTML

Steps to Reproduce

Create a new dashboard.
Add a Text widget.
Insert the following payload:

<img src=x onerror="alert('XSS Executed\nToken: ' + localStorage.getItem('ob-token'))">

Architectural Context

Outerbase Cloud and its backend services were discontinued in 2025.

The current version of Outerbase Studio operates purely as a client-side application, with dashboard data stored locally in the browser.

Impact

In the current architecture, the impact is limited to local self-XSS within a user's browser session.
The previously described scenarios involving:

authentication token theft
account takeover
database access

are no longer applicable since there are no active backend services or authentication tokens.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-55650 has a CVSS score of 4.4 (Medium). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

@outerbase/studio (<= 0.10.2)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The unsafe HTML rendering in the Text Widget has been removed in commit https://github.com/outerbase/studio/commit/b06fb85e5967440278d5a815721b360920566ab9 by eliminating the use of dangerouslySetInnerHTML.

Frequently Asked Questions

What is CVE-2026-55650? CVE-2026-55650 is a medium-severity cross-site scripting (XSS) vulnerability in @outerbase/studio (npm), affecting versions <= 0.10.2. No fixed version is listed yet. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2026-55650? CVE-2026-55650 has a CVSS score of 4.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @outerbase/studio are affected by CVE-2026-55650? @outerbase/studio (npm) versions <= 0.10.2 is affected.
Is there a fix for CVE-2026-55650? No fixed version is listed for CVE-2026-55650 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2026-55650 exploitable, and should I be worried? Whether CVE-2026-55650 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-55650 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-55650? No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.