What happened
A five-CVE mass disclosure for the open-source AiSOC platform (reported 2026-09-30). CVE-2026-103055 (7.5) hard-codes the JWT verification key; CVE-2026-103057 (4.3) leaves internal push endpoints open; CVE-2026-103054 lets MSSP users claim other tenants. All fixed in 12.0.0.
Why it matters
The platform is an AI-native SOC; cross-tenant alert access and forged event injection poison exactly the data an AI SOC uses for detection and prioritization, and can be used to exfiltrate security telemetry or blind/poison downstream AI decision-making.
Attack vector
When AISOC_REALTIME_JWT_SECRET is unset, the realtime WebSocket/SSE service verifies JWTs with a hard-coded constant, so an unauthenticated attacker forges subscription tickets with arbitrary tenant IDs to read cross-tenant live alerts and incidents. Companion CVE-2026-103057 shows the POST /internal/agent-event and POST /internal/push endpoints accept unauthenticated events that broadcast forged/malicious content over WebSocket and Redis.
Affected systems
AiSOC versions 5.1.0–11.x (realtime WebSocket/SSE service; hard-coded JWT fixed in 12.0.0)
Mitigation
Upgrade to AiSOC 12.0.0 or later; until then set the AISOC_REALTIME_JWT_SECRET environment variable (CVE-2026-103057 has no auth fix short of upgrade).