CVE-2026-44888
Unauthenticated RCE in Pi.Alert via SaveConfigFile() allowing code execution.
Is CVE-2026-44888 being exploited?
Not confirmed. CVE-2026-44888 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-44888?
CVE-2026-44888 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44888?
Yes. A fix has been recorded for CVE-2026-44888. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44888 affect?
CVE-2026-44888 affects Pi.Alert intruder detector devices, Pi.Alert web service, pialert.conf loader. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44888?
Apply official patch and enable protections immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
OS-level RCE via crafted config injected into pialert.conf loaded by exec(); unauthenticated on defaults.
Patch when possible
- affected< 2026-05-07
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.