Nanobot CVE-2026-49140

Exploitation requires the attacker to hold an authenticated Matrix room membership in a room connected to the target Nanobot instance - confirmed by the CVSS vector PR:L (low privileges required). The Nanobot Matrix channel integration must be configured and active; deployments that do not use the Matrix channel are not affected. Exploitation is limited to the availability dimension (A:L per CVSS); there is no path to data access or integrity modification. No user interaction is required (UI:N) and attack complexity is low (AC:L), meaning any room member can trigger the condition repeatedly without any special timing or race condition. Exploitation is bounded by the attacker's ability to remain a room member and sustain concurrent media event submissions.

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L) assigns a base score of 4.3 (Medium), indicating a network-reachable, low-complexity attack requiring low-privilege authentication with limited availability impact. The PR:L designation confirms that an attacker must hold a valid Matrix room membership - unauthenticated exploitation is not possible per the CVSS vector. The impact is restricted to availability (A:L), with no confidentiality or integrity exposure. No EPSS score was provided in the source data; no CISA KEV listing and no public exploit code have been identified, suggesting this is not under active mass exploitation. The practical risk is highest for deployments where Nanobot's Matrix channel is exposed to semi-trusted or public Matrix rooms, since any room member can trigger the condition. For private, tightly controlled Matrix rooms, exploitability is substantially reduced. The combination of low CVSS, no KEV, no POC, and authentication prerequisite places this in a 'patch in routine cycle' category for most environments, with elevated urgency only for public-facing Matrix integrations.

An attacker who is a member of a Matrix room connected to a Nanobot instance sends a burst of concurrent Matrix media events, each referencing a large remote media file but omitting or falsifying the declared content-length metadata. The handler initiates simultaneous downloads for each event, fully buffering each response body into process memory before the post-download rejection fires, causing rapid memory and bandwidth exhaustion. Service degradation or outright unavailability results without any exploit code beyond standard Matrix client tooling. No public POC has been identified at time of analysis.