Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-103055 – Cross-Tenant Authentication Bypass via Hard-Coded JWT Secret – AiSOC v7.5.0 to v11

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-103055 is a hard-coded cryptographic key vulnerability (CWE-321/CWE-798) affecting AiSOC, a security operations platform, that allows unauthenticated attackers to forge valid real-time subscription tickets and access another tenant’s live alert, case, and agent data. The flaw exists because AiSOC’s realtime edge service falls back to a publicly known constant for JWT ticket verification whenever the AISOC_REALTIME_JWT_SECRET environment variable is not explicitly configured — a condition the vendor’s own deployment templates (Docker Compose and Helm charts) leave unmet by default. The issue carries a CVSS v4.0 base score of 8.7 (High) and affects AiSOC versions 7.5.0 through 11.2.0.

Technical details

  • Root cause: The realtime service’s ticket-verification code (resolveTicketSecret() in auth.ts) references a development-only fallback string, 'aisoc-dev-realtime-ticket-secret-not-for-production', when no production secret is supplied.
  • Trigger conditions: The vendor-provided Docker Compose and Helm deployment manifests never set AISOC_REALTIME_JWT_SECRET (or the related ENVIRONMENT / AISOC_ENV / APP_ENV variables) for the realtime container, so the environment-detection logic never switches into production mode and the fallback constant remains active in real deployments.
  • Attack vector: An attacker who knows the published constant can independently mint a JSON Web Token "ticket" and present it to the exposed WebSocket and Server-Sent-Events endpoints — GET /ws/{alerts|cases|agents|insights|graph|all}?token= and GET /sse?token= — which the console proxy forwards without additional authentication checks.
  • Tenant confusion: Because the subscription’s target tenant is derived directly from the (forgeable) JWT claims, a crafted ticket can select any tenant identifier, granting cross-tenant access with no prior authentication or API interaction.
  • Impact: Unauthenticated disclosure of live, streaming security data — alerts, case updates, agent/investigation events, and approval workflows — for arbitrary customer tenants. The vulnerability affects confidentiality only (no integrity or availability impact) but leaves no trace in API access logs since the attacker never contacts the primary API.

Affected software

  • AiSOC (beenuar/AiSOC) versions 7.5.0 up to and including 11.2.0
  • Fixed in AiSOC v12.0.0

Severity

  • CVSS v4.0: 8.7 (High) — 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
  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
  • Network-exploitable, low attack complexity, no privileges or user interaction required.

Mitigation and recommended actions

  • Immediate: Upgrade AiSOC to v12.0.0 or later, which removes the hard-coded fallback constant, makes resolveTicketSecret() fail closed when no secret is configured, and auto-generates a unique secret at first run.
  • If upgrading is not immediately possible:
    • Explicitly set a strong, randomly generated AISOC_REALTIME_JWT_SECRET value for the realtime service in all deployment environments (Docker Compose, Helm/Kubernetes) — do not rely on defaults.
    • Verify that ENVIRONMENT (or AISOC_ENV / APP_ENV) is correctly propagated to the realtime container so production-mode checks activate.
    • Restrict network exposure of the /ws/* and /sse endpoints (e.g., via network ACLs, WAF rules, or gateway authentication) until the secret is properly configured and the platform is patched.
    • Rotate the realtime JWT secret after remediation, since the previous default may have already been exposed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge