Issabel Framework
Approved changes feed: RSS · Atom
cpe:2.3:a:issabel_foundation:issabel_framework:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Issabel Foundation (3f5233e4-b6c9-5ab3-b112-de986e0f396b) |
|---|---|
| Product | Issabel Framework (5a9f8389-84c0-54b9-8b2d-6f2cb746b160) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-89026 |
vulnerable | 2026-09-16 04:34:09.460423 |
Issabel Framework Hard-coded JWT Key RCE via pbxapi/manager/originate
CRITICAL (9.8)
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.
Published: 2026-09-15T16:41:39.363Z
Updated: 2026-09-17T19:27:44.069Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.