CVE-2026-89026: Issabel Framework Hard-coded JWT Key RCE via pbxapi/manager/originate

Published Sep 15, 2026
·
Updated

The Issabel Framework, the web framework supporting Issabel PBX software, before commit b97dbaf contains a hard-coded HS256 JWT signing key in the pbxapi index.php file that is identical across every installation, allowing unauthenticated remote attackers to forge valid bearer tokens. Attackers can use the forged token to call the manager originate endpoint with the System application parameter, causing Asterisk to execute arbitrary OS commands as the Asterisk user. Exploitation evidence was first observed by the Shadowserver Foundation on 2026-09-09.

Affected Software

2 affected components
Issabel Issabel Framework<b97dbaf
pbxapi/manager/originate

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Issabel Framework (pbxapi/index.php) to a version that resolves this vulnerability.

    Patch commit b97dbaf
  2. Compensating control

    Restrict network access to the Asterisk manager originate endpoint (pbxapi/manager/originate) so unauthenticated remote attackers cannot reach it.

Event History

Sep 15, 2026
CVE Published
via MITRE·04:41 PM
Data Sourced
via MITRE·04:41 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

Any unauthenticated remote attacker able to reach the affected Issabel Framework pbxapi endpoint can forge bearer tokens because the HS256 JWT signing key is identical across installations.

2

What access or interaction does exploitation require?

Exploitation requires network access to the affected endpoint only. It does not require prior authentication, privileges, or user interaction.

3

What is the impact of a successful attack?

An attacker can invoke the manager originate endpoint with the System application parameter, causing Asterisk to execute arbitrary operating-system commands as the Asterisk user.

4

How can I determine whether my installation is affected?

Installations whose Issabel Framework version predates commit b97dbaf are affected. Review the framework source or deployed version history to determine whether commit b97dbaf0b71c1c36f841e672b664afbeb02773bd is present.

5

Is exploitation occurring in the wild?

Yes. The Shadowserver Foundation first observed exploitation evidence on 2026-09-09.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203