Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-85684 – Unauthenticated Path Traversal Leading to Arbitrary File Write/RCE – Marker (datala

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-85684 is a path traversal vulnerability (CWE-73: External Control of File Name or Path) in the marker document-processing package by datalab-to (PyPI package marker-pdf), versions through 2.0.0. The flaw resides in the FastAPI /marker/upload handler, which fails to sanitize the file.filename parameter, allowing an unauthenticated network attacker to write arbitrary files to, or delete existing files from, the host filesystem. The vulnerability carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: the upload handler builds the destination path with os.path.join(UPLOAD_DIRECTORY, file.filename), using the client-supplied filename directly with no validation, normalization, or use of os.path.basename().
  • Trigger condition: an attacker submits a file to the /marker/upload endpoint with a filename containing directory traversal sequences (e.g. ../) instead of a plain filename.
  • Attack vector: network, no authentication and no user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: the crafted filename can cause the server to write attacker-controlled content to arbitrary filesystem paths, or overwrite/delete existing files outside the intended upload directory — impacting integrity and availability of the host.

Affected software

  • marker (PyPI package marker-pdf), all versions from 0 through 2.0.0 inclusive.

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
  • CVSS v4.0 Base Score: 8.8 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to a marker release that sanitizes uploaded filenames (verify with the vendor/project which released version resolves this issue, as no fixed version is stated in the CVE record at the time of publication).
  • If no patch is available: Restrict network access to the /marker/upload endpoint (e.g., place it behind authentication, a reverse proxy, or firewall rules limiting exposure to trusted hosts); do not expose the marker server directly to the internet; monitor/alert on file writes outside the configured upload directory; consider deploying the service with a filesystem sandbox or read-only root filesystem to limit write impact.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: <h1>Marker API</h1>

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge