Koffei

CVE-2026-89026

🟠 Medium

Issabel Framework (open-source PBX based on Asterisk) · All versions prior to commit b97dbaf0b71c1c36f841e672b664afbeb02773bd

CVSS (Koffei note)
9.8
CVSS (v4.0, CVE List)
9.3
EPSS (2026-11-18)
2.699%
86.22th percentile

Exploitation

Yes, exploitation documented by Shadowserver since 09/09/2026 (not yet in CISA KEV) Re-tested 19/11/2026 (60-day rule): the most recent dated exploitation on this row is 09/09/2026, 71 days old, outside the 60-day window, and no newer dated exploitation was read, so 🔴 → 🟠.

Timeline

  1. 15/09/2026CVE record published (CVE List)
  2. 17/09/2026Issabel PBX Auth Bypass

Risk

9.8 Critical (v3.1) / 9.3 (v4.0) — AV:N/AC:L/PR:N/UI:N, EPSS 0.5% (hard-coded HS256 JWT signing key, identical across all installations → RCE via token forgery)

Fix

Patch available via the referenced commit — verify the deployed version

Official 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.

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

CWE-321