CVE-2026-89026: Issabel Framework Hard-Coded JWT Key Remote Code Execution
CVE-2026-89026 is a critical vulnerability in the Issabel Framework supporting Issabel PBX deployments. A hard-coded HS256 JWT signing key shared across affected installations allows unauthenticated remote attackers to forge valid bearer tokens and bypass API authentication. Attackers can then invoke the PBX API manager originate endpoint with Asterisk's System application parameter, resulting in arbitrary operating-system command execution as the Asterisk service account. Shadowserver Foundation first observed exploitation evidence on September 9, 2026.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises the confidentiality, integrity, and availability of the PBX within the permissions available to the Asterisk account. Potential consequences include theft of call records and PBX configuration data, modification of dial plans, abuse of telephony resources, malware deployment, persistence, and disruption of communications. Further network movement depends on the compromised server's connectivity and accessible credentials. The vulnerability does not inherently provide root privileges.
Mitigation
If you can’t patch tonight, do this now.
Restrict access to PBX API endpoints and Asterisk management services using firewall rules, trusted-source allowlists, VPN access, and network segmentation. Avoid exposing these interfaces directly to the internet. Monitor web-server, Issabel, Asterisk, and endpoint logs for suspicious bearer-token use, unusual originate requests, System application invocations, unexpected shell commands, and anomalous outbound connections. These measures reduce exposure but do not replace patching.
Remediation
Patch, then assume compromise.
Update Issabel Framework to a revision containing security commit b97dbaf0b71c1c36f841e672b664afbeb02773bd or a later release incorporating the fix. The patch replaces the universal hard-coded signing key with a configuration-backed key. Verify that the patched code is active in production and the shared vulnerable signing key is no longer used. Investigate previously exposed systems for compromise; if compromise is identified, rotate affected credentials, perform forensic review, and rebuild systems where necessary.
Exploits
2 exploits validated by Mallory's analysis.
References
Frequently asked questions
- Is CVE-2026-89026 exploited in the wild?
- Yes. As of Nov 10, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-89026?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-89026, the earliest disclosed Sep 16, 2026.
- Is there a patch for CVE-2026-89026?
- Update Issabel Framework to a revision containing security commit b97dbaf0b71c1c36f841e672b664afbeb02773bd or a later release incorporating the fix. The patch replaces the universal hard-coded signing key with a configuration-backed key.
- How severe is CVE-2026-89026?
- CVE-2026-89026 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 2.7% (86th percentile) as of Nov 10, 2026.
Recent activity
43 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.