ETK-2026-88Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.
no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
other AiSOC >= 7.5.0, <= 11.2.0
fixed in 12.0.0
CWE-287 Improper Authentication
ETK-2026-88, no cve assigned
3d 01h 27msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+19d
0
+5d
+10d
+15d

description

AiSOC realtime WebSocket and SSE authentication can use a repository-exposed fallback signing key in affected deployments. An unauthenticated attacker who can reach the realtime endpoint may obtain subscriptions for a tenant they choose. The issue depends on the realtime container lacking a configured production environment and dedicated realtime JWT secret.

mitigation

Upgrade aisoc to version 12.0.0 or later. Until upgraded, configure the realtime container with a unique AISOC_REALTIME_JWT_SECRET and a production environment value, and restrict public access to its realtime endpoints.

fixed in 12.0.0

check
no
exploit
no
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.
–
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.
–
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-09-29 03:04Z

this entry in the feed

GET /api/v1/feed/ETK-2026-88

{
  "etk_id": "ETK-2026-88",
  "cve_id": null,
  "display_id": "ETK-2026-88",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Hard-coded realtime authentication key in aisoc",
  "summary": "AiSOC realtime WebSocket and SSE authentication can use a repository-exposed fallback signing key in affected deployments. An unauthenticated attacker who can reach the realtime endpoint may obtain subscriptions for a tenant they choose. The issue depends on the realtime container lacking a configured production environment and dedicated realtime JWT secret.",
  "mitigation": "Upgrade aisoc to version 12.0.0 or later. Until upgraded, configure the realtime container with a unique AISOC_REALTIME_JWT_SECRET and a production environment value, and restrict public access to its realtime endpoints.",
  "vendor": "other",
  "product": "AiSOC",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.5.0, <= 11.2.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "12.0.0"
      ],
      "package_name": "aisoc",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.74630445,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-09-29T03:04:12+00:00",
      "days": -22.074014768125,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:50:46.898506+00:00",
      "url": "https://github.com/beenuar/AiSOC/security/advisories/GHSA-4m55-xhcm-wjcr"
    }
  }
}

published 2026-09-30 06:15Z
last change 2026-10-21 04:45Z

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.