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

> Unauthenticated attackers can inject Python code into the configuration file, leading to remote code execution on the Pi.Alert network monitoring system.

- **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-r59g-5wf9-f7vv

## What is CVE-2026-44887?

CVE-2026-44887 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 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.

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

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


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

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

## Is CVE-2026-44887 being exploited?

There is no known exploitation of CVE-2026-44887 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44887 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: There is no known exploitation of CVE-2026-44887 in the wild and no public exploit code.

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-44887/ (Markdown: https://insights.sbomify.com/CVE-2026-44887/index.md)
```

## Sources

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

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