CVE-2026-44888

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
23.4%
KEV
Not listed

Published

May 27, 2026

Last Modified

May 29, 2026

Advisory Details (1)

Auto-updated Jun 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Unauthenticated RCE via Python Config File Injection in SaveConfigFile() (Interger) · Advisory · leiweibau/Pi.Alert · GitHub

https://github.com/leiweibau/Pi.Alert/security/advisories/GHSA-xg85-f8qw-7c5f

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 70× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 188 total refreshes for this CVE.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-13 22:30 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 22:57 UTCEG score recompute
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-08 22:54 UTCEG score recompute
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-02 23:43 UTCEG score recompute
  18. 2026-07-01 21:20 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 14:02 UTCEG score recompute
  21. 2026-07-01 09:16 UTCEG score recompute
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 09:06 UTCEG score recompute
  24. 2026-06-30 02:36 UTCEG score recompute
  25. 2026-06-29 19:46 UTCEG score recompute
Show 75 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 13:56 UTCEG score recompute
  4. 2026-06-28 23:13 UTCEG score recompute
  5. 2026-06-28 18:51 UTCEG score recompute
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 13:30 UTCEG score recompute
  8. 2026-06-28 09:08 UTCEG score recompute
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-28 04:48 UTCEG score recompute
  12. 2026-06-28 00:09 UTCEG score recompute
  13. 2026-06-27 19:48 UTCEG score recompute
  14. 2026-06-27 15:22 UTCEG score recompute
  15. 2026-06-27 11:01 UTCEG score recompute
  16. 2026-06-27 06:33 UTCEG score recompute
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-27 01:56 UTCEG score recompute
  19. 2026-06-26 21:19 UTCEG score recompute
  20. 2026-06-26 16:59 UTCEG score recompute
  21. 2026-06-26 02:14 UTCEG score recompute
  22. 2026-06-25 21:53 UTCEG score recompute
  23. 2026-06-25 17:32 UTCEG score recompute
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
  26. 2026-06-25 13:11 UTCEG score recompute
  27. 2026-06-25 08:49 UTCEG score recompute
  28. 2026-06-24 23:44 UTCEG score recompute
  29. 2026-06-24 14:05 UTCEPSS rescore
  30. 2026-06-23 21:33 UTCEPSS rescore
  31. 2026-06-22 14:25 UTCEPSS rescore
  32. 2026-06-22 14:25 UTCEPSS rescore
  33. 2026-06-21 14:56 UTCEPSS rescore
  34. 2026-06-21 14:56 UTCEPSS rescore
  35. 2026-06-21 01:59 UTCEPSS rescore
  36. 2026-06-19 19:25 UTCEPSS rescore
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-18 17:52 UTCEPSS rescore
  39. 2026-06-18 03:38 UTCEG score recompute
  40. 2026-06-17 22:52 UTCEG score recompute
  41. 2026-06-17 18:30 UTCEG score recompute
  42. 2026-06-17 17:53 UTCEPSS rescore
  43. 2026-06-17 13:59 UTCEG score recompute
  44. 2026-06-17 09:38 UTCEG score recompute
  45. 2026-06-17 04:56 UTCEG score recompute
  46. 2026-06-17 00:35 UTCEG score recompute
  47. 2026-06-16 20:14 UTCEG score recompute
  48. 2026-06-16 17:52 UTCEPSS rescore
  49. 2026-06-16 15:54 UTCEG score recompute
  50. 2026-06-16 11:16 UTCEG score recompute
  51. 2026-06-16 06:56 UTCEG score recompute
  52. 2026-06-16 02:35 UTCEG score recompute
  53. 2026-06-15 22:14 UTCEG score recompute
  54. 2026-06-15 17:49 UTCEPSS rescore
  55. 2026-06-15 13:17 UTCEG score recompute
  56. 2026-06-15 06:33 UTCEG score recompute
  57. 2026-06-15 02:11 UTCEG score recompute
  58. 2026-06-14 21:50 UTCEG score recompute
  59. 2026-06-14 17:29 UTCEG score recompute
  60. 2026-06-14 13:09 UTCEG score recompute
  61. 2026-06-14 08:47 UTCEG score recompute
  62. 2026-06-14 04:27 UTCEG score recompute
  63. 2026-06-14 00:02 UTCEG score recompute
  64. 2026-06-13 23:00 UTCEPSS rescore
  65. 2026-06-13 19:40 UTCEG score recompute
  66. 2026-06-13 12:02 UTCEG score recompute
  67. 2026-06-13 07:41 UTCEG score recompute
  68. 2026-06-13 03:19 UTCEG score recompute
  69. 2026-06-12 23:12 UTCEPSS rescore
  70. 2026-06-12 23:12 UTCEPSS rescore
  71. 2026-06-12 22:59 UTCEG score recompute
  72. 2026-06-12 18:37 UTCEG score recompute
  73. 2026-06-12 14:16 UTCEG score recompute
  74. 2026-06-12 09:56 UTCEG score recompute
  75. 2026-06-12 05:34 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44888?
CVE-2026-44888 is a critical vulnerability published on May 27, 2026. 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…
When was CVE-2026-44888 disclosed?
CVE-2026-44888 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44888 actively exploited?
CVE-2026-44888 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44888?
CVE-2026-44888 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-44888?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44888, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-44888

Explore →

Is Your Infrastructure Affected by CVE-2026-44888?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.