Skip to main content
Menu
CVEs

CVE

Atomic Server arbitrary file read in the /download handler

CVE-2026-69156EUVD-2026-127553

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

8.1HighCNA
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.

Published
Last modified
Reference
Last checked
11/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Atomic Server, an open source headless CMS and real-time database, has an arbitrary file read flaw in its download handler. A remote attacker with a low-privilege login can abuse a crafted internal ID value on a resource they own to read files the server process can access, including the root agent private key, which allows full read, write, and delete access to server data.

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, the Commit application path in lib/src/commit.rs allows an authenticated Agent to assign the server-managed internalId property to an owned resource without character validation. The /download handler in server/src/handlers/download.rs passes that value to filesystem path construction and NamedFile::open without sanitization, containment validation, or a File-class check, so traversal or absolute paths can read files available to the server process. Reading the server configuration can expose the root Agent private key and allow root impersonation with full read, write, and delete access to server data. This issue is fixed in version 0.40.3.

cve.now Index

11Pcve.now Index 11 of 100 · methodology v3 · provisional
  • 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.1/10CVSS 8.1
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 30 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-69156 (Atomic Server: Arbitrary file read via user-controlled `internalId` in the `/download` handler (leaks root agent private key)), 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-69156 (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-69156 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69156 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-8vc4-8hjq-988p
- https://github.com/ontola/atomic-server/commit/59d067c797c946b839c9101fedff4c40171c0c61
- 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-69156
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-69156"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • ontola atomic-server

    From 0.30.0 · fixed in 0.40.3

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Repository
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-69156

Is CVE-2026-69156 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-69156?

atomic-server: from 0.30.0 before 0.40.3.Source: cve.now feed data

How do I fix CVE-2026-69156?

Upgrade to a fixed version: 0.40.3.Source: cve.now feed data

More CVEs