Is CVE-2026-82518 exploited in the wild?

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

How severe is CVE-2026-82518?

Medium severity, with a CVSS score of 6.5, published 10 November 2026.

Is there a fix for CVE-2026-82518?

Yes: fixed in 2.0.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-82518 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-82518?

Check whether you run Akamai CLI 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-82518: Akamai CLI path traversal in package installation

CVE-2026-82518 · Severity: medium · CVSS 6.5 · Published 2026-11-10

Akamai CLI is a command-line management tool that installs packages containing command extensions. A path traversal vulnerability in how it processes package metadata allows attackers to place malicious executables outside the intended installation directory, potentially overwriting legitimate programs on the user's system. An attacker who tricks a user into installing a malicious package can persistently compromise the system with code that survives uninstallation.

Vendors: Akamai.

Quick answers

Is CVE-2026-82518 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82518 being exploited in the wild.
How severe is CVE-2026-82518?: Medium severity, with a CVSS score of 6.5, published 10 November 2026.
Which products and versions are affected?: Akamai CLI before 2.0.6.
Is there a fix for CVE-2026-82518?: Yes: fixed in 2.0.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-82518 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-82518?: Check whether you run Akamai CLI 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.

How to fix

Fixed in: 2.0.6

Technical details

The vulnerability exists in the package installation flow where the commands[].name value from cli.json is accepted without validating for path traversal sequences (../, absolute paths, or path separators). This name parameter is later used directly as a filesystem path component when writing installed command binaries, allowing an attacker to write files outside the package directory. The flaw occurs during Akamai CLI's own installation logic, before the user ever executes the installed command, driven purely by metadata in the package.

Affected products

Akamai CLI before 2.0.6

Timeline

2026-11-10: disclosed
2026-11-10: advisory

References

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