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 en…

published 2026-08-27 2 mo ago modified 2026-09-01 2 mo ago also EUVD-2026-67130

cvss: 6.0; version 4.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 3

Eclipse Foundation Eclipse SW360 20.0.1, 20.1.1

github.com/eclipse-sw360/sw360#4518 pull request
github.com/eclipse-sw360/sw360#4517 pull request
github.com/eclipse-sw360/sw360#4516 pull request

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 2 mo ago (2026-08-27)

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

gitlab.eclipse.org https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/765 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	4.0	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
CNA	4.0	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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

Eclipse Foundation Eclipse SW360

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory
CWE-73 External Control of File Name or Path

References

Sources

CVE List CVE-2026-79653
NVD CVE-2026-79653

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary