# CVE-2026-44888: Unauthenticated RCE via Python Config File Injection in SaveConfigFile() (Interger)

> Unauthenticated attackers can inject Python code via config values to achieve remote code execution on Pi.Alert installations.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-xg85-f8qw-7c5f

## What is CVE-2026-44888?

CVE-2026-44888 is a critical code injection vulnerability in leiweibau Pi.Alert, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pi.Alert is a WIFI / LAN intruder detector with web service monitoring. Prior to 2026-05-07, Pi.Alert's SaveConfigFile() endpoint writes user-supplied numeric config values (e.g., SMTP_PORT) directly into
pialert.conf without validation. Since pialert.conf is loaded via Python's exec() every 3–5 minutes by the
background cron process, an attacker can inject arbitrary Python code and achieve unauthenticated OS-level RCE. On
default installations (PIALERT_WEB_PROTECTION = False), no credentials are required. This vulnerability is fixed in 2026-05-07.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-44888?


## How do I fix CVE-2026-44888?

No fix has been published for CVE-2026-44888 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44888 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44888 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44888 and fix it if it is affected.

What it is: CVE-2026-44888 is a critical code injection vulnerability in leiweibau Pi.Alert, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44888 exists.

Affected product: leiweibau Pi.Alert. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44888/ (Markdown: https://insights.sbomify.com/CVE-2026-44888/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44888
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44888
- OSV: https://osv.dev/vulnerability/CVE-2026-44888

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44888/
Summaries are generated and may contain mistakes; the official description above is the record.