Code Injection in Pi.Alert (CVE-2026-44887)
Summary
Code injection in Pi.Alert (CVE-2026-44887). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2026-05-07 or later.
Original description
The description as published by the source.
Pi.Alert is a WIFI / LAN intruder detector with web service monitoring. Prior to 2026-05-07, Pi.Alert's web-based configuration editor allows arbitrary Python code to be injected into pialert.conf. Since the background scan daemon loads this file via Python's exec(), injected code executes as the daemon process. With web protection disabled (the default configuration), no authentication is required, making this an unauthenticated Remote Code Execution vulnerability. This vulnerability is fixed in 2026-05-07.
Source: NIST National Vulnerability Database 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-44887 has been found in Pi.Alert.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade Pi.Alert to 2026-05-07 or later.
If unsure, ask your IT team or search "Pi.Alert CVE-2026-44887" on the vendor's site.
CVE-2026-44887 (Pi.Alert) — CWE-94 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2026-05-07 — 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.
Arbitrary code execution (CWE-94) exists in Pi.Alert.
Check the vendor advisory for the affected versions of Pi.Alert.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 2026-05-07.
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 'Pi.Alert' . 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 'Pi.Alert' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Pi.Alertを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Pi.Alert to 2026-05-07ステージング環境で 2026-05-07 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov