CVE-2026-103055

waiting for further signalsZero needs more public information before it can validate it.

GHSA-4m55-xhcm-wjcr ↗EUVD-2026-89539 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
beenuar AiSOC >= 7.5.0, <= 11.2.0
fixed in 12.0.0
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-58, permanent identifier
4d 07h 25msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+405h08m
0
+2h
+4h
+6h
+8h
+10h

description

AiSOC versions 7.5.0 through versions before 12.0.0 use a built-in JWT verification value for realtime WebSocket and SSE endpoints if AISOC_REALTIME_JWT_SECRET is not configured. An unauthenticated remote attacker could create accepted subscription credentials for another tenant and view that tenant's realtime alerts, cases, events, or graph updates.

mitigation

Upgrade AiSOC to version 12.0.0 or later. Set AISOC_REALTIME_JWT_SECRET to a strong, deployment-specific secret, especially until all instances are upgraded.

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.
0.41%33rd percentile
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 00:19Z
Δ 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-30 00:19Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-58",
  "cve_id": "CVE-2026-103055",
  "display_id": "CVE-2026-103055",
  "ghsa_id": "GHSA-4m55-xhcm-wjcr",
  "euvd_id": "EUVD-2026-89539",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hard-coded JWT verification key in AiSOC realtime services",
  "summary": "AiSOC versions 7.5.0 through versions before 12.0.0 use a built-in JWT verification value for realtime WebSocket and SSE endpoints if AISOC_REALTIME_JWT_SECRET is not configured. An unauthenticated remote attacker could create accepted subscription credentials for another tenant and view that tenant's realtime alerts, cases, events, or graph updates.",
  "mitigation": "Upgrade AiSOC to version 12.0.0 or later. Set AISOC_REALTIME_JWT_SECRET to a strong, deployment-specific secret, especially until all instances are upgraded.",
  "vendor": "beenuar",
  "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": [
    321
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0041,
  "epss_percentile": 0.3332,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 21.70848585,
  "t0_at": "2026-09-30T00:19:11.252000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T00:19:11.252000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T00:19:11.252000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103055"
    }
  }
}

published 2026-09-30 01:07Z
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.