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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.6
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Akamai CLI version before 2.0.6 Victim must install or update a malicious package
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Akamai CLI version before 2.0.6 Victim must install or update a malicious packageUpgrade to a fixed version: 2.0.6.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Akamai Akamai CLI
fixed in 2.0.6
Evidence 9
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Other links · 6
- Patch
- Patch
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-82518
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-82518?
Akamai CLI: before 2.0.6.Source: cve.now feed data
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: vulncheck.com
How do I fix CVE-2026-82518?
Upgrade Akamai CLI to version 2.0.6 or later, which contains the fix.Source: vulncheck.com