# CVE-2022-44748: Uploading workflows to KNIME Server may override arbitrary file system contents

> Authenticated attackers can overwrite arbitrary server files via malicious ZIP uploads, potentially leading to data corruption or remote code execution.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Nov 2022
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-29c9-qmhw-f6px

## What is CVE-2022-44748?

CVE-2022-44748 is a high-severity path traversal vulnerability in KNIME Server, published on 24 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A directory traversal vulnerability in the ZIP archive extraction routines of KNIME Server since 4.3.0 can result in arbitrary files being overwritten on the server's file system. This vulnerability is also known as 'Zip-Slip'.

An attacker can create a KNIME workflow that, when being uploaded, can overwrite arbitrary files that the operating system user running the KNIME Server process has write access to. The user must be authenticated and have permissions to upload files to KNIME Server.

This can impact data integrity (file contents are changed) or cause errors in other software (vital files being corrupted). It can even lead to remote code execution if executable files are being replaced and subsequently executed by the KNIME Server process user. In all cases the attacker has to know the location of files on the server's file system, though.

Note that users that have permissions to upload workflows usually also have permissions to run them on the KNIME Server and can therefore already execute arbitrary code in the context of the KNIME Executor's operating system user.

There is no workaround to prevent this vulnerability from being exploited. Updates to fixed versions 4.13.6, 4.14.3, or 4.15.3 are advised.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-44748?

It affects 1 product.


Products: Knime Knime Server.

## How do I fix CVE-2022-44748?

No fix has been published for CVE-2022-44748 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-44748 being exploited?

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

## Other vulnerabilities in KNIME Server

- [CVE-2021-44726](https://insights.sbomify.com/CVE-2021-44726/): Cross-site scripting in n/a (high 8.8)
- [CVE-2021-44725](https://insights.sbomify.com/CVE-2021-44725/): Path traversal in n/a (high 7.5)
- [CVE-2021-45097](https://insights.sbomify.com/CVE-2021-45097/): Hardcoded credentials in n/a (low 2.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-44748 and fix it if it is affected.

What it is: CVE-2022-44748 is a high-severity path traversal vulnerability in KNIME Server, published on 24 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-44748 in the wild and no public exploit code.

Affected product: KNIME Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2022-44748/ (Markdown: https://insights.sbomify.com/CVE-2022-44748/index.md)
```

## Sources

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

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