CVE-2026-89026

Issabel Framework Hard-coded JWT Key RCE via pbxapi/manager/originate

Published Sep 15, 2026 CVSS 4.0 · 9.3 Critical EPSS 2.7% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The Issabel Framework includes a hard‑coded HS256 JWT signing key that is identical across all installations prior to commit b97dbaf0b71c1c36f841e672b664afbeb02773bd. Attackers can generate a valid bearer token without any authentication and then call the manager originate endpoint with the System application parameter. Asterisk subsequently executes the supplied command string as the Asterisk user, granting the attacker arbitrary OS command execution on the host. Shadowserver observed active exploitation on 2026-09-09, confirming real‑world usage.

Affected Systems

The vulnerability affects all deployments of Issabel Foundation’s Issabel Framework that use the pbxapi index.php file prior to the fix incorporated in commit b97dbaf0b71c1c36f841e672b664afbeb02773bd. Any installation that has not applied this patch is vulnerable.

Risk and Exploitability

The CVSS score of 9.3 reflects a high severity, and the EPSS score of 3% indicates a nonzero exploitation probability. The vulnerability is not listed in the CISA KEV catalog. Attackers can remotely forge a bearer token without authentication and evolve it over HTTP or HTTPS to the pbxapi/manager/originate endpoint, causing Asterisk to run arbitrary OS commands as the Asterisk user. Because the flaw bypasses authentication, remote exploitation is straightforward.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the Issabel Framework patch corresponding to commit b97dbaf0b71c1c36f841e672b, which removes the hard‑coded signing key and requires proper token generation.
  • Configure the framework to enforce JWT validation on all API requests and replace the default signing key with a unique, secure key per deployment.
  • Limit unauthenticated access to the pbxapi/manager/originate endpoint by configuring firewall rules or access‑control policies so that only trusted hosts or internal networks may send originate commands.

Generated by OpenCVE AI on October 24, 2026 at 14:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Issabel Foundation
Issabel Foundation issabel Framework
Vendors & Products Issabel Foundation
Issabel Foundation issabel Framework
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Issabel Framework Hard-coded JWT Key RCE via pbxapi/manager/originate
Weaknesses CWE-321
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 17, 2026, 7:27 PM
Reserved
Sep 10, 2026, 4:23 PM
Status
Deferred
Published
Sep 15, 2026, 5:17 PM
Modified
Sep 24, 2026, 9:08 PM