Skip to main content
Menu
CVEs

Seafile SeaDoc remote code execution in confluence-to-wiki converter

Affects SeaDoc 2.0.4 before 2.0.11 and 3.0.0 before 3.0.8 on instances with a public .sdoc share link or a published wiki. Fixed in 2.0.11 and 3.0.8.

CVE-2026-129167EUVD-2026-125600Published November 13, 2026, updated

9.2CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 2.0.11, 3.0.8
Who is exposed
Not reported

Summary

Written by a model

Seafile SeaDoc converter 2.0.4 before 2.0.11 and 3.0.0 before 3.0.8 contains an absolute path traversal vulnerability that allows unauthenticated attackers holding a public share token to execute code. Attackers supply an absolute filename to /api/v1/confluence-to-wiki/ to extract a ZIP from download_url into the Python library path, then trigger the module's import via a file-convert request.

Who should check

Teams running Seafile SeaDoc 2.0.4 to 2.0.10 or 3.0.0 to 3.0.7 with a public .sdoc share link or a published wiki

“SeaDoc converter 2.0.4 before 2.0.11 and 3.0.0 before 3.0.8”

vulncheck.com

What to do

Upgrade to a fixed version: 2.0.11, 3.0.8.

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-129167 (SeaDoc converter 2.0.4 before 2.0.11 and 3.0.0 before 3.0.8 Path Traversal RCE via confluence-to-wiki), 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-129167 (entry last updated 2026-11-18):
Affected:
- Seafile SeaDoc: from 2.0.4, fixed in 2.0.11; from 3.0.0, fixed in 3.0.8
Fixed versions: 2.0.11, 3.0.8.
Conditions (all must be true for the bug to be hit):
- Instance has a public .sdoc share link or a published wiki (source: https://vul.yulun.ac.cn/20261024/seafile/)
- SeaDoc 2.0 or 3.0 deployment made before the advisory's 2026-11-02 cutoff (source: https://vul.yulun.ac.cn/20261024/seafile/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129167 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129167 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/haiwen/seadoc-converter/commit/cb43162e8bc2991a2900c8acf85090358a30e516
- https://vul.yulun.ac.cn/20261024/seafile/
- https://github.com/haiwen/seadoc-converter/blob/bb6cf0fb9ebc6bb05c9161acbfd6289737ec2cd6/seadoc_converter/server/apis.py#L26-L42
- https://github.com/haiwen/seadoc-converter/blob/bb6cf0fb9ebc6bb05c9161acbfd6289737ec2cd6/seadoc_converter/server/apis.py#L360-L395
- https://www.vulncheck.com/advisories/seadoc-converter-2.0.4-before-2.0.11-and-3.0.0-before-3.0.8-path-traversal-rce-via-confluence-to-wiki
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-129167
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-129167"}.

Affected versions

cve.now Index

42of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.2, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now5 days
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 13Nov 22
  • EPSS: 0.72%
  • Posted on X by cve.now Nov 13

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 7

Questions about CVE-2026-129167

Is CVE-2026-129167 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A path traversal flaw in the SeaDoc converter lets an attacker who holds a public .sdoc share link run commands through the converter. The advisory reproduced this as root.

Source: vul.yulun.ac.cn, vulncheck.com

Which versions are affected by CVE-2026-129167?

SeaDoc: from 2.0.4 before 2.0.11; from 3.0.0 before 3.0.8.

Source: cve.now feed data

Am I affected, and how do I check?

SeaDoc 2.0.4 before 2.0.11 and 3.0.0 before 3.0.8 are affected, in deployments with a public .sdoc share link or a published wiki. The advisory covers SeaDoc 2.0 and 3.0 deployments made before 2026-11-02. Check the installed SeaDoc version and whether public .sdoc share links or a published wiki exist on the instance.

Source: vul.yulun.ac.cn, vulncheck.com

How do I fix CVE-2026-129167?

Upgrade to SeaDoc 2.0.11 or 3.0.8, matching the release line in use.

Source: vul.yulun.ac.cn, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.