CVE-2026-85684: marker through 2.0.0 Path Traversal via upload filename
marker through 2.0.0 contains a path traversal vulnerability in the FastAPI /marker/upload handler that fails to sanitize the file.filename parameter. Unauthenticated attackers can supply filenames containing directory traversal sequences to write arbitrary files to any location or delete existing files on the system.
Security readout for executives and security teams
Plain-English summary
Marker through version 2.0.0 reportedly lets an unauthenticated attacker abuse an uploaded filename to overwrite files or delete existing data. A reachable upload service could therefore suffer serious integrity loss, service disruption, or broader compromise depending on the service account’s filesystem permissions.
Executive priority
Prioritize immediate containment of reachable Marker upload services, then confirm and apply maintainer-approved remediation. Internet-facing or broadly accessible deployments warrant emergency handling because exploitation requires no authentication and could alter or remove files. Isolated deployments remain important but can be prioritized according to reachability and filesystem privileges.
Technical view
The FastAPI /marker/upload handler reportedly uses file.filename without adequately rejecting directory-traversal sequences. CVE-2026-85684 is classified as CWE-73 and scored CVSS 3.1 9.1: network-accessible, low complexity, unauthenticated, and requiring no user interaction, with high integrity and availability impact but no stated confidentiality impact.
Likely exposure
Highest risk applies where Marker through 2.0.0 runs its server component and /marker/upload is reachable by untrusted users. Actual impact depends on filesystem permissions and deployment isolation. The supplied affected-version metadata is inconsistent, listing version "0" while the advisory title and description say through 2.0.0; confirm inventory against vendor guidance.
Exploitation context
The supplied record is not flagged in KEV, and the cited bundle provides no evidence of active exploitation. Exploitation is nevertheless described as remotely reachable without authentication, privileges, or user interaction. Treat exposed instances urgently while distinguishing technical exploitability from confirmed attacks in the wild.
Researcher notes
The supplied evidence identifies unsanitized file.filename handling in marker/scripts/server.py at v2.0.0 and maps the issue to CWE-73. CVSS indicates integrity and availability impacts only. The bundle does not establish a fixed release, patch commit, proof of exploitation, or observed campaigns. Version metadata should be reconciled before asserting an exact affected range.
Mitigation direction
Restrict untrusted access to /marker/upload until vendor-supported remediation is confirmed.
Upgrade according to current Marker maintainer guidance when a fixed release is identified.
Run Marker with minimal filesystem permissions and isolate it from sensitive paths.
Reject traversal sequences and accept only server-generated upload filenames.
Back up critical files and protect backups from the Marker service account.
Validation and detection
Inventory Marker deployments and confirm whether versions through 2.0.0 are present.
Determine whether /marker/upload is internet-facing or otherwise accessible to untrusted users.
Review upload handling to verify filenames cannot escape the intended directory.
Check the Marker process account’s write and delete permissions across the host.
Review filesystem and application logs for unexpected writes, deletions, or suspicious upload filenames.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-73 · source CWE mapping
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.