IPS Signature Sep 16, 2026

GajIPS - IPS Signature Update — GS EXPLOIT: Issabel PBX unauthenticated remote code execution, CVE-2026-89026

Severity: CRITICAL · Priority: P1 — active exploitation, escalate on hit

This rule raises an alert when an attacker attempts to exploit a critical flaw in Issabel, an open-source phone-system (PBX) platform built on Asterisk and widely used for business telephony. The affected software shipped with a secret signing key built into its code that was identical on every installation. Because that key was public knowledge once discovered, an attacker needs no username, password, or prior access — they can forge a valid-looking access token and send a single request to the phone system's management interface that instructs it to run operating-system commands on the server. This rule watches for that command-execution request.

A hit here is a top-urgency signal. The flaw is rated critical (9.3), and security researchers confirmed real-world exploitation beginning 9 September 2026, with internet-exposed Issabel systems being actively targeted. A successful attack runs commands on the phone server and can lead to malware installation, theft of call records and configuration, tampering with call routing, toll fraud, and a foothold to move deeper into the network. Treat an alert as an active, serious intrusion attempt against the phone system.

On a hit: identify whether the targeted host is an Issabel PBX and whether its Framework component has been updated to a fixed build (the corrected version released after the flaw was patched); anything earlier is vulnerable. If it is unpatched and internet-exposed, assume potential compromise and escalate to incident response immediately — review web-server, Issabel, and Asterisk logs for unusual access-token activity and unexpected "originate" requests, look for unfamiliar processes or outbound connections from the server, and check for tampering with dial plans or new persistence. Because the underlying weakness is a shared secret key, updating to the fixed version is the definitive fix; systems should not be considered safe until patched.

Reference: https://www.cve.org/CVERecord?id=CVE-2026-89026
See the latest threat intelligence