← Back
CVE-2026-44334
high
CVSS 8.4
Code Injection in praison (CVE-2026-44334)
Summary
code injection in praison (CVE-2026-44334). Successful exploitation can lead to full system takeover. Exploitable via `POST /v1/recipes/run`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44334** has been found in praison.
Attackers can target a specific entry point like `POST /v1/recipes/run` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "praison CVE-2026-44334" on the vendor's site.
CVE-2026-44334 (praison) — CWE-94 / CVSS v3 8.4
Attack vector: local / unauthenticated / no user interaction
Attack surface: POST /v1/recipes/run
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. Attackers reach the vulnerable code path via `POST /v1/recipes/run` without authentication.
📍 Affected scope
praison — . Attack surface: POST /v1/recipes/run.
🔥 Severity
Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 `POST /v1/recipes/run` requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /v1/recipes/run' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /v1/recipes/run` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /v1/recipes/run on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- exploit [email protected]