← Back
CVE-2026-46383
medium
CVSS 5.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**Path traversal** (CWE-22) exists in apm-cli. Attackers reach the vulnerable code path via ``main`` without authentication.
📍 Affected scope
apm-cli — . Attack surface: `main` / `apm.lock.yaml` / `plugin_parser.py` / `tarfile`.
🔥 Severity
Severity: Medium (CVSS 5.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **0.13.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade apm-cli to 0.13.0ステージング環境で 0.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
apm-cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.13.0"}]}]
PyPI
apm-cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.13.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-46383
- package https://github.com/microsoft/apm
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://github.com/microsoft/apm/commit/77d1dda8303c8d7ccb6148788a6274fdece98499
- web https://github.com/microsoft/apm/releases/tag/v0.13.0
- web https://github.com/advisories/GHSA-mq5j-pw29-jcv3