Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-89026: Issabel Framework Hard-Coded JWT Key Remote Code Execution

Published Sep 15, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS9.3Critical · v4
EPSS2.7%86th percentile
CISA KEVNoNot listed
In the wildReported22 exploitation records in Mallory
IdentifiersCVE-2026-89026CWE-321 · Use of Hard-coded Cryptographic Key

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
CVE-2026-89026This three-file repository contains an MIT license, usage documentation, and a standalone Python 3 exploit script for CVE-2026-89026. The script uses only the standard library and implements HTTP/HTTPS session handling, cookies, redirects, compression decoding, TLS verification bypass, API-prefix handling, and HS256 JWT generation. It abuses the pre-patch, installation-invariant pbxapi JWT key to mint a Bearer token identifying as admin. In test mode, it compares unauthenticated and forged-token access to the pbxapi root without sending an originate request. Command mode sends an authenticated request to /pbxapi/manager/originate configured with Asterisk Application=System and a caller-supplied command. Read mode uses that execution primitive to copy a selected readable file to the web root and then retrieve it, since AMI does not return command stdout in the originate response. The documented patch replaces the static key with a secret loaded from /etc/issabel.conf. This is a functional unauthenticated remote code execution exploit rather than solely a detection script; its command payload is operator-supplied but basic.cflowsec · Disclosed Sep 16, 2026 · python · markdown · web · networkOperationalCVE-2026-89026This two-file repository contains a Python 3 PoC/scanner and a README. The main entry point, `CVE-2026-89026.py`, is an interactive command-line utility that maintains cookies, handles redirects and compressed HTTP responses, optionally disables TLS certificate verification, and normalizes a supplied Issabel target URL. It probes several PBXAPI URL variants, creates HS256 JWTs with a hard-coded signing key, and uses the forged bearer token to test whether PBXAPI authentication is bypassed. Its exploit path targets `GET /pbxapi/manager/originate` and requests Asterisk `Application=System`, yielding arbitrary command execution as the Asterisk service user when accepted. The menu also supports a single URL or sequential scanning of a user-provided IP:port/URL list. The README describes the detection mode as non-executing, but the included Python code is a functional exploit because it contains an optional command-execution path. No established exploit framework is used.AranFarzami · Disclosed Sep 21, 2026 · python · markdown · network · webOperational
FAQ

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.
Activity feed

Recent activity

43 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
nuclei templates pull requestsNews · Oct 16, 2026Add CVE-2026-89026 Issabel PBX API JWT key detection by alex700 · Pull Request #17437 · projectdiscovery/nuclei-templatesAn Issabel JWT key vulnerability referenced in a Nuclei detection-template contribution. The content does not describe the underlying flaw, security impact, or affected versions. Local testing commands do not establish exploitation or active scanning in the wild.Read more ↗the hacker newsNews · Sep 16, 2026Attackers Exploit Issabel Framework Flaw Enabling Unauthenticated OS Command ExecutionA critical (CVSS v3.1 9.8; CVSS v4.0 9.3) unauthenticated remote OS-command-execution vulnerability in Issabel Framework. A hard-coded HS256 JWT signing key permits attackers to forge bearer tokens and invoke the /pbxapi/manager/originate endpoint with Asterisk's System application, executing commands as the Asterisk user.Read more ↗cyber security newsNews · Sep 16, 2026Critical Issabel PBX Command Execution Vulnerability Exploited in the WildA critical unauthenticated remote OS-command-execution vulnerability in the Issabel Framework caused by a hard-coded HS256 JWT signing key in pbxapi/index.php. Attackers can forge bearer tokens and abuse the pbxapi/manager/originate endpoint to invoke Asterisk's System application as the Asterisk service account.Read more ↗cryptika blogNews · Sep 16, 2026Critical Issabel PBX Command Execution Vulnerability Exploited in the Wild | Cryptika CybersecurityA critical unauthenticated remote OS command-execution vulnerability in the Issabel Framework caused by a hard-coded HS256 JWT signing key in pbxapi/index.php. Attackers can forge bearer tokens and abuse the pbxapi/manager/originate endpoint to invoke Asterisk's System application and execute commands as the Asterisk service account.Read more ↗
+3 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity36Community discussion across Reddit, Mastodon, and other social sources.