← Back
CVE-2026-55579
critical
CVSS 9.8
Vulnerability in pheditor/pheditor (CVE-2026-55579)
Summary
vulnerability in pheditor/pheditor (CVE-2026-55579). Successful exploitation can lead to full system takeover. Exploitable via ``admin``. Mitigation: upgrade to `2.0.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55579** has been found in pheditor/pheditor.
Attackers can target a specific entry point like ``admin`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade pheditor/pheditor to **2.0.6** or later.
If unsure, ask your IT team or search "pheditor/pheditor CVE-2026-55579" on the vendor's site.
CVE-2026-55579 (pheditor/pheditor) — CWE-798 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `admin` / `e538f05b6faec99e5b23726bc9c17d6b57774297` / `main` / `PASSWORD_BCRYPT`
Patched: `2.0.6` — 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
**A vulnerability** (CWE-798) exists in pheditor/pheditor. Attackers reach the vulnerable code path via ``admin`` without authentication.
📍 Affected scope
pheditor/pheditor — . Attack surface: `admin` / `e538f05b6faec99e5b23726bc9c17d6b57774297` / `main` / `PASSWORD_BCRYPT`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.0.6**.
🛡️ 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 'pheditor/pheditor' .` 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 'pheditor/pheditor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pheditor/pheditor` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pheditor/pheditor to 2.0.6ステージング環境で 2.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
pheditor/pheditor
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.6"}]}]