Skip to main content
Menu
CVEs

CVE

Atomic Server unauthenticated SSRF in the /bookmark endpoint

CVE-2026-69158EUVD-2026-127554

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

8.6HighCNA
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
26/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Atomic Server, an open source headless CMS and real-time database, has a flaw in its /bookmark endpoint that can be reached remotely, without logging in. An attacker can make the server fetch URLs of their choosing and return the content, which can expose internal services and cloud metadata.

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. Prior to 0.40.3, unauthenticated requests to /bookmark can supply a url that server/src/plugins/bookmark.rs passes through fetch_data to fetch_body. Endpoint dispatch in lib/src/db.rs invokes the handler before check_read, and lib/src/client/helpers.rs previously checked only that the URL began with HTTP, without restricting loopback, private, link-local, DNS-rebinding, or redirect targets. The handler reflects fetched content in returned resource fields, making this a full-response server-side request forgery that can expose internal services and plain-GET cloud metadata. The short request timeout limits slow targets, and metadata services requiring a separate token request are outside the demonstrated GET-only path. This issue is fixed in version 0.40.3.

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.6/10CVSS 8.6
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 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-69158 (Atomic Server: Unauthenticated full-response SSRF in Atomic-Server /bookmark endpoint), 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-69158 (entry last updated 2026-11-17):
Affected:
- ontola atomic-server: 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-69158 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69158 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-ff87-73jp-f3v4
- https://github.com/ontola/atomic-server/commit/006ff290f7ec976c8cbafdceb7b6899389abd5be
- https://github.com/ontola/atomic-server/commit/2d4535fcd84761288027616505cc61abdf05bc50
- https://github.com/ontola/atomic-server/commit/e7f551d385045708240ca56889d1334a39349735
- 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-69158
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-69158"}.

Timeline

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

Affected versions

  • ontola atomic-server

    fixed in 0.40.3

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Repository
  2. Repository
  3. Repository
  4. Repository

Corrections

None so far.

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

Questions about CVE-2026-69158

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

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

How do I fix CVE-2026-69158?

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

More CVEs