Path Traversal in apm-cli (CVE-2026-46383)
Summary
Path traversal in apm-cli (CVE-2026-46383). Data can be tampered with by attackers. Exploitable via main. Mitigation: upgrade to 0.13.0 or later.
Original description
The description as published by the source.
Microsoft APM is an open-source, community-driven dependency manager for AI agents. Prior to 0.13.0, Microsoft APM contains a Windows-specific archive extraction boundary failure in the legacy-bundle probe used by apm install on supported Python 3.10 and 3.11 runtimes. When apm install is given a local .tar.gz that is not recognized as a plugin-format bundle, APM probes whether it is a legacy --format apm bundle. On Python versions earlier than 3.12, that probe extracts untrusted tar members with raw tar.extractall() without rejecting Windows absolute member names such as D:/.... This vulnerability is fixed in 0.13.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46383 has been found in apm-cli.
Attackers can target a specific entry point like main over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.5/10.
What to do: upgrade apm-cli to 0.13.0 or later.
If unsure, ask your IT team or search "apm-cli CVE-2026-46383" on the vendor's site.
CVE-2026-46383 (apm-cli) — CWE-22 / CVSS v3 5.5
Attack vector: local / unauthenticated
Attack surface: main / apm.lock.yaml / plugin_parser.py / tarfile
Patched: 0.13.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in apm-cli. Attackers reach the vulnerable code path via main without authentication.
Check the vendor advisory for the affected versions of apm-cli. Attack surface: main / apm.lock.yaml / plugin_parser.py / tarfile.
Severity: Medium (CVSS 5.5/10). Data can be tampered with by attackers.
Update to 0.13.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'apm-cli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'apm-cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
apm-cliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade apm-cli to 0.13.0ステージング環境で 0.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com