dbcve.org
DocmostApplication

CVE-2026-22249

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-15
Fix available
A fix is available. Upgrade to 0.24.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Docmost is an open-source collaborative wiki and documentation software. From 0.21.0 to before 0.24.0, Docmost is vulnerable to Arbitrary File Write via Zip Import Feature (ZipSlip). In apps/server/src/integrations/import/utils/file.utils.ts, there are no validation on filename. This vulnerability is fixed in 0.24.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Docmost versions 0.21.0 through 0.24.0 contain a ZipSlip vulnerability in the Zip import feature. The file extraction logic in apps/server/src/integrations/import/utils/file.utils.ts does not validate filenames, allowing path traversal sequences (../) within the archive to write files to arbitrary filesystem locations outside the intended directory.

MitigationUpgrade Docmost to version 0.24.0 or later, which includes filename validation in the file extraction logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DocmostApplication
Affected:>= 0.21.0, < 0.24.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Docmost version
    Check the package.json file in the Docmost installation directory, or run 'npm list docmost' or check the version in the application's package metadata
    Affected if The installed version is >= 0.21.0 and < 0.24.0
  2. Locate the file extraction utility
    Find the file apps/server/src/integrations/import/utils/file.utils.ts in the Docmost installation directory
    Affected if The file exists and was not patched (no filename validation logic present)
  3. Check for Zip import feature usage
    Review application logs or configuration for any recent import operations that involved zip archives
    Affected if Zip import functionality has been used, enabling the vulnerable code path
  4. Inspect the file extraction code
    Open file.utils.ts and search for extraction logic - look for missing validation of zip entry names before extraction, specifically the absence of checks for '../' or absolute path patterns
    Affected if The code extracts files without validating that the destination path remains within the intended target directory

You are affected if Docmost version is between 0.21.0 and 0.24.0 inclusive and the Zip import feature has been used or could be used with untrusted zip archives.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.24.0 or later
Fixed in 0.24.0
Vendor patch github.com →
Interim mitigation

Upgrade Docmost to version 0.24.0 or later, which includes filename validation in the file extraction logic.

Recommended fix High confidence

0.24.0

  1. 1. Back up your current Docmost installation and database before proceeding with the upgrade.
  2. 2. If using Docker, stop the current Docmost container: docker stop docmost
  3. 3. Pull the new Docker image for version 0.24.0: docker pull docmost/docmost:0.24.0
  4. 4. If using Docker, update your docker-compose.yml or run command to use version 0.24.0, then start the container: docker-compose up -d (or docker start docmost)
  5. 5. If installing directly from source, navigate to your Docmost directory and run: git fetch origin followed by git checkout v0.24.0 or git pull to get the fixed version
  6. 6. Run any database migrations if required for version 0.24.0
  7. 7. Verify the upgrade was successful by checking the Docmost version in the application UI or via API
  8. 8. Test the Zip import functionality to confirm the vulnerability is no longer exploitable
Caveat Review the Docmost 0.24.0 release notes for any configuration or feature changes before upgrading, as minor version upgrades may include new functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Docmost Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22249 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22249 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data