{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22249 exists.","fix":"No fix has been published for CVE-2026-22249 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22249 is a high-severity path traversal vulnerability in docmost, published on 15 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-22249 and fix it if it is affected.\n\nWhat it is: CVE-2026-22249 is a high-severity path traversal vulnerability in docmost, published on 15 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22249 exists.\n\nAffected product: docmost. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-22249/ (Markdown: https://insights.sbomify.com/CVE-2026-22249/index.md)","id":"CVE-2026-22249","markdown":"https://insights.sbomify.com/CVE-2026-22249/index.md","name":"CVE-2026-22249","record":{"aliases":["GHSA-54pm-hqxm-54wg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Docmost wiki software","requires_auth":"low_privilege","summary":"Attackers can write arbitrary files via ZipSlip in Docmost's import feature, potentially leading to code execution or data modification.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"docmost","vendor":"docmost"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Docmost affected by an Arbitrary File Write via Zip Import Feature (ZipSlip)","id":"CVE-2026-22249","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"wlc can skip SSL verification","id":"CVE-2026-22250"},"packages":[],"prev":{"headline":"GLPI affected by Remote Code Execution via malicious upload","id":"CVE-2026-22248"},"products":["docmost"],"published":"2026-01-15","related":[{"cvss_score":7.3,"headline":"Docmost Affected by Stored XSS in Public Share Page","id":"CVE-2026-24045","kev_date_added":null,"published":"2026-02-10"},{"cvss_score":6.3,"headline":"Docmost is vulnerable to stored Cross-Site Scripting (XSS) through Mermaid rendering","id":"CVE-2026-23630","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-55574","kev_date_added":null,"published":"2025-08-25"},{"cvss_score":5.4,"headline":"Docmost: XSS in Comments with JavaScript URI","id":"CVE-2026-40927","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":5.4,"headline":"Docmost page content has stored XSS via unsanitized attachment URLs","id":"CVE-2026-34212","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":5.4,"headline":"Docmost has cross-page attachment overwrite via flawed attachmentId overwrite validation","id":"CVE-2026-34213","kev_date_added":null,"published":"2026-04-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-15","vendors":["docmost"]},"summary":"Attackers can write arbitrary files via ZipSlip in Docmost's import feature, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/CVE-2026-22249/"}