CVE-2026-79653

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.0Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.0
EG Score
6.0(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity60% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 27, 2026

Advisory Details (4)

Auto-updated Aug 27, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

fix(backend): harden attachment filesystem path handling

Fix merged in eclipse-sw360/sw360 PR #4516 on 2026-08-21 — awaiting tagged release

https://github.com/eclipse-sw360/sw360/pull/4516
github_pr

fix(backend): harden attachment filesystem path handling

Fix merged in eclipse-sw360/sw360 PR #4517 on 2026-08-21 — awaiting tagged release

https://github.com/eclipse-sw360/sw360/pull/4517
github_pr

fix(backend): harden attachment filesystem path handling

Fix merged in eclipse-sw360/sw360 PR #4518 on 2026-08-21 — awaiting tagged release

https://github.com/eclipse-sw360/sw360/pull/4518
generic

[Eclipse SW360] Path traversal in filesystem attachment store via unsanitized Attachment.filename (arbitrary file write) (#765) · Issues · Eclipse Projects Security / vulnerability-reports · GitLab

https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/765

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 23:56 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 20:28 UTCEG score recompute
  5. 2026-08-27 20:18 UTCEG score recompute
  6. 2026-08-27 17:27 UTCEG score recompute
  7. 2026-08-27 16:49 UTCEG score recompute
  8. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-79653?
CVE-2026-79653 is a medium vulnerability published on August 27, 2026. 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…
When was CVE-2026-79653 disclosed?
CVE-2026-79653 was first published in the National Vulnerability Database on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79653 actively exploited?
CVE-2026-79653 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.1% of all scored CVEs.
What is the CVSS score of CVE-2026-79653?
CVE-2026-79653 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-79653?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79653, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-79653

Explore →

Is Your Infrastructure Affected by CVE-2026-79653?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs