# CVE-2026-79653: Path traversal in Eclipse SW360

> Attackers can manipulate filenames during upload to achieve arbitrary file path traversal when file system storage is enabled.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **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:** 27 Aug 2026
- **Updated:** 27 Aug 2026

## What is CVE-2026-79653?

CVE-2026-79653 is a medium-severity path traversal vulnerability in Eclipse SW360, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Eclipse SW360 versions 19.0.0, 19.1.0, 19.2.0, 20.0.0, 20.1.0, if the system is configured to use file system storage with config key enable.attachment.store.to.file.system, the attacker can manipulate the filename upon upload and can essentially cause arbitrary file path traversal.

The immediate workaround is to disable enable.attachment.store.to.file.system or update to fixed versions.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-79653 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79653 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79653 is a medium-severity path traversal vulnerability in Eclipse SW360, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79653 exists.

Affected product: Eclipse SW360. 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-2026-79653/ (Markdown: https://insights.sbomify.com/CVE-2026-79653/index.md)
```

## Sources

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

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