Skip to main content
VulnerabilityPublished Updated

CVE-2026-54386: marimo · Cross-site Scripting

Affects marimoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 0.23.9 when convenient.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.23.9
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade marimo to 0.23.9.

Affected software

ProductAffectedFixed in
marimo-teammarimoAffected
  • <0.23.9
Fixed in–
GitHubmarimopkg:github/marimoOther threatsAffected
  • <0.23.9
Fixed in
  • 0.23.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should avoid exposing vulnerable versions to untrusted networks or users. Implementing web application firewalls or input validation may provide temporary mitigation but are not guaranteed to fully prevent exploitation.

Description

marimo before 0.23.9 contains a reflected cross-site scripting vulnerability in the notebook page that allows unauthenticated attackers to inject arbitrary JavaScript by exploiting improper escaping of single quotes in the file query parameter reflected into an inline JavaScript string literal. Attackers can craft a malicious link with a payload beginning with __new__ to bypass the 404 check and inject JavaScript into the page, which executes without Content-Security-Policy restrictions in the origin of a victim's marimo server.

References

Community reviews

Loading reviews…