# 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


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-pfpf-25qg-8vx8

## What is CVE-2026-129167?

CVE-2026-129167 is a critical vulnerability in Seafile SeaDoc, published on 13 Nov 2026. 

### Official description

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.

Weakness: CWE-36 (Absolute Path Traversal)

## Which versions are affected by CVE-2026-129167?

2 open source packages ship an affected version, including haiwen/seadoc-converter.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `haiwen/seadoc-converter` | GitHub | `pkg:github/haiwen/seadoc-converter` | From 2.0.4 | 2.0.11 |
| `haiwen/seadoc-converter` | GitHub | `pkg:github/haiwen/seadoc-converter` | From 3.0.0 | 3.0.8 |

## How do I fix CVE-2026-129167?

Upgrade haiwen/seadoc-converter to a fixed version for your release line: 2.0.11 or 3.0.8.

## Is CVE-2026-129167 being exploited?

There is no known exploitation of CVE-2026-129167 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129167 and fix it if it is affected.

What it is: CVE-2026-129167 is a critical vulnerability in Seafile SeaDoc, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129167 in the wild and no public exploit code.

Affected packages and fixed versions:
- haiwen/seadoc-converter (GitHub): affected from 2.0.4; fixed in 2.0.11
- haiwen/seadoc-converter (GitHub): affected from 3.0.0; fixed in 3.0.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129167/ (Markdown: https://insights.sbomify.com/CVE-2026-129167/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129167
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129167
- OSV: https://osv.dev/vulnerability/CVE-2026-129167

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129167/
Summaries are generated and may contain mistakes; the official description above is the record.
