# CVE-2026-103055: AiSOC 7.5.0 before 12.0.0 Authentication Bypass via Hard-coded JWT Secret

> Attackers can bypass authentication and access cross-tenant live alerts by exploiting a hard-coded JWT secret in AiSOC's realtime services.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-4m55-xhcm-wjcr, GHSA-j6w5-vmvx-vgrp

## What is CVE-2026-103055?

CVE-2026-103055 is a high-severity vulnerability in beenuar AiSOC, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AiSOC versions 7.5.0 before 12.0.0 use a hard-coded constant for JWT verification in the realtime WebSocket and SSE service when the AISOC_REALTIME_JWT_SECRET environment variable is not set. Unauthenticated attackers can forge subscription tickets with arbitrary tenant identifiers to access cross-tenant live alerts, cases, agent events and graph updates through the realtime endpoints.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-103055?


## How do I fix CVE-2026-103055?

No fix has been published for CVE-2026-103055 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103055 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-103055 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103055 and fix it if it is affected.

What it is: CVE-2026-103055 is a high-severity vulnerability in beenuar AiSOC, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-103055 exists.

Affected product: beenuar AiSOC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103055/ (Markdown: https://insights.sbomify.com/CVE-2026-103055/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103055
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103055
- OSV: https://osv.dev/vulnerability/CVE-2026-103055

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103055/
Summaries are generated and may contain mistakes; the official description above is the record.