CVE-2026-89026

validatedZero produced an exploit or a check.

GHSA-mmrg-2gjg-78x9 ↗EUVD-2026-78838 ↗

check availableZero validated a working check for it.proven exploitableZero has validated a full working exploit.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+5.8dkevAttacks confirmed in the real world.0d
Issabel Foundation Issabel Framework
fixed in b97dbaf0b71c1c36f841e672b664afbeb02773bd
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-508, permanent identifier
+18dTTV
34mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal +0dcve.org publication+0.7dkev+1.0dpublic poc+6.5dcheck + exploit+19d
+5d
+10d
+15d
+20d

description

Issabel Framework installations using code earlier than commit b97dbaf contain a shared JWT signing key. An unauthenticated remote attacker can forge bearer tokens and invoke affected PBX functionality to run operating-system commands as the Asterisk user.

mitigation

Update Issabel Framework to a revision that includes commit b97dbaf. Until updates are complete, restrict untrusted network access to the PBX API and related management interfaces.

fixed in b97dbaf0b71c1c36f841e672b664afbeb02773bd

check
available
exploit
yes
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.69%51st percentile
agent run time
34m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-15 16:41Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+5.8d
Δ to kevAttacks confirmed in the real world.
0d

outcome

Differential: the exploit fired on the vulnerable build and stayed silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-15
    vulncheck_kev: trigger signal, started the run
  2. 2026-09-15 00:00Z
  3. 2026-09-15 16:41Z
  4. 2026-10-04 04:20Z

this entry in the feed

GET /api/v1/feed/CVE-2026-89026

{
  "etk_id": "ETK-2026-508",
  "cve_id": "CVE-2026-89026",
  "display_id": "CVE-2026-89026",
  "ghsa_id": "GHSA-mmrg-2gjg-78x9",
  "euvd_id": "EUVD-2026-78838",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hard-coded JWT signing key in Issabel Framework",
  "summary": "Issabel Framework installations using code earlier than commit b97dbaf contain a shared JWT signing key. An unauthenticated remote attacker can forge bearer tokens and invoke affected PBX functionality to run operating-system commands as the Asterisk user.",
  "mitigation": "Update Issabel Framework to a revision that includes commit b97dbaf. Until updates are complete, restrict untrusted network access to the PBX API and related management interfaces.",
  "vendor": "Issabel Foundation",
  "product": "Issabel Framework",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < b97dbaf0b71c1c36f841e672b664afbeb02773bd"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "b97dbaf0b71c1c36f841e672b664afbeb02773bd"
      ],
      "package_name": "Issabel Framework",
      "purl": null
    }
  ],
  "cwes": [
    321
  ],
  "cvss_score": 9.8,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0069,
  "epss_percentile": 0.5178,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": true,
  "pipeline_minutes": 34.27681666666667,
  "t0_at": "2026-09-15T16:41:39.363000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-03T23:07:36.393360+00:00",
      "days": 18.268021184722222,
      "is_lower_bound": false,
      "measured_at": "2026-09-15T16:41:39.363000+00:00",
      "url": null
    },
    "exploit": {
      "at": "2026-10-03T23:07:36.393360+00:00",
      "days": 18.268021184722222,
      "is_lower_bound": false,
      "measured_at": "2026-09-15T16:41:39.363000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-09-15T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-15T16:41:39.363000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-89026"
    },
    "public_poc": {
      "at": "2026-09-21T10:59:47+00:00",
      "days": 5.762588391203704,
      "is_lower_bound": false,
      "measured_at": "2026-09-15T16:41:39.363000+00:00",
      "url": "https://github.com/AranFarzami/CVE-2026-89026"
    },
    "trigger_signal": {
      "at": "2026-09-15T00:00:00+00:00",
      "days": -0.6955944791666666,
      "is_lower_bound": false,
      "measured_at": "2026-09-15T16:41:39.363000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-89026"
    }
  }
}

published 2026-10-03 22:33Z
last change 2026-10-20 23:23Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.