← Back
CVE-2026-39891
high
CVSS 8.8
Code Injection in praison (CVE-2026-39891)
Summary
code injection in praison (CVE-2026-39891). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `4.5.115` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-39891** has been found in praison.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade praison to **4.5.115** or later.
If unsure, ask your IT team or search "praison CVE-2026-39891" on the vendor's site.
CVE-2026-39891 (praison) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: `4.5.115` — 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
**arbitrary code execution** (CWE-94) exists in praison.
📍 Affected scope
praison — .
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **4.5.115**.
🛡️ 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 'praison' .` 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 'praison' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `praison` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade praison to 4.5.115ステージング環境で 4.5.115 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。