No impact incident

Pulseway: PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619): Pulseway Status

Current status of Pulseway: Operational — live Pulseway status

Timeline

1. Oct 22, 2026, 13:19 UTC
   investigating
   Two critical vulnerabilities in PHP that allow unauthenticated remote code execution have been identified. The Pulseway security teams are assessing all systems and products and applying fixes as they become available.
2. Oct 23, 2026, 20:27 UTC
   identified
   Pulseway is aware of two critical vulnerabilities in PHP: CVE-2026-109618 and CVE-2026-109619. CVE-2026-109618 involves a remote code execution vulnerability where handling out-of-memory errors via longjmp() leaves request memory uninitialized due to improper control flow management, potentially allowing attackers to achieve remote code execution using out-of-memory (OOM) triggers. CVE-2026-109619 describes a remote code execution vulnerability where longjmp() fatal error handling leaves global memory pointing to freed memory regions. These regions can later be accessed during subsequent requests, potentially enabling arbitrary code execution. Pulseway has completed an evaluation of its product portfolio regarding these vulnerabilities. As our investigation and remediation efforts continue, we will keep the following list updated with the latest information. Here is what each status means: Fully Patched: The fix has been applied. Compensating Controls: The product is impacted, protective controls are in place, and we are working to remediate. Unaffected: The product is not affected by these vulnerabilities. Product Status: Pulseway - Compensating Controls Software Catalog - Unaffected

Updates as published by Pulseway (original).