Is CVE-2026-78299 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-78299 being exploited in the wild.

How severe is CVE-2026-78299?

Critical severity, with a CVSS score of 9.1, published 14 September 2026.

Which products and versions are affected?

Eclipse Embedded CDT 6.0 to 6.7.

Is there a fix for CVE-2026-78299?

A patch was published on 2026-09-14: Eclipse Embedded CDT 6.8.0, Eclipse IDE for Embedded C/C++ Developers 2026-09 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-78299 attacked?

It is attacked over the network.

Am I affected by CVE-2026-78299?

Check whether you run Eclipse Embedded CDT at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-78299: Eclipse Embedded CDT path traversal in CMSIS-Pack extraction

CVE-2026-78299 · Severity: critical · CVSS 9.1 · Published 2026-09-14

Eclipse Embedded CDT is an IDE plugin for embedded C/C++ development. A flaw in how it extracts CMSIS hardware definition packages allows attackers to write arbitrary files to any location on the developer's system—potentially including startup scripts or system binaries—if the developer installs a malicious or compromised pack from a vendor or network intermediary.

Vendors: Eclipse.

Quick answers

Is CVE-2026-78299 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-78299 being exploited in the wild.
How severe is CVE-2026-78299?: Critical severity, with a CVSS score of 9.1, published 14 September 2026.
Which products and versions are affected?: Eclipse Embedded CDT 6.0 to 6.7.
Is there a fix for CVE-2026-78299?: A patch was published on 2026-09-14: Eclipse Embedded CDT 6.8.0, Eclipse IDE for Embedded C/C++ Developers 2026-09 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-78299 attacked?: It is attacked over the network.
Am I affected by CVE-2026-78299?: Check whether you run Eclipse Embedded CDT at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a Zip Slip path traversal flaw (CWE-22) in the `InstallJob.unzip()` method. When extracting CMSIS-Pack `.pack` archive files, the code appends raw `ZipEntry.getName()` values directly to the destination folder path without canonicalizing or validating that the resulting path remains within the pack directory. An attacker-controlled archive can include entries with directory traversal sequences (e.g., `../../../../../../home/user/.bashrc`) that escape the intended extraction directory. The archive URL is fetched from the vendor's `.pdsc` manifest, making any compromised vendor, MITM on unencrypted HTTP pack URLs, or network attacker a potential source. The fix was released in version 6.8.0 and patches the containment check during extraction.

Affected products

Eclipse Embedded CDT 6.0 to 6.7

Timeline

2026-09-14: disclosed
2026-09-14: patched: Eclipse Embedded CDT 6.8.0, Eclipse IDE for Embedded C/C++ Developers 2026-09

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.