CVE
Atomic Server account takeover via stored XSS in file downloads
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 0.40.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.40.3.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Atomic Server has a stored cross-site scripting flaw: uploaded HTML or SVG files are served inline from the application's own origin. An attacker with a logged-in account that has folder write access can exploit this over the network, and when a victim opens a crafted download link, the attacker's script can read the session cookie and the agent private key, allowing persistent account impersonation.
Written by a model from the sources below. Verify against them.
Original description
Atomic Server is an open source headless CMS and real-time database. From 0.30.0 until 0.40.3, an authenticated Agent with folder write access can use POST /upload to store HTML or SVG content that GET /download/{path} serves from the application origin through server/src/handlers/download.rs. The response sets Content-Disposition: inline and lacks forced attachment handling and X-Content-Type-Options: nosniff, allowing the browser to render the uploaded active content as the application. When a victim opens the link, the script can access the JavaScript-readable atomic_session cookie and the Agent private key in same-origin IndexedDB, enabling persistent account impersonation. This issue is fixed in version 0.40.3.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.40.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-69155 (Atomic Server: Stored XSS via uploaded files served inline (same-origin) on `/download` → account takeover), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-69155 (entry last updated 2026-11-17):
Affected:
- ontola atomic-server: from 0.30.0, fixed in 0.40.3
Fixed versions: 0.40.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-69155 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69155 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ontola/atomic-server/security/advisories/GHSA-x277-3wcg-g9r2
- https://github.com/ontola/atomic-server/commit/457c1dc9af4cd00d2aec89720718e504a49f392d
- https://github.com/ontola/atomic-server/commit/8a8badfd3099765e62ccf6f92dc78a408a11106f
- https://github.com/ontola/atomic-server/releases/tag/v0.40.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-69155
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-69155"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- ontola atomic-server
From 0.30.0 · fixed in 0.40.3
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-69155
Is CVE-2026-69155 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-69155?
atomic-server: from 0.30.0 before 0.40.3.Source: cve.now feed data
How do I fix CVE-2026-69155?
Upgrade to a fixed version: 0.40.3.Source: cve.now feed data