{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44888 exists.","fix":"No fix has been published for CVE-2026-44888 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-44888 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44888 exists.\n\nAffected product: leiweibau Pi.Alert. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44888/ (Markdown: https://insights.sbomify.com/CVE-2026-44888/index.md)","id":"CVE-2026-44888","markdown":"https://insights.sbomify.com/CVE-2026-44888/index.md","name":"CVE-2026-44888","record":{"aliases":["GHSA-xg85-f8qw-7c5f"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Pi.Alert network monitor","requires_auth":"none","summary":"Unauthenticated attackers can inject Python code via config values to achieve remote code execution on Pi.Alert installations.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"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\npialert.conf without validation. Since pialert.conf is loaded via Python's exec() every 3–5 minutes by the\nbackground cron process, an attacker can inject arbitrary Python code and achieve unauthenticated OS-level RCE. On\ndefault installations (PIALERT_WEB_PROTECTION = False), no credentials are required. This vulnerability is fixed in 2026-05-07.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Unauthenticated RCE via Python Config File Injection in SaveConfigFile() (Interger)","id":"CVE-2026-44888","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"WebOb: Location header normalization during redirect leads to open redirect","id":"CVE-2026-44889"},"packages":[],"prev":{"headline":"Unauthenticated RCE via Python Config File Injection in SaveConfigFile() (Path)","id":"CVE-2026-44887"},"products":["Pi.Alert"],"published":"2026-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["leiweibau"]},"summary":"Unauthenticated attackers can inject Python code via config values to achieve remote code execution on Pi.Alert installations.","url":"https://insights.sbomify.com/CVE-2026-44888/"}