Atomic Server flaw lets uploaded HTML files hijack accounts; no patch yet
A GitHub advisory describes a high-severity stored XSS bug in Atomic Server's /download route that could let an authenticated user steal other users' sessions and signing keys. Versions 0.30.0 through 0.40.1 are affected, and no fixed release is listed.
Atomic Server, a Rust-based data server, has a stored cross-site scripting flaw that can lead to account takeover, according to an advisory published November 18 in the GitHub Advisory Database. The bug is tracked as CVE-2026-69155 (GHSA-x277-3wcg-g9r2). [1]
The advisory lists rust/atomic-server versions 0.30.0 through 0.40.1 as affected and names no patched version. GitHub rates the issue high, with a CVSS score of 8.7. [1]
According to the advisory, files uploaded through POST /upload are returned by GET /download/{path}. HTML and SVG files are served with an inline content disposition, so browsers render them instead of downloading them. The route also sets no Content-Security-Policy or X-Content-Type-Options: nosniff header, and it serves files from the same origin as the application interface. [1]
In the scenario the advisory describes, an authenticated user uploads a malicious HTML file and sends the link to a victim. When the victim opens it, the script runs in the app's origin. It can read the session cookie, which is not marked HttpOnly, and the user's Ed25519 private key stored in IndexedDB. That would let the attacker sign commits as the victim indefinitely. The advisory says that if the victim is an admin or root agent, the result is server takeover. [1]
The report states that the behaviour was confirmed at the HTTP layer in a lab setting. It says in-browser execution and key theft follow from the response headers but were not separately demonstrated. The advisory does not say whether the flaw has been exploited in the wild. [1]
The advisory recommends several fixes: forcing attachment downloads on /download, adding nosniff and a sandboxing CSP, serving uploads from a separate origin, setting HttpOnly and Secure on the session cookie, and keeping the private key out of JavaScript-readable storage. [1]
Sources
- GitHub Advisory Database: GHSA-x277-3wcg-g9r2 (CVE-2026-69155): Atomic Server: Stored XSS via uploaded files served inline (same-origin) on `/download` → account takeoverSource published · TechDots found it
Statements labelled as a company's claim have not been independently confirmed by TechDots.
Get Cybersecurity stories by email
Related coverage
AWS reworks Well-Architected Framework, adding secure coding and backup resilience guidance
AWS says its updated Well-Architected Framework splits environment-wide guardrails from per-workload reviews, adds secure coding and ransomware-resilient backup practices, and trims workload best practices from 307 to 216 to ease automated reviews.
AWS previews Infoblox threat intelligence rules inside Route 53 Resolver DNS Firewall
AWS says Infoblox Threat Defense is now in preview in Route 53 Resolver DNS Firewall, letting customers subscribe via AWS Marketplace to partner-managed DNS threat feeds. The Marketplace fee is waived during preview, but the rules require the paid DNS Firewall Advanced option.
Cloudflare picks leader-optional QuePaxa algorithm to keep its global Meerkat control plane moving
Cloudflare says its experimental Meerkat consensus service runs on QuePaxa, a 2023 academic algorithm that does not depend on a single leader, to avoid stalls on volatile wide-area networks. The performance figures come from Cloudflare's own testing and have not been independently verified.