The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-129167: Seafile SeaDoc flaw allows code execution

By The Daily Byte ·15 Nov 2026 ·3 min read
Two people working on laptops with documents at a desk in a bright office

A public share link for a Seafile document could hand an attacker code execution on the server behind it. The flaw, tracked as CVE-2026-129167, affects the SeaDoc collaborative document editor and is fixed in SeaDoc 2.0.11 and 3.0.8.

SeaDoc runs as three processes: the Seafile web front end, the sdoc-server, and the seadoc-converter. All three trust the same signing key, known as JWT_PRIVATE_KEY. When someone opens a public .sdoc share link, the front end places a token in the page so that anonymous preview works. That token is meant to be read-only, but the converter checked only that the token's signature was valid, not what it was allowed to do. As a result, the anonymous token from a public share page was accepted on every converter endpoint.

One of those endpoints, /api/v1/confluence-to-wiki/, took a file name supplied by the caller and used it to build paths without checking whether it was absolute. An attacker could supply an absolute path, have the converter download a ZIP archive and extract it into Python's library path, and then trigger the planted module's import with a file-conversion request. In the researcher's reproduction, the package was planted inside Python's encodings directory, giving code execution inside the converter container.

Who is affected

SeaDoc versions 2.0.4 to 2.0.10 and 3.0.0 to 3.0.7 are affected. The fixed releases are 2.0.11 and 3.0.8. The attack needs a public .sdoc share link or a published wiki, because that is where the anonymous token comes from, and the converter must be reachable through the Seafile front end. In the official Docker Compose deployment it is exposed under /sdoc-server/converter/.

A deployment with no public .sdoc share links and no published wiki does not expose the token path described here. But any organisation that shares documents publicly should assume the route was available and patch promptly.

The fix

The open-source seadoc-converter fix is commit cb43162e, dated 29 October 2026, which adds validation of the file name and related inputs on the affected endpoint. The sdoc-server component is closed source; Haiwen, the company behind Seafile, told the researcher by email on 2 November 2026 that SeaDoc 2.0 and 3.0 were fixed. Administrators should upgrade to SeaDoc 2.0.11 or 3.0.8, or later, and re-pull the seafileltd/sdoc-server image.

After updating, it is worth checking the converter container for unexpected directories under Python's encodings folder, which is where the researcher's proof placed its package. Any unfamiliar files there should be treated as a sign of compromise and investigated before the system is trusted again.

Exploitation status

The CVE record was published on 13 November 2026 and rates the flaw 9.2 Critical under CVSS 4.0 and 8.1 High under CVSS 3.1. It is classified as CWE-36, absolute path traversal. No exploitation in the wild has been reported, and the flaw was not in CISA's Known Exploited Vulnerabilities catalogue as of 14 November 2026. The researcher's write-up describes a laboratory reproduction, not a campaign, but the attack requires no account and no user interaction beyond holding a public share token, so exposed deployments should not wait for evidence of attacks before patching.

Sources: Ostorlab, Seafile SeaDoc RCE via Public Share Link (CVE-2026-129167); Red Packet Security, CVE Alert: CVE-2026-129167.